[jboss-dev-forums] [Design of JBoss Portal] - Re: Design of Portal Deployer

[alesj]

"mwringe" wrote : 
  | I must not understand this part enough. If I have a sar with a nested war, the war is sent to the tomcat deployer last no matter what parentfirst is set in the sar deployer.   
  | Note that I tested this deploying the sar after the server has been started. If the sar is in the deploy directory as the server starts its behaves differently.
  | 
  | I have been trying it using the dependency deployer, but it doesn't work. If I specify I want the war to be deployed after the sar is done with the real stage, it fails since it can't find the sar dependency. It will work perfectly fine in the war is removed from the sar and is no longer nested.
  | 
  | I would prefer to use the dependency mechanism rather than changing the portal from a sar into something else with its own custom deployer, but I can if necessary.
  | 
OK, the parentFirst == false was a guess/quick attemp :-), which doesn't work here.

What exactly are you trying to do?
As it sounds weird/wrong. :-)
e.g. .sar is only finished when its children (in this case .war) are finished
but your .war should wait for .sar to finish ... chicken and egg problem ;-)

Although in this case you might even get away with this,
as .war at the end is nothing more than a mbean --> ServiceDeployer.
And if you put proper depends on it, it would have the right order dependencies.
I'm just not sure how easy/hard it is to add dependencies to a .war's mbean representation.

What about if you deploy things separately - with proper jboss-dependency.xml in the top level?
The classloading should work, as long as the flat (non-scoped) model is used. 
Or it's part of common/server lib - which I guess is right place so real jbp users can write against your custom jbp api.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202776#4202776

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202776