[jboss-user] [JBoss Portal] - Re: Order of -object.xml is not guaranteed

[Antoine_h]

Hello,

Yes ! exactly !
it is the real question : the architecture of the whole portal and inner application aggregated by the portal.

Here some few things, that may be usefull.

for what you say, about technical thing (multiple web.xml, sessions, class depencies)... this is main questions.
there are solutions : 
 - several HTTP sessions : yes... but you don't use them... and would have them anyway without a portal... so... that the cost of aggregating things.
 - several : web.xml : you can put the common thing in the model of web.xml of jboss... and the specific thing in each package. more clean, no ?
 - class dependencies : use libs... organise thing with SAR,... this is more clean architecture...
 - multiple delivery : if you want independant delivery and deployement, you have multiple delivery. If you don't need it, you can put every thing in the same package, ... and in the same -object.xml

but this requiere some study... and defining things for each portal project.

mainly, as you conclued it, I am saying that doing the architecture based on the web page tree may not be enough for agregating inner applications.

It is better (and may be requiered) to organize the architecture of a portal, with a focus on the aggregation of inner application.
This is important, as defining the page is only one part of it : there are always some more, as java, JSP, JSF, ... JMX services involved in the aggregated applications.

for what I see in several companies (as a consultant), many of them wants to take a portal plateform, ... just to have a tool to build web pages.

one of them took the portal just to give to a webmaster a tool to build it's pages.
and that is not the best tool for that...
and they end with developper headhache... or when the developer reach to deliver something, ... they have with some big big production troubles.
That is not the portal plateform responsability. It is what they have done with it.

So... yes, some user will see that through -object.xml and admin GUI cool prototyping feature... but I want to warn : think of architecture of the whole packages also... for a successfull development and portal in production...
(whatever JSR-168 portal plateform you work with...)

hope it helps...
Antoine


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

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