Seth,
I can't directly help you with WebSphere but I am interested in how you got it working and with which version of Jetspeed 2 you are working.
As you might know, I created a new branch of Jetspeed 2 somewhat more than a week ago (branch: deployment_refactoring, see http://issues.apache.org/jira/browse/JS2-210) in which I've implemented an application server indepedent deployment model. If you haven't tried that one out yet, you might have a better result doing so.
Note the current limitations of that branch though (see the JS2-210 issue). I'm working right now on improvements which should resolve those limitations, but it probably will take me a few hours more (or possibly a few days if I run out of time) before I can commit those improvements.
Regarding your question about cross context problem: all portlets deployed with Jetspeed 2 use cross context. So, if the default portlets provided by Jetspeed 2 *are* working, cross context shouldn't be the problem. Maybe if you provide us with some more detailed information (like error messages and stacktraces) I or someone else can help you better.
Regards, Ate
Seth Ford wrote:
I have jetspeed 2 working with WebSphere 5.1.2 except for the portals that are done through a hot deploy.... Can any explain how to do this in WebSphere? I have tried to install the portlet WARs seperatly, but have run into request dispatcher include related issues.... looks like a cross context problem Thanks Seth
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
