Hi,

Endorsing either JDK or Tomcat seems like a good way to get conflicts to me, 
which could then be harder to resolve.

I would put the libs in WEB-INF/lib, ideally by building the webapp via your 
own maven project, using the magnolia-bundle as an overlay WAR.

That will also force you to resolve library incompatibilities ahead of time.

Regards from Vienna,

Richard


> -----Ursprüngliche Nachricht-----
> Von: [email protected] [mailto:user-list-owner@magnolia-
> cms.com] Im Auftrag von Matteo Pelucco (via Magnolia Forums)
> Gesendet: Dienstag, 13. Mai 2014 16:53
> An: Magnolia User List
> Betreff: [magnolia-user] WebServices (jax-ws) with Magnolia 5.x
> 
> Hi guys,
> any time I start a webservice-based project, I "reinvent the wheel": once
> because the webserver is Microsoft based, another time it is built with Axis,
> other again Magnolia version is different..
> 
> So I ask.
> 
> Which is the best way to deploy jax-ws libraries (2.2.7) on a Magnolia
> installations?
> 
> 1) Drop all jax-ws ri bundle in WEB-INF/lib, aside of Magnolia jars.
> 2) Endorse JDK
> 3) Endorse Tomcat
> 
> Any good advise here?
> I see that Magnolia already has some jax-ws library (e.g.: jaxb-core,
> FastInfoset...).. I don't want to have my installation unstable..
> 
> Thanks as usual
> M.
> 
> --
> Context is everything: http://forum.magnolia-
> cms.com/forum/thread.html?threadId=6073cbf7-d3f1-4661-ac8e-
> 641aafba7160
> 
> 
> ----------------------------------------------------------------
> For list details, see http://www.magnolia-cms.com/community/mailing-
> lists.html
> Alternatively, use our forums: http://forum.magnolia-cms.com/
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------



----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to