Axis is a great choice because if you switch containers again, you can stick with Axis. Also, it is a lot simpler than dealing with all the overhead of managing and deploying web services in a big bulky J2EE container ... (my personal bias ...).
However, if you must manage your web services within the container, say as EJBs, then have a look at the the WSEE v1.1 specification (JSR-109). Web Services built and packaged this way should run in any J2EE container. Here is an article about it -> http://www-106.ibm.com/developerworks/webservices/library/ws-jsrart/ P.S. you shouldn't have to regenerate the skeleton classes for each new container as long as the entire application - including the generated classes - are packaged in your EAR. Of course, if you change your WSDL and regnerate using the tools from the new container, then the results will be incompatible with the older container's stuff. --- Kiran Kumar <[EMAIL PROTECTED]> wrote: > Hello friends, I need to provide some webservices in > my web-application. Currently this application is on > oracle 9iAS. They have plans to migrate this > application on weblogic 8.1, but in near future. > > I want to build the web services such a way that > when I migrate to a different container, I don't > have to change any code. > > But once I generate the skeleton classes (server > side) using 9iAS tools (Jbuilder..), I will edit the > "impl" classes to call my business logic.. When I > eventually switch to a different container, I will > again have to generate the skeleton classes and may > need to edit the impl classes and they may generate > different class names also. > > So If I choose Axis, I won't have these problems. I > just have to deploy the war file without changing > any code. But I will be limited to what Axis > provides, I will not be able to utilize any extra > features provided by the container. > > I want to take your opinion whether to go with Axis > in my scenario or put the effort to configure the > web services when I switch to a different container. > > Sorry for long mail. I appreciate your help and > time. > > Thanks > Kiran > > ------------------------------------------------ > > This e-mail, and any attachments thereto, is > confidential and is intended only for the > individual(s) named. If you are not the intended > recipient, please let us know by e-mail reply and > delete it from your system; do not copy/save this > e-mail or disclose its contents to anyone. E-mail > transmissions cannot be guaranteed to be secure or > error-free as the transmission could be interrupted, > corrupted, lost, destroyed, altered, arrive late or > contain viruses. ObjectWave does not accept > liability for any errors or omissions in the > contents of this e-mail which arise as a result of > e-mail transmission. The views expressed in this > e-mail do not necessarily reflect those of > ObjectWave or its affiliates. > > ------------------------------------------------ > > >
