[Design of JBoss Portal] - Re: Design of Portal Deployer
by mwringe
"alesj" wrote : "mwringe" wrote :
| | 1) The current approach is that we have all the jars that used to exist in the portlet container sar moved over to the deployer. The sar is then used to just to start the portlet container at run time (it becomes basically just a jboss-service.xml file).
| |
| Why -service.xml instead of -beans.xml?
|
Thats the way the current sar is setup, I can be converted to a -beans.xml in the future. Is there a big reason to switch?
"alesj" wrote :
| "mwringe" wrote :
| | The deployer uses the microcontainer kernel to get a reference to the portlet containers runtime objects and uses those to directly inject the information into the running server.
| |
| Why MC kernel usage?
| Inject portal objects directly.
|
Because the deployers are started before the deployables, so I can't inject something from a deployable into a deployer (correct me if I am wrong, but I have tried this)
So I use the MC kernel to get a reference to the objects at runtime which gives me the same result.
"alesj" wrote :
| "mwringe" wrote :
| | 2) more distinct separation between the deployer and the portlet container.
| | The deployer would only contain jars for the metadata, the deployers themselves and for interface classes that will be used to pass data between the deployer and the portlet container.
| | In this case the deployer would parse the xml files into metadata, then convert the metadata into the proper classes for the common interface, then have the portal container have new classes to interface with the deployer to convert the common interface into the classes that it requires.
| |
| OK, the common metadata driven approach.
|
So the common metadata driven approach is the best?
"alesj" wrote :
| Any new idea with the .tld handling?
No, and there are other deployers which need to do similar things (sometimes even worst than the tld deployers). I know its not the best way of doing it, but it works. It something that will need to be looked into more and fixed (if possible).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208616#4208616
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208616
15 years, 5 months
[Design of JBoss Portal] - Re: Design of Portal Deployer
by alesj
"mwringe" wrote :
| 1) The current approach is that we have all the jars that used to exist in the portlet container sar moved over to the deployer. The sar is then used to just to start the portlet container at run time (it becomes basically just a jboss-service.xml file).
|
Why -service.xml instead of -beans.xml?
"mwringe" wrote :
| The deployer uses the microcontainer kernel to get a reference to the portlet containers runtime objects and uses those to directly inject the information into the running server.
|
Why MC kernel usage?
Inject portal objects directly.
"mwringe" wrote :
| 2) more distinct separation between the deployer and the portlet container.
| The deployer would only contain jars for the metadata, the deployers themselves and for interface classes that will be used to pass data between the deployer and the portlet container.
| In this case the deployer would parse the xml files into metadata, then convert the metadata into the proper classes for the common interface, then have the portal container have new classes to interface with the deployer to convert the common interface into the classes that it requires.
|
OK, the common metadata driven approach.
Any new idea with the .tld handling?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208518#4208518
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208518
15 years, 5 months