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

[mwringe]

"alesj" wrote : 
  | 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 ;-)
  | 
The portal sar packages some wars within it, but these wars are going to have to be deployed after the container service is started in the sar. The old way of doing this was looping through everything that was deployed on the server when the service is started.
I don't actually need the whole sar to be finished, just as long as the container service is started.

"alesj" wrote : 
  | 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.
  | 
Adding a jboss-dependency.xml file to the WEB-INF folder does properly add dependencies to the war, so I don't think I need to do anything else there.
It just doesn't seem to work nicely when inside a sar (as you have mentioned above).

"alesj" wrote : 
  | 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.
  | 
Things work properly is deployed separetely, it just means there will be more things to deploy on the server than just a single sar.


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

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