"thomas.diesler(a)jboss.com" wrote : In other words, I have JBossWebMetaData - how do I deploy them?
OK, I still don't see where you create it.
Where does the owner thread come from - who triggers the creation?
>From Adrian's response:
"adrian(a)jboss.org" wrote :
| The other web deployers don't care whether the WebMetaData came from parsing
| a web.xml or if you created it programmatically.
You create Deployment on the fly, attach JBWMD to it, and just push it to the deployers.
They will pick the metadata the same way as if it came from parsing jboss-web.xml.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132100#4132100
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132100
Any component can setup an endpoint using the endpoint API.
The impl of that API uses the WS deployment aspect shown above - we do not have a deployer at that time. i.e. the component initiates the deployment at runtime.
| // Create the endpoint
| EndpointBean epImpl = new EndpointBean();
| endpoint = Endpoint.create(SOAPBinding.SOAP11HTTP_BINDING, epImpl);
|
| // Create and start the HTTP server
| SPIProvider spiProvider = SPIProviderResolver.getInstance().getProvider();
| HttpServer httpServer = spiProvider.getSPI(HttpServerFactory.class).getHttpServer();
| httpServer.start();
|
| // Create the context and publish the endpoint
| HttpContext context = httpServer.createContext("/jaxws-endpoint");
| endpoint.publish(context);
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132098#4132098
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132098
IMHO, we should generally decide whether a combination of CR+LF is valid for an incomming message.
If it is valid (even for a normal incoming message) the stack should preserve it.
It can possibly be invalid for an incoming message that uses WS-Security, in which case we should have a clear error message if possible.
If it is invalid, our stack should not produce it.
Generally, I believe we should be strict rather than lenient with respect to message integrity. Axis opted to be lenient and tried to tolerate all sorts of inconsistencies - AFAICS they ended up with an unmaintainable code base.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132091#4132091
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132091
Using the JAX-WS Endpoint API it is possible to setup a WS endpoint for a given endpoint bean and web context.
Prior to the changes above we used to generate webapp descriptors and deployed them through the client deployer API.
Please show me how to do this in memory. I generate the JBossWebMetaData ,but I don't have a deployment unit to attach it to.
| DeploymentUnit unit = dep.getAttachment(DeploymentUnit.class);
| if (unit != null)
| {
| unit.addAttachment(JBossWebMetaData.class, jbwmd);
| unit.addAttachment(WebMetaDataModifier.PROPERTY_GENERATED_WEBAPP, Boolean.TRUE);
| }
| else
| {
| // TODO: endpoint API cannot use an existing deployment unit
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132073#4132073
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132073