JBossDeveloper

"richard.opalka@jboss.com" wrote:

"alesj" wrote:

What do you have in your .sar? MBeans?

No, just web archive (incorporating WebService endpoints our deployers operate with)

"richard.opalka@jboss.com" wrote:

"alesj" wrote:

http://java.dzone.com/articles/a-look-inside-jboss-microconta

I'm reading it now ;)

I'm going to reset this conversation in the next post,
but first let me try to summarise the description of this problem
from this long thread and explain what I think is really happening
(and tell you how you would do exactly what you are asking for
although it is the wrong way to do it).

So you can tell me where I have misunderstood .... :-)

You have a sar that contains a war, e.g. like the web-console

[ejort@warjort management]$ ls -l console-mgr.sar/
total 1560
-rw-rw-r-- 1 ejort ejort 142692 Nov 3 20:59 console-mgr-classes.jar
-rw-rw-r-- 1 ejort ejort 307601 Nov 3 20:59 jcommon.jar
-rw-rw-r-- 1 ejort ejort 1098048 Nov 3 20:59 jfreechart.jar
drwxrwxr-x 2 ejort ejort 4096 Nov 3 20:59 META-INF
drwxrwxr-x 7 ejort ejort 4096 Nov 3 21:00 web-console.war

So now for the reset. Which of the following mistakes is true? :-)

"adrian@jboss.org" wrote:

1) The webapp (metadata) you are creating is missing a dependency
so the services are being constructed in the wrong order.

2) You are trying to create or access the service in the deployer processing which
you should not be doing.

"richard.opalka@jboss.com" wrote:

"richard.opalka@jboss.com" wrote:

Thus we're getting null for JBossWebMetaData ctx loader which isn't true in case we're deploying such .sar archive using hot deploy feature (JBossAS is already running). The problem is on JBossAS bootstrap when we have such .sar archive in the deploy directory.

 ClassLoader warLoader = unit.getClassLoader();
 thread.setContextClassLoader(warLoader);

<snip/>

 webApp = new WebApplication(metaData);
 webApp.setClassLoader(warLoader);

In general all your processing in the deployers should just be based on metadata
available to deployers or configuration on the deployers.

You shouldn't be looking at any services.

e.g. suppose the war had a dependency on an ejb from some other application
then its not going to be started until that ejb exists regardless of when jbossweb.sar
gets started.

"richard.opalka@jboss.com" wrote:

"adrian@jboss.org" wrote:

I don't see a ctx loader on JBossWebMetaData?
That doesn't make any sense.

Here's our code:

 // JSE endpoints
 else if (dep.getAttachment(JBossWebMetaData.class) != null)
 {
 JBossWebMetaData webMetaData = dep.getAttachment(JBossWebMetaData.class);
 ClassLoader classLoader = webMetaData.getContextLoader();
 if (classLoader == null)
 {
 // [JBWS-2246] hack for .sar deployments incorporating web services deployments
 classLoader = dep.getInitialClassLoader();
 }
 dep.setRuntimeClassLoader(classLoader);
 }

 /** The web context class loader, used to create the ws4ee service endpoint */
 @Deprecated
 private transient ClassLoader cxtLoader;