|
|
|
|
|
|
| | | |
FAQs: Web Services
Does WebLogic Server 6.1 support SOAP Messages with Attachments?
WebLogic Server 6.1 can accept SOAP Messages with Attachments. However, the implementation currently does not do anything with the attachment. This means that WebLogic Server will accept a SOAP Message with an Attachment, the SOAP message will be parsed and processed, but the attachment will be ignored. Full support for attachments will be available in a future release.
Does WebLogic Server 6.1 support SOAP?
Yes. WebLogic Server's implementation of SOAP is included as part of the Web Services subsystem. For detailed information on creating Web Services with WebLogic Server, see Programming WebLogic Web Services.
Are Microsoft SOAP Toolkit and .NET supported in WebLogic Server 6.1?
At the time of WLS 6.1 development, there were incompatibilites between Microsoft SOAP Toolkit and the .NET beta. Since MS SOAP Toolkit was the only SOAP implementation officially supported by Microsoft, WLS 6.1 supports MS SOAP Toolkit only. .NET will be supported in a future release.
Can I use Version 6.1 of the WebLogic Web Services Client API in a WebLogic Server 6.0 component?
No. If you use the WebLogic Server Web Service client API (version 6.1) in a WebLogic Server 6.0 component, such as an EJB, you get the error java.rmi.ConnectException: No available router to destination. This is because a 6.0 JNDI URL factory gets called rather than the initial context factory that you specify in your client code.
To work around this problem, delete the 6.0 JNDI URL factories by adding the following code snippet when you make your initial context:
h.put(Context.URL_PKG_PREFIXES, "");
What interoperability issues should I be aware of with 6.1 WebLogic Web services?
6.1 WebLogic Web services pass most of the Round 2 SOAP Interoperability tests. For details about specific interoperability issues, see Interoperability.
|
|
|
|
|
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|