JBossDeveloper

"thomas.diesler@jboss.com" wrote:
I read http://labs.jboss.com/file-access/default/members/jbossmc/freezone/docs/2.0.x/userGuide/pt04.html
Is there anywhere else this is documented?

How do I set the deployments class path?
I cant do

 // There is one top level deployment
 ContextInfo context = factory.addContext(unit, "");
 context.addClassPathEntry(entry);

In my case, the deployment should use the context class loader of the calling component.

"adrian@jboss.org" wrote:

I don't know if the non-VFS stuff is documentated?
There's certainly lots of examples in the testsuite.
The user guide just tells people how to do normal things. ;-)

Thomas, can you enable some trace on "org.jboss.system" and paste it here?

The Security Deployer just deals with the MetaData and creates a top level service bean. It does not do any Classloader circus.

There is something that is happening with your web service deployments.

The relevant code is in the ServiceDeployer:

 public void deploy(DeploymentUnit unit, ServiceMetaData deployment) throws DeploymentException
 {
 ObjectName name = deployment.getObjectName();
 try
 {
 ObjectName loaderName = deployment.getClassLoaderName();
 if (loaderName == null)
 {
 ClassLoader cl = unit.getClassLoader();
 if (cl != null && cl instanceof RepositoryClassLoader)
 loaderName = ((RepositoryClassLoader) cl).getObjectName();
 // TODO add to RealClassLoader
 else if (cl != null && cl instanceof RealClassLoader)
 loaderName = ((RealClassLoader) cl).getObjectName();
 else
 loaderName = defaultClassLoader;
 }

What is the codebase for the org.jboss.test.ws.jaxws.endpoint.EndpointTestCase in the JBAS-5257 issue? The last time I looked at the ws tests the codebase was https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2. This no longer exists?

https://svn.jboss.org/repos/jbossws/stack/native/tags/jbossws-native-2.0.3.GA/

"thomas.diesler@jboss.com" wrote:

You create Deployment on the fly

Yes, please show me the code that creates the deployment on the fly - attaches the WMD and deployes it afterwards.

"alesj" wrote:
Or where exactly are you stuck now?

I meant programatically. :-)

What is the piece of code that tries to do something with deployments but fails?
What exactly is trying to do?
What is supposed to do?
Where do you see the possible problem?
...

You need to give me exact details.
Or exact questions.

Sorry, but I'm not gonna dig into WS code.

Give me few minutes, I'll review the test and the failure.

Ales, don't worry about it.
I gave up trying to help these guys a while ago.

If somebody doesn't have the analysis skills to make a question answerable
then I don't have the time to try to guess/work out what the question actually is.
http://wiki.jboss.org/wiki/HelpExpertSystem

Please help me, is not such a question.

This is our usecase:

We have the jaxws-endpoint-servlet.war web archive with the following content:

jar -tvf jaxws-endpoint-servlet.war
META-INF/
META-INF/MANIFEST.MF
WEB-INF/
WEB-INF/classes/
WEB-INF/classes/org/
WEB-INF/classes/org/jboss/
WEB-INF/classes/org/jboss/test/
WEB-INF/classes/org/jboss/test/ws/
WEB-INF/classes/org/jboss/test/ws/jaxws/
WEB-INF/classes/org/jboss/test/ws/jaxws/endpoint/
WEB-INF/classes/org/jboss/test/ws/jaxws/endpoint/EndpointBean.class
WEB-INF/classes/org/jboss/test/ws/jaxws/endpoint/EndpointInterface.class
WEB-INF/classes/org/jboss/test/ws/jaxws/endpoint/EndpointServlet.class
WEB-INF/wsdl/
WEB-INF/wsdl/TestService.wsdl
WEB-INF/web.xml

The most important class here is EndpointServlet, which contains the following lines of code:

public void init(ServletConfig config) throws ServletException
{
 super.init(config);

 // Create the endpoint
 EndpointBean epImpl = new EndpointBean();
 javax.xml.ws.Endpoint 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);
}

JBossWebMetaData jbwmd = dep.getAttachment(JBossWebMetaData.class);

AbstractDeployment deployment = createSimpleDeployment(dep.getSimpleName());
MutableAttachments ma = (MutableAttachments)deployment.getPredeterminedManagedObjects();
ma.addAttachment(HttpSpec.PROPERTY_GENERATED_WEBAPP, Boolean.TRUE);
ma.addAttachment(ClassLoaderFactory.class, new ContextClassLoaderFactory());
ma.addAttachment(JBossWebMetaData.class, jbwmd);
mainDeployer.deploy(deployment);

...

private static class ContextClassLoaderFactory implements ClassLoaderFactory
{
 public ClassLoader createClassLoader(DeploymentUnit unit) throws Exception
 {
 return Thread.currentThread().getContextClassLoader();
 }

 public void removeClassLoader(DeploymentUnit unit) throws Exception
 {
 }
}

You need to make a copy of the JBossWebMetaData and use setContextRoot("jaxws-endpoint").

The getPredeterminedManagedObjects attachments bucket is the wrong one to be using. This is for data that is set from previous admin edits through the profileservice. The client spi does not look correct for deployer implementations.

We also need this usecase in the jbossas testsuite as an illustration of proper dynamic deployment creation.