Re: getting Jetspeed 2 to work with WebSphere 5.1.2
He is the error that I get when I import the war file directly after they are registered TRAS0014I: The following exception was logged java.lang.NullPointerException at com.ibm.ws.webcontainer.srt.SRTServletRequest.getContextPath(SRTServletRequest.java:1229) at javax.servlet.http.HttpServletRequestWrapper.getContextPath(HttpServletRequestWrapper.java:183) at org.apache.jetspeed.container.invoker.ServletPortletInvoker.invoke(ServletPortletInvoker.java:209) at org.apache.jetspeed.container.invoker.ServletPortletInvoker.render(ServletPortletInvoker.java:124) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:103) at org.apache.jetspeed.container.JetspeedPortletContainerWrapper.renderPortlet(JetspeedPortletContainerWrapper.java:88) at org.apache.jetspeed.aggregator.impl.RenderingJob.run(RenderingJob.java:109) at org.apache.jetspeed.aggregator.impl.Worker$1.run(Worker.java:171) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:626) at org.apache.jetspeed.aggregator.impl.Worker.run(Worker.java:165) . java.lang.NullPointerException at com.ibm.ws.webcontainer.srt.SRTServletRequest.getContextPath(SRTServletRequest.java:1229) at javax.servlet.http.HttpServletRequestWrapper.getContextPath(HttpServletRequestWrapper.java:183) at org.apache.jetspeed.container.invoker.ServletPortletInvoker.invoke(ServletPortletInvoker.java:209) at org.apache.jetspeed.container.invoker.ServletPortletInvoker.render(ServletPortletInvoker.java:124) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:103) at org.apache.jetspeed.container.JetspeedPortletContainerWrapper.renderPortlet(JetspeedPortletContainerWrapper.java:88) at org.apache.jetspeed.aggregator.impl.RenderingJob.run(RenderingJob.java:109) at org.apache.jetspeed.aggregator.impl.Worker$1.run(Worker.java:171) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:626) at org.apache.jetspeed.aggregator.impl.Worker.run(Worker.java:165) On Tue, 15 Mar 2005 17:48:40 -0700, Seth Ford <[EMAIL PROTECTED]> wrote: > Yeah... I have been working on Jetspeed 2 M1 and am struggling to > get the default portlets to work in WebSphere 5.1.2 I guess I can try > your new branch, but if you can provide any help getting them working > on WebSphere/WSAD I would appreciate it. In > this case I am trying to use the hot deploy the database is > connection fine the portal deploys but then WebSphere does not have > any idea about the new contexts that have been layed down /demo > and such > > I have also tried importing the portlet war files but then I get a > requestdispatcher include error > Has any got jetspeed 2 working on WebSphere? And if so I would > appreciate any details you might have > > > On Sun, 13 Mar 2005 22:51:45 +0100, Ate Douma <[EMAIL PROTECTED]> wrote: > > 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] > > > > > >
Re: getting Jetspeed 2 to work with WebSphere 5.1.2
Yeah... I have been working on Jetspeed 2 M1 and am struggling to get the default portlets to work in WebSphere 5.1.2 I guess I can try your new branch, but if you can provide any help getting them working on WebSphere/WSAD I would appreciate it. In this case I am trying to use the hot deploy the database is connection fine the portal deploys but then WebSphere does not have any idea about the new contexts that have been layed down /demo and such I have also tried importing the portlet war files but then I get a requestdispatcher include error Has any got jetspeed 2 working on WebSphere? And if so I would appreciate any details you might have On Sun, 13 Mar 2005 22:51:45 +0100, Ate Douma <[EMAIL PROTECTED]> wrote: > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: getting Jetspeed 2 to work with WebSphere 5.1.2
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]
getting Jetspeed 2 to work with WebSphere 5.1.2
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]
