Re: WebLogic 8 <> WebSphere 6.0.1 -
T3S - NoClassDefFound

Sebastian Bayerlein <> writes:

You should use IIOP in this instance. Trying to use the full WL client
is only going to lead to this sort of problem. Support have an
interoperability document for setting this kind of thing up, you
should probably ask for it.

andy

> Hi,
>
> Im using WebSphere 6.0.1 as a client and WebLogic 8.1 as my server. I want
to connect to weblogic with t3s-protocol.
>
> As a standalone, not running on websphere, the connection works fine. But
if I include my client to a WebSphere Portlet, I get the following error:
>
> [13.12.07 16:00:07:510 CET] 00000072 ServletWrappe E   SRVE0068E: Die
Methode service() für das Servlet StaticContentPortlet konnte nicht
aufgerufen werden. Ausgelöste Ausnahme: java.lang.NoClassDefFoundError:
weblogic/jndi/WLInitialContextFactoryDelegate 
> 	at weblogic.jndi.Environment.getContext(Environment.java:166)
> 	at weblogic.jndi.Environment.getInitialContext(Environment.java:145)
> 	at com.test.t3s.TwoWaySSL.init(Unknown Source)
> 	at com.test.portlet.StaticContentPortlet.doView(Unknown Source)
> 	at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:235)
> 	at javax.portlet.GenericPortlet.render(GenericPortlet.java:163)
> 	at
com.ibm.wps.pe.pc.std.cmpf.impl.PortletFilterChainImpl.render(PortletFilterChain
Impl.java:144)
> 	at
com.ibm.wps.pe.pc.std.invoker.impl.PortletServlet.dispatch(PortletServlet.java:1
30)
> 	at
com.ibm.wps.pe.pc.std.invoker.impl.PortletServlet.doGet(PortletServlet.java:69)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
> 	at
com.ibm.wps.pe.pc.std.cache.CacheablePortlet.service(CacheablePortlet.java:393)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
> 	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)

> 	at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java
(Compiled Code))
> 	at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDisp
atcher.java:670)
> 	at
com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.
java:204)
> 	at
com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.
java:168)
> 	at
com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.
java:97)
> 	at
com.ibm.wps.pe.pc.std.PortletContainerImpl.renderPortlet(PortletContainerImpl.ja
va:110)
> 	at
com.ibm.wps.pe.pc.PortletContainerImpl.doRenderPortlet(PortletContainerImpl.java
:587)
> 	at
com.ibm.wps.pe.ext.render.AbstractRenderManager.performService(AbstractRenderMan
ager.java:247)
> 	at
com.ibm.wps.pe.pc.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:1
15)
> 	at
com.ibm.wps.engine.tags.PortletRenderTag.doStartTag(PortletRenderTag.java:161)
> 	at
com.ibm._jsp._Control._jspx_meth_portal$1skin_portletRender_0(_Control.java:953)

> 	at com.ibm._jsp._Control._jspx_meth_portal$1logic_if_4(_Control.java:985)
> 	at com.ibm._jsp._Control._jspService(_Control.java:582)
>
> Has somebody an idea, why it runs as a standalone version and why it is not
running on WebSphere as a portlet?
>