Note, that the default mapping for xsd:dateTime is java.util.Date. Since the XML Schema type has unlimited precision, fractions smaller than a millisecond would be lost in this mapping. If this is an issue, it is possible to change the generated stub by hand and use either java.sql.Timestamp or org.idoox.wasp.serialization.xsdbuiltin.DateTime.
WS-I Interoperability Testing Tools in all current versions (1.0 and 1.1) incorrectly report a violation of assertions BP2102 and BP2122 on WSDLs that contain an xsd:import element without a schemaLocation attribute. This is not a problem of SSJ and such WSDLs are interoperable.
The SoapSpy tool does not comply with WS-I Basic Profile 1.1.
WSO2 SOA Enablement Server cannot be installed to a path containing special and international characters.
WSO2 SOA Enablement Server cannot be started with the wasp.location property in UNC format.
.NET allows its services to use DIME attachments even with no mention of them in the WSDL. However, WSO2 SOA Enablement Server for Java requires the attachment to be defined in the WSDL. (Please see the section "No WSDL Support for DIME" in Microsoft's document Using Web Services Enhancements to Send SOAP Messages with Attachments for details.)
To support attachments not described in WSDL, use the prepared handler org.systinet.wasp.attachments.UnreferencedAttachmentsHandler.
Remote references do not work with SOAP 1.2 protocol.
SAAJ implementation does not contain the text/plain and image/jpg DataContentHandler.
xsd:choice in rpc/encoded mode does not work properly
SAAJ SOAPMessage with attachments does not support initialization from InputStream and writing to OutputStream (without attachments it works properly). You can use WSO2 SOA Enablement Server transport messages instead.
Method overloading does not work when DII is used.
When starting HTTP server and calling destroy() on it, it takes about 40 seconds in some cases to stop the server due to a JDK bug (depending on the configuration of maxReadTime in the HTTP server configuration). The same problem exists on the client side when using transport coupling for asynchronous invocation. Under rare conditions the server must be closed using the System.exit() call.
SMTP Multi-part messages (using mail transport) can be transferred incorrectly (some SMTP servers refuse messages with bare '\n').
No support of WS-Addressing EndpointReference policy. A policy can be attached to EndpointReference but it is not sent with the EndpointReference in WS-Addressing headers. If such a policy is received in WS-Addressing headers it is ignored now.
Only standard policy attachments per EndpointReference and global policy are supported now (also per WSO2 SOA Enablement Server ServiceEndpoint). The SpecVersion assertion is the only part of WS-PolicyAssertions that is implemented.
WSO2 SOA Enablement Server is not compatible with .NET Framework Type System.Char.
When a WSO2 SOA Enablement Server service endpoint uses the RPC binding and encoding style, it must explicitly declare rpc/encoded behavior in its deployment descriptor. (Please see Java Collections in .NET for details.)
The xsd:dateTime schema is represented as java.util.Date in Java, and as System.DateTime in .NET. However, System.DateTime is a value type and therefore it cannot be null.
Restrictions on Using WS-Security: See Restrictions.
Configuring WS-Security for WS-ReliableMessaging Setting message configuration into the call context affects only outgoing responses, not WS-RM acknowledgments. WS-RM acknowledgements are still affected by setting message configuration into the service endpoint context. Please see Configuring WS-Security for WS-ReliableMessaging for details.
"spy_client" targets are missing from some Security demos. Our SoapSpy tool does not work properly with SOAP headers or SSL.
The Kerberos authentication provider suffers from some difficulties with Sun's implementation of Kerberos. For related bugs, use the search string "kerberos bugs" at http://java.sun.com.
As everything now runs under the system account, Subject.doAs() is not called during request routing.
WSO2 SOA Enablement Server authorization providers allow access control between the outside world and WSO2 SOA Enablement Server for Java. Services are allowed to manage the whole framework offered by WSO2 SOA Enablement Server.
Multi-valued attributes are not supported by the LDAP user store implementation.
Passwords are stored in plain text in our configuration files.
When WSO2 SOA Enablement Server for Java is ported to an application server, there can be a number of complications with using the WSO2 SOA Enablement Server security framework. For more details, please see Porting Notes.
SPKM support was removed from WSO2 SOA Enablement Server for Java.
Persistent AsyncConversation from the asynchronous invocation API is not implemented. Hence, application code cannot be informed about the acknowledgement or response receipt after restart.
When using asynchronous invocation with an anonymous client, the beginXXX method is blocked until the request is delivered.
Non-finished AsyncConversations are not unblocked when a sequence expires.
The reliable anonymous request-response use-case is not fully supported, as a response can not be delivered when a connection is broken, aborted, timed out, etc.
Reliable non-anonymous client applications never shut down automatically when using the ServiceClient.setAsyncEndpointPath(...) method. The endpoint should be unpublished by the ServiceClient.unpublishAsyncEndpoint() method and after that the client application will exit.
No support of WS-RM SequenceRef. It is not possible to attach a policy to an individual sequence or sequence prefix directly.
When the first request to an EJB as a Web service is directed to localhost, the EJB will not be accessible from outside. It is best to access an EJB as a Web service using the full name of the computer.
Many versions of JBoss come with an older embedded Hypersonic database that is not supported by our persistent storage tool. Due to this fact we recommend using a different supported database than Hypersonic when WSO2 SOA Enablement Server for Java is ported to the JBoss application server.
Some web server containers or application servers delete web applications temporary directories when they reboot. This may cause important data and modified configurations to be lost. If you port a self-contained WSO2 SOA Enablement Server web application to such a web server or application server, do not copy the WSO2 SOA Enablement Server web application to the deployment directory. Extract it there instead.
WSO2 SOA Enablement Server Administration Console suffers from the following issues:
You cannot add an interceptor that is parameterized using the WSO2 SOA Enablement Server Server Administration Console.
Java2WSDL cannot parse source using Java 5's new language features. The workaround is to create WSDLs only from class files.
GUI UserStore has the following known issues:
When login to the server fails, the user is allowed to perform all operations, but the tools freeze as soon as the user tries one.
Context menus do not work on Linux.
An invalid user with an empty name can be added to the user store.
There are problems with the hiding of inactive functions when switching between the user store and the key store.
AuthPolicy does not show a warning message when trying to assign a non-existent role to a user. The role is not assigned, but a warning should be displayed.
SoapSpy has difficulty with large attachments and chunked HTTP messages.