• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • paul wheaton
  • Ron McLeod
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:

Webservice deployment dilemma using weblogic server.

 
Ranch Hand
Posts: 42
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello All,

I am new to webservice .. learning JAX-WS using Weblogic as a middle-ware.

I have seen in examples that there are two ways of deployment :---

1. using Endpoint.publish() method eg..



2. using a build.xml file eg..



I want to know if we can use Endpoint.publish() for realtime projects.. What is the compelling reason to use this method of deployment why is better or worse to use Endpoint.publish over deployment through a build.xml script.


Is there another way of deployment by creating a war/ear file and then deploying it using the weblogic console

Is there a server independent deployment technique so that if I move the webservice code from one server to the other I dont have to follow server specific deployment processes as given in the above build.xml spefic for weblogic server



I have been surfing through many examples and articles in google.. but could not find a coherent answer to my questions... If I am being naive please excuse me but I need to clear these doubtful niggles that are pinching my comprehension of the Webservice concept..

Regards

Guy
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic