I don't see any value in building a plain JAX-WS service in Ivy without using ivy... The Ivy way is: - create a new Process of type 'Webservice Process''[Webservice Process][1]' - define a signature (in/out parameters)([in/out parameters][2]) - implement business logic in the process that handles webservice invocations and return a result. You can do this in plain Java, but don't have to. You can use all the rich APIs and ProcessElements that speeds up the development time. Behind the scenes ivy will generate a normal JAX-WS endpoint with everything you need. And it will provide monitoring, logging, authentication and deployment life-cycle handling out of the box. ...and if there is really something missing. You still can modify the generated JAX-WS service descriptor and implement it with anything you like in plain Java.Java. [1]: https://developer.axonivy.com/doc/latest/DesignerGuideHtml/ivy.processmodeling.html#ivy.wizards.newprocess [2]: https://developer.axonivy.com/doc/latest/DesignerGuideHtml/ivy.processmodeling.html#ivy-processmodels-elements-wsprocessstart

I don't see any value in building a plain JAX-WS service in Ivy without using ivy... The Ivy way is: - create a new Process of type 'Webservice Process' - define a signature (in/out parameters) - implement business logic in the process that handles webservice invocations and return a result. You can do this in plain Java, but don't have to. You can use all the rich APIs and ProcessElements that speeds up the development time. Behind the scenes ivy will generate a normal JAX-WS endpoint with everything you need. And it will provide monitoring, logging, authentication and deployment life-cycle handling out of the box. ...and if there is really something missing. You still can modify the generated JAX-WS service descriptor and implement it with anything you like in plain Java.