[ http://issues.apache.org/jira/browse/JS2-257?page=comments#action_12356050 ]
Michael Lipp commented on JS2-257: ---------------------------------- As David Jencks pointed out, I meant JSR-88(deployment) rather than JSR-77 (j2ee management), of course. > Deployment using JSR77 > ---------------------- > > Key: JS2-257 > URL: http://issues.apache.org/jira/browse/JS2-257 > Project: Jetspeed 2 > Type: New Feature > Components: Deployment > Versions: 2.0-POST > Environment: Any > Reporter: Michael Lipp > Fix For: 2.0-POST > > I am trying to build an EAR that includes Jetspeed as a module (1). I have > put the "shared libraries" as (client-)libraries in the EAR and the > jetspeed.war as a web module. Looks quite promising so far. Of course, > deployment of portlets doesn't work. As far as I have understood the > architecture, the next step would be write a DeploymentManager that uses > JSR77 to deploy the portlet modules in the application server. This should > then be a "general" solution for any JSR77 compliant application server. > Being new to Jetspeed, I' appreciate if someone could confirm that this is > the way to go or tell me if this approach is wrong before I continue the > effort. > Thanks > Michael > (1) I often get the impression that the J2EE ecosystem suffers from mixing up > components and containers. The installation instructions give me the > impression that -- although Jetspeed is a web component -- is has partially > be conceived as an extension of the application server. In order to really > call it "J2EE compliant", I feel it must be possible to bundle Jetspeed into > an EAR in order to be able to deliver a complete (enterprise) application to > the customer in that format. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
