QA

Q&A

Q1:

Can I use a Java client to access the Web Services provided by .NET?

A1:

Because the cornerstone of Web Services is seamless and interoperable interaction irrespective of the technology used, it is perfectly possible for a Java client to access .NET's Web Services. The Java client needs to use the fully qualified service name and WSDL port of the Web Service provided by .NET, along with the type of binding. The Java client can use JAX-RPC to communicate with the Web Services provided by the .NET server components because the underlying protocol used by JAX-RPC is SOAP.

Q2:

Will WebLogic Server 7.0 help me to expose an EJB's business methods as a Web Service?

A2:

Most certainly yes. The main advantage of WebLogic Server 7.0 is a changed model for Web Services that allows components deployed in WebLogic Server, such as EJBs, to be exposed as Web Services to Web Services client applications. After building the .jar file of an EJB, you should generate the web-services.xml file using the ant tool. The generated web-services.xml file is packaged into the final .ear file along with the generated classes for data types of the methods of the EJB that are exposed using Web Services.



Sams Teach Yourself BEA WebLogic Server 7. 0 in 21 Days
Sams Teach Yourself BEA WebLogic Server 7.0 in 21 Days
ISBN: 0672324334
EAN: 2147483647
Year: 2002
Pages: 339

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net