<div>
I don't know if JDeveloper can generate the stubs by itself. I know though that it doesn't really matter.<br />
<br />
All IDEs that support the operation above (axis2 client) use the wsdl2java tool of axis2 and generate the exact same client (changes might occur if IDE supports something else beside axis2 like xfire, jax_ws etc).<br />
<br />
Personally I use maven2 and I let maven2 appropriate plugin to do the work. <br />

</div>


I don't know if JDeveloper can generate the stubs by itself. I know though that it doesn't really matter.

All IDEs that support the operation above (axis2 client) use the wsdl2java tool of axis2 and generate the exact same client (changes might occur if IDE supports something else beside axis2 like xfire, jax_ws etc).

Personally I use maven2 and I let maven2 appropriate plugin to do the work.


<div>
But I wanted to know if I can use client stubs created by axis in Jdeveloper environment?
</div>


But I wanted to know if I can use client stubs created by axis in Jdeveloper environment?

<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
We have an portal application which is in Jdeveloper IDE. Now there is an webservice which we now should start using.<br />
<br />
My question is whether I need to generate stub file using axis2 and import them to Jdeveloper<br />
<br />
or Jdeveloper itself can generate the client stubs.<br />
<br />
Let me know which one is better? <br />
<br />
Thanks<br />
Roop
</div>
</div>


Hello,

We have an portal application which is in Jdeveloper IDE. Now there is an webservice which we now should start using.

My question is whether I need to generate stub file using axis2 and import them to Jdeveloper

or Jdeveloper itself can generate the client stubs.

Let me know which one is better? 

Thanks
Roop

Accessing a Web service and using Axis2 and Jdeveloper IDE

Java Enterprise Edition (Java EE) is a specification defining a collection of Java-based server and client technologies and how they interoperate. Java EE specifies server and client architectures and uses profiles to define technology sets targeted at specific classes of applications. All Java EE profiles share a set of common features, such as naming and resource injection, packaging rules and security requirements.