Re: [jbossws-dev] EJB3 endpoints into WAR deployments

>> I'd say we won't have DeploymentType abstraction anymore. >> We will just have EndpointType abstraction with the following values: >> * JAXWS_POJO >> * JAXWS_EJB3 >> * JAXRPC_POJO >> * JAXRPC_EJB21 > The jaxrpc side of the issue is still to analysed, anyway, I see your > point, we can simply derive the DeploymentType info (JAR or WAR) from > the new EndpointType, so the former can simply be removed. But we still need let each endpoint easily know its deploymentType(war,ear or jar) information and other deployment context information(WarMetaData, EARMetaData or we wrapped JSEArchiveMeteData, EJB EJBArchiveMetaData). Then we can decide the address and context root when the ws endpoint is actually published.

> In the next future we'll work on allowing different context-root for > endpoints in the same webapp: that also implies deep changes in the > container integration, as most probably multiple webapps need to be > started to be able to publish endpoints in different context-roots and I > can foresee multiple issues with that (classloading just to say one). The @WebContext annotated with EJB3Endpoint is supported outside war file . We won't consider to support this case this time to keep thing simple ?

JAXWS_POJO WS endpoints coexists with EJB3Endpoint in a war file and there is jboss-web.xml to define the Context root with specific value. and EJB3Endpoint annotated with @WebContext. Alessio, can your new created dynamically publish endpoint function help on this case ?