Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

use of webservices.xml  RSS feed

 
Ranadhir Nag
Ranch Hand
Posts: 138
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We write a simple webservice and deploy it on weblogic 10.3
Specifically,we follow the following steps:
1.write the WSDL
2.generate the Impl using wsdlc
3.compile the server classes,including the impl using jswc in exploded form.
4.use the weblogic admin console to deploy this application,by pointing weblogic to the implementation source.

We notice that after this process,we do not have any webservices.xml(or its weblogic equivalent weblogic-webservices.xml) formed in the WEB-INF of the generated war.
Does this mean that webservices.xml is a optional deployment descriptor?
What is it meant for?
 
Ranadhir Nag
Ranch Hand
Posts: 138
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have one twist to this tale .
We are using jwsc on weblogic to generate the server stubs for our impl classes.

<target name="build-service">
<!--add jwsc and related tasks here -->
<jwsc
srcdir="."
destdir="${server_classes}"
>
<jws file="oracle/wls/em/SampleBackendComponent.java"/>
<!--type="JAXWS"/>-->
</jwsc>
</target>

On commenting out the 'type="JAXWS"' line(default is JAX-RPC I believe), we do get the weblogic-webservices.xml.
However the 'JAXWS' option gives us no deployment descriptor on compilation.

Is this intended?Does JAXWS bring about some behavioural changes that do not need deployment descriptors any more?
 
Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!