Pedro Correia [
http://community.jboss.org/people/sgt_pimenta] created the discussion
"Re: jbossws-native: Publish HttpContext via Endpoint API"
To view the discussion, visit:
http://community.jboss.org/message/605699#605699
--------------------------------------------------------------
Hi Richard,
I understand that the feature has been dropped, but from the end-user point of view I
wouldn't really look at it as a "hack".
If there is a container available (i.e. JBoss/Tomcat) why should one be "forced"
to use Netty, Jetty, Glassfish mini-server, etc.? :)
In other words, it means that any JBossWS *javax.xml.ws.Endpoint* implementation (native,
cxf, metro) is not compatible (programmatically at least) with JEE container deployment;
which (by the book) should be performed using the classical WAR packaging approach.
Correct?
I was checking CFX "Endpoint" implementation and wondering if, by any chance,
would be possible to inject the container's HTTP server in the endpoint's
*JaxWsServerFactoryBean* ? Maybe I am persisting in the "hack" here...
Thanks for your support, I will consider your recommendation for switching to CFX as
well.
Pedro
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/605699#605699]
Start a new discussion in JBoss Web Services at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]