Can lifeRay work on Weblogic 10?

[Anônimo, modificado 16 Anos atrás.]

Can lifeRay work on Weblogic 10?

[Roman Hoyenko, modificado 16 Anos atrás.]

I believe it can. There were some issues with Weblogic having their own portlet container included with it, but I think people were able to overcome the problems.

[Mark Townsend, modificado 16 Anos atrás.]

I am trying to install LifeRay 4.4.2 on WebLogic Server 10 MP1 (10.0.0.1) and getting the following error messages.

On startup of the server:
Starting Liferay Enterprise Portal 4.4.2 (Spurgeon / Build 4402 / February 22, 2008)
11:03:36,665 INFO [DynamicDialect:79] Determining dialect for Oracle 10
11:03:36,712 INFO [DynamicDialect:102] Using dialect org.hibernate.dialect.Oracle10gDialect
11:03:57,962 INFO [PortalUtil:2317] Portal lib url C:/bea102/user_projects/domains/canes_liferay_domain/servers/AdminServer/tmp/_WL_user/liferay-portal-4/rlte6i/war/WEB-INF/lib/portal-impl.jar!/com/liferay/portal/util/PortalUtil.class
11:03:57,962 INFO [PortalUtil:2342] Portal lib directory C:/bea102/user_projects/domains/canes_liferay_domain/servers/AdminServer/tmp/_WL_user/liferay-portal-4/rlte6i/war/WEB-INF/lib/
11:03:58,087 INFO [PluginPackageHotDeployListener:71] Reading plugin package for the root context
Compiler warnings:
zip:C:/bea102/user_projects/domains/canes_liferay_domain/servers/AdminServer/tmp/_WL_user/liferay-portal-4/rlte6i/war/WEB-INF/lib/portletbridge-portlet.jar!/org/portletbridge/xsl/portletbridge.xsl: line 106: Attribute 'src' outside of element.
ERROR: 'The first argument to the non-static Java function 'equalsIgnoreCase' is not a valid object reference.'
FATAL ERROR: 'Could not compile stylesheet'
11:03:58,743 ERROR [MainServlet:205] java.lang.IllegalStateException: Could not compile stylesheet
java.lang.IllegalStateException: Could not compile stylesheet
at org.portletbridge.portlet.DefaultTemplateFactory.<init>(DefaultTemplateFactory.java:61)
at org.portletbridge.portlet.PortletBridgePortlet.init(PortletBridgePortlet.java:67)
at javax.portlet.GenericPortlet.init(GenericPortlet.java:85)
at com.liferay.portlet.CachePortlet.init(CachePortlet.java:191)
at com.liferay.portlet.PortletInstanceFactory._init(PortletInstanceFactory.java:211)
at com.liferay.portlet.PortletInstanceFactory._init(PortletInstanceFactory.java:191)
at com.liferay.portlet.PortletInstanceFactory._create(PortletInstanceFactory.java:108)
at com.liferay.portlet.PortletInstanceFactory.create(PortletInstanceFactory.java:53)
at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:201)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1853)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1750)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

On trying to go to http://localhost:7001 I get:
<Mar 19, 2008 11:05:34 AM PDT> <Error> <HTTP> <BEA-101020> <[weblogic.servlet.internal.WebAppServletContext@1b030d8 - appName: 'liferay-portal-4', name: 'liferay-portal-4.4.2.war', context-path: ''] Servlet failed with Exception
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
at org.apache.xml.security.Init.<clinit>(Unknown Source)
at org.openxri.xml.XRD.<clinit>(XRD.java:108)
at org.openid4java.discovery.Discovery.<init>(Discovery.java:53)
at org.openid4java.consumer.ConsumerManager.<init>(ConsumerManager.java:50)
at com.liferay.portal.util.OpenIdUtil.<init>(OpenIdUtil.java:79)
Truncated. see log file for complete stacktrace

Any ideas on what is missing? I went through all of the instructions that is in the LifeRay 4 Administration Guide.

Thanks,
Mark

[praveen kumar, modificado 16 Anos atrás.]

add log4j.jar to your weblogic global lib folder and the could not compile style sheet error is due to nonrecognitions of portletbridge.xsl file .im getting this error whenever i am running the weblogic server but no problem with running application.Its working fine.

[Mark Townsend, modificado 16 Anos atrás.]

praveen kumar:

add log4j.jar to your weblogic global lib folder and the could not compile style sheet error is due to nonrecognitions of portletbridge.xsl file .im getting this error whenever i am running the weblogic server but no problem with running application.Its working fine.

I tried that. I added the log4j-1.2.6.jar file to my WL_DOMAIN\lib directory where I put the liferay dependency jars. Could it be something to do with running the server from Eclipse that it isn't picking up that directory to add to the classpath. Wait, I know that it is because I tried deleting one of the jar files from there while the server was running and I couldn't.

Downloaded latest version of log4j and trying now. I'll let you know.

[Mark Townsend, modificado 16 Anos atrás.]

Tried putting commons-logging-1.1.jar and log4j.jar into the WL_DOMAIN/lib directory with now luck.

Looking into the liferay-portal-4.4.2.war file and it's WEB-INF/lib, I see that those jar files are already there.

However, I still get the error message. Here is the latest stack trace when I go to http://localhost:7001

java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
at org.apache.xml.security.Init.(Unknown Source)
at org.openxri.xml.XRD.(XRD.java:108)
at org.openid4java.discovery.Discovery.(Discovery.java:53)
at org.openid4java.consumer.ConsumerManager.(ConsumerManager.java:50)
at com.liferay.portal.util.OpenIdUtil.(OpenIdUtil.java:79)
at com.liferay.portal.util.OpenIdUtil.(OpenIdUtil.java:91)
at com.liferay.portal.security.auth.OpenIdAutoLogin.login(OpenIdAutoLogin.java:54)
at com.liferay.portal.servlet.filters.autologin.AutoLoginFilter.doFilter(AutoLoginFilter.java:78)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:98)
at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:149)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:98)
at com.liferay.portal.servlet.filters.sessionid.SessionIdFilter.doFilter(SessionIdFilter.java:78)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

[praveen kumar, modificado 16 Anos atrás.]

Hi

Dont use that war in weblogic use liferay-portal-4.4.2-with dependicies.war and use manual deployment . i am Sure it will work fine.....

[Mark Townsend, modificado 16 Anos atrás.]

praveen kumar:

Hi

Dont use that war in weblogic use liferay-portal-4.4.2-with dependicies.war and use manual deployment . i am Sure it will work fine.....

Praveen,

I have tried that with the same results. I am putting the war file into the autodeploy directory. I have also tried it deploying via the Console.

Any other thoughts? Are there settings when deploying that need to be set that are not mentioned in the Liferay documentation?

It would be a real coo if I can get this to work with WebLogic.

I'll post the full output of what happens also when the war file loads to see if there are any clues there as well.

Thanks,
Mark

Output below:

Loading zip:C:/bea102/user_projects/domains/canes_liferay_domain/servers/AdminSe
rver/tmp/_WL_user/liferay-portal-4/2ij29z/war/WEB-INF/lib/portal-impl.jar!/porta
l.properties
Starting Liferay Enterprise Portal 4.4.2 (Spurgeon / Build 4402 / February 22, 2
008)
09:15:23,284 INFO [DynamicDialect:79] Determining dialect for Oracle 10
09:15:23,316 INFO [DynamicDialect:102] Using dialect org.hibernate.dialect.Orac
le10gDialect
09:15:54,207 INFO [PortalUtil:2317] Portal lib url C:/bea102/user_projects/doma
ins/canes_liferay_domain/servers/AdminServer/tmp/_WL_user/liferay-portal-4/2ij29
z/war/WEB-INF/lib/portal-impl.jar!/com/liferay/portal/util/PortalUtil.class
09:15:54,207 INFO [PortalUtil:2342] Portal lib directory C:/bea102/user_project
s/domains/canes_liferay_domain/servers/AdminServer/tmp/_WL_user/liferay-portal-4
/2ij29z/war/WEB-INF/lib/
09:15:54,363 INFO [PluginPackageHotDeployListener:71] Reading plugin package fo
r the root context
Compiler warnings:
zip:C:/bea102/user_projects/domains/canes_liferay_domain/servers/AdminServer/t
mp/_WL_user/liferay-portal-4/2ij29z/war/WEB-INF/lib/portletbridge-portlet.jar!/o
rg/portletbridge/xsl/portletbridge.xsl: line 106: Attribute 'src' outside of ele
ment.
ERROR: 'The first argument to the non-static Java function 'equalsIgnoreCase' i
s not a valid object reference.'
FATAL ERROR: 'Could not compile stylesheet'
09:15:56,816 ERROR [MainServlet:205] java.lang.IllegalStateException: Could not
compile stylesheet
java.lang.IllegalStateException: Could not compile stylesheet
at org.portletbridge.portlet.DefaultTemplateFactory.<init>(DefaultTempla
teFactory.java:61)
at org.portletbridge.portlet.PortletBridgePortlet.init(PortletBridgePort
let.java:67)
at javax.portlet.GenericPortlet.init(GenericPortlet.java:85)
at com.liferay.portlet.CachePortlet.init(CachePortlet.java:191)
at com.liferay.portlet.PortletInstanceFactory._init(PortletInstanceFacto
ry.java:211)
at com.liferay.portlet.PortletInstanceFactory._init(PortletInstanceFacto
ry.java:191)
at com.liferay.portlet.PortletInstanceFactory._create(PortletInstanceFac
tory.java:108)
at com.liferay.portlet.PortletInstanceFactory.create(PortletInstanceFact
ory.java:53)
at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:201)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(St
ubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecuri
tyHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubL
ifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHel
per.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
mpl.java:507)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppS
ervletContext.java:1853)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(
WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAp
pServletContext.java:1750)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletCon
text.java:2909)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.jav
a:973)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
teDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
eDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedMod
uleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(Module
ListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
teDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
eDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartMod
ulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.ja
va:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.
java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(Deploym
entStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(Ap
pContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.ac
tivate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.ac
tivateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Commit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCom
mit(StartOperation.java:139)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.co
mmit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeplo
ymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(
DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.com
mit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
09:15:59,425 INFO [HotDeployUtil:76] Initializing hot deploy manager 15774211
09:15:59,472 INFO [ServerDetector:76] Detected server weblogic
09:16:01,363 INFO [AutoDeployDir:76] Auto deploy scanner started for C:\Documen
ts and Settings\mark.l.townsend\liferay\deploy
09:16:02,410 INFO [CustomSQLUtil:110] Database name Oracle
09:16:02,410 INFO [CustomSQLUtil:156] Detected Oracle with database name Oracle

Loading zip:C:/bea102/user_projects/domains/canes_liferay_domain/servers/AdminSe
rver/tmp/_WL_user/liferay-portal-4/2ij29z/war/WEB-INF/lib/portal-impl.jar!/porta
l.properties for {companyId=1, webId=liferay.com}
<Mar 25, 2008 9:17:35 AM PDT> <Error> <HTTP> <BEA-101020> <[weblogic.servlet.int
ernal.WebAppServletContext@4724ea - appName: 'liferay-portal-4', name: 'liferay-
portal-4.4.2-with-dependencies.war', context-path: ''] Servlet failed with Excep
tion
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
at org.apache.xml.security.Init.<clinit>(Unknown Source)
at org.openxri.xml.XRD.<clinit>(XRD.java:108)
at org.openid4java.discovery.Discovery.<init>(Discovery.java:53)
at org.openid4java.consumer.ConsumerManager.<init>(ConsumerManager.java:
50)
at com.liferay.portal.util.OpenIdUtil.<init>(OpenIdUtil.java:79)
Truncated. see log file for complete stacktrace
>

[praveen kumar, modificado 16 Anos atrás.]

Hi Townsend,

add the Commons-logging.jar in your weblogic domain/lib folder and try it.........

[Mark Townsend, modificado 16 Anos atrás.]

praveen kumar:

Hi Townsend,

add the Commons-logging.jar in your weblogic domain/lib folder and try it.........

I've tried adding it. I've tried adding log4j. I've tried adding both. commons-logging.jar is in the war file, so I don't even understand why it's needed anyway.

There is some strange classpath thing going on. Is there anyway that I can just disable the openid portlet? I don't need it at all.

[Mark Townsend, modificado 16 Anos atrás.]

Success!

In order to run Liferay 4.4.2 in WebLogic, you MUST put


<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>


in the weblogic.xml for the liferay 4.4.2 war file.

The only problem I seem to be having problems with now is that the xercesImpl.jar is being ignored and I get an error when trying to go to the Admin page.


11:14:40,837 ERROR [IncludeTag:52] Current URL /web/guest/admin generates except
ion: weblogic.servlet.jsp.CompilationException: Failed to compile JSP /html/port
al/portlet_access_denied.jsp
portlet_access_denied.jsp:1:1: The validator class: "org.apache.taglibs.standard
.tlv.JstlXmlTLV" has failed with the following exception: "java.lang.ClassCastEx
ception: weblogic.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^
portlet_access_denied.jsp:1:1: The validator class: "org.apache.taglibs.standard
.tlv.JstlSqlTLV" has failed with the following exception: "java.lang.ClassCastEx
ception: weblogic.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^
portlet_access_denied.jsp:1:1: The validator class: "org.apache.taglibs.standard
.tlv.JstlCoreTLV" has failed with the following exception: "java.lang.ClassCastE
xception: weblogic.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^
portlet_access_denied.jsp:1:1: The validator class: "org.apache.taglibs.standard
.tlv.JstlFmtTLV" has failed with the following exception: "java.lang.ClassCastEx
ception: weblogic.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^

11:14:40,852 ERROR [IncludeTag:52] weblogic.servlet.jsp.CompilationException: Fa
iled to compile JSP /html/portal/portlet_access_denied.jsp
portlet_access_denied.jsp:1:1: The validator class: "org.apache.taglibs.standard
.tlv.JstlXmlTLV" has failed with the following exception: "java.lang.ClassCastEx
ception: weblogic.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^
portlet_access_denied.jsp:1:1: The validator class: "org.apache.taglibs.standard
.tlv.JstlSqlTLV" has failed with the following exception: "java.lang.ClassCastEx
ception: weblogic.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^
portlet_access_denied.jsp:1:1: The validator class: "org.apache.taglibs.standard
.tlv.JstlCoreTLV" has failed with the following exception: "java.lang.ClassCastE
xception: weblogic.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^
portlet_access_denied.jsp:1:1: The validator class: "org.apache.taglibs.standard
.tlv.JstlFmtTLV" has failed with the following exception: "java.lang.ClassCastEx
ception: weblogic.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^

at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:165)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:235)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(Servlet
StubImpl.java:394)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:309)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(Request
DispatcherImpl.java:525)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispat
cherImpl.java:454)
at com.liferay.taglib.util.IncludeTag.doEndTag(IncludeTag.java:64)
at jsp_servlet._html._common._themes.__portlet._jsp__tag56(__portlet.jav
a:3544)
at jsp_servlet._html._common._themes.__portlet._jsp__tag55(__portlet.jav
a:3508)
at jsp_servlet._html._common._themes.__portlet._jspService(__portlet.jav
a:2310)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run
(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecuri
tyHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(Request
DispatcherImpl.java:525)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispat
cherImpl.java:454)
at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:163
)

11:14:49,446 ERROR [velocity:154] Method iconPortlet threw exception for referen
ce $theme in template _SERVLET_CONTEXT_/html/themes/classic/templates/portlet.vm
at [11,25]
<Mar 26, 2008 11:15:07 AM PDT> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.in
ternal.WebAppServletContext@11a9e33 - appName: '_appsdir_liferay-portal-4.4.2-wi
th-dependencies_dir', name: 'liferay-portal-4.4.2-with-dependencies', context-pa
th: ''] Root cause of ServletException.
weblogic.servlet.jsp.CompilationException: Failed to compile JSP /html/common/er
ror.jsp
error.jsp:1:1: The validator class: "org.apache.taglibs.standard.tlv.JstlXmlTLV"
has failed with the following exception: "java.lang.ClassCastException: weblogi
c.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^
error.jsp:1:1: The validator class: "org.apache.taglibs.standard.tlv.JstlSqlTLV"
has failed with the following exception: "java.lang.ClassCastException: weblogi
c.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^
error.jsp:1:1: The validator class: "org.apache.taglibs.standard.tlv.JstlCoreTLV
" has failed with the following exception: "java.lang.ClassCastException: weblog
ic.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^
error.jsp:1:1: The validator class: "org.apache.taglibs.standard.tlv.JstlFmtTLV"
has failed with the following exception: "java.lang.ClassCastException: weblogi
c.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^

at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(Unknown Source)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:165)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:235)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(Servlet
StubImpl.java:394)
Truncated. see log file for complete stacktrace
>

[praveen kumar, modificado 16 Anos atrás.]

Hi Townsend,

Actually i had deployed my liferay-portal-4.4.2 with dependencies.war in Manual deployment using weblogic domain console

i have done by gng http://localhost:7001/console url and i deployed it successfully.....dont put the war file in autodeploy folder...

[Mark Townsend, modificado 16 Anos atrás.]

praveen kumar:

Hi Townsend,

Actually i had deployed my liferay-portal-4.4.2 with dependencies.war in Manual deployment using weblogic domain console

i have done by gng http://localhost:7001/console url and i deployed it successfully.....dont put the war file in autodeploy folder...

I should say that I had no problem getting it deployed. However, trying to open the portal by going to http://localhost:7001 had many runtime errors. To get rid of the initial runtime errors you have to put the configuration in the weblogic.xml that I mentioned in my previous email. This forces WebLogic to use the jar files in the WEB-INF/lib and /classes. Otherwise, there are lots of collisions or something that prevents it from running.

As I said above, now when I try and go into the Admin tab, I get SAXFactory errors.

It is my opinion that Liferay 4.4.2 is NOT compatible with WebLogic 10.

[praveen kumar, modificado 16 Anos atrás.]

OfCourse townsend ,themes provided by liferay is also not working and portlet initializing also slow .....

[Mark Townsend, modificado 16 Anos atrás.]

praveen kumar:

OfCourse townsend ,themes provided by liferay is also not working and portlet initializing also slow .....

Praveen, et. al.

It seems that Liferay 4.4.2 only works with WebLogic Server 10.0.0.0 and NOT 10.0.0.1.

And you are correct, the themes don't seem to work and the portlets load extremely slow..

[praveen kumar, modificado 16 Anos atrás.]

TownSend,

Have you worked Liferay Portal with Acegi Security System ,if you have any ideas about this can you share with me?

[Plamen Petrov, modificado 15 Anos atrás.]

Hi,

Let's go back to the original question... Can lifeRay work on Weblogic 10?

I tried to deploy Liferay 5.0.1 on WebLogic 10.0. I downloaded the WAR file (Servlet 2.4) and the additional files
After fixing weblogic.xml (according to the instructions in this thread) to give priority to the local jars I started getting this compilation error:

An unexpected system error occurred.

weblogic.servlet.jsp.CompilationException: Failed to compile JSP /html/portal/render_portlet.jsp render_portlet.jsp:385:131: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlConfiguration = new PortletURLImpl(request, PortletKeys.PORTLET_CONFIGURATION, plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^ render_portlet.jsp:407:111: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlEdit = new PortletURLImpl(request, portletDisplay.getId(), plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^ render_portlet.jsp:430:119: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlEditDefaults = new PortletURLImpl(request, portletDisplay.getId(), plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^ render_portlet.jsp:453:116: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlEditGuest = new PortletURLImpl(request, portletDisplay.getId(), plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^ render_portlet.jsp:476:111: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlHelp = new PortletURLImpl(request, portletDisplay.getId(), plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^ render_portlet.jsp:499:35: Type javax.portlet.PortletRequest contains no field with this name. String lifecycle = PortletRequest.RENDER_PHASE; ^----------^ render_portlet.jsp:502:29: Type javax.portlet.PortletRequest contains no field with this name. lifecycle = PortletRequest.ACTION_PHASE; ^----------^ render_portlet.jsp:516:37: Type javax.portlet.PortletRequest contains no field with this name. if (lifecycle.equals(PortletRequest.RENDER_PHASE)) { ^----------^ render_portlet.jsp:554:112: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlPrint = new PortletURLImpl(request, portletDisplay.getId(), plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^

(sorry for the bad formating, but this is exactly how the message is displayed on the screen).
Please, note, that there is no javax.portlet.* in the WLS distribution, so it is not a question of having the wromg jar in the classpath.

I submitted it also as a bug report, LEP-5923.

Any ideas how to proceed?

Regards,
Plamen

[ora egozi barzilai, modificado 15 Anos atrás.]

Plamen Petrov:

Hi,

Let's go back to the original question... Can lifeRay work on Weblogic 10?

I tried to deploy Liferay 5.0.1 on WebLogic 10.0. I downloaded the WAR file (Servlet 2.4) and the additional files
After fixing weblogic.xml (according to the instructions in this thread) to give priority to the local jars I started getting this compilation error:
.........

I am not sure this is a real consolation.........
but I just did exactly the same you did except for one thing : I didnt change the weblogic.xml.

and it worked for me - my AS already has some jars(from previous installtion) but I dont think this is what solved the problem. so if you havent tried it yet, I would try deloying with the original weblogic.xml.

Ora

[Plamen Petrov, modificado 15 Anos atrás.]

Thanks Ora,

I tried deploying without modification of weblogic.xml, but then I get the ClassCastExcpetion mentioned earlier in that post:

weblogic.servlet.jsp.CompilationException: Failed to compile JSP /html/common/error.jsp
error.jsp:1:1: The validator class: "org.apache.taglibs.standard.tlv.JstlXmlTLV" has failed with the following exception: "java.lang.ClassCastException: weblogic.xml.jaxp.RegistrySAXParserFactory".
<%
^-
%>
-^

My weblogic isntallation is clean, "out-of-the box" download from BEA's web site.

Regards,
Plamen

[brad gilbert, modificado 15 Anos atrás.]

Has anyone been able to get Liferay 5.0.1 running on Weblogic 10 ? I've tried modifying weblogic.xml as described earlier in this thread, but I still get this error:

error.jsp:1:1: The validator class: "org.apache.taglibs.standard.tlv.JstlFmtTLV"
: "java.lang.ClassCastException: weblogic.xml.jaxp.RegistrySAXParserFactory".


I've tried getting Liferay to run on Weblogic 8.1 SP6 as well and the best I can do is get it to run, but it is extremely slow.

[The Meurwinn Concept, modificado 15 Anos atrás.]

Hi, we have exactly the same error log.

error.jsp:1:1: The validator class: "org.apache.taglibs.standard.tlv.JstlFmtTLV"
: "java.lang.ClassCastException: weblogic.xml.jaxp.RegistrySAXParserFactory".

Does anyone found the solution ?

Thank you.

[Manny Ortez, modificado 15 Anos atrás.]

Hi, I'm new to Liferay, but experienced this same problem when trying to deploy to Weblogic 10 MR1. The solution ultimately was to remove xml-apis.jar from the Liferay war file we were trying to deploy. That file is provided by the JDK that comes with Weblogic, and having a duplicate copy in the Liferay bundle caused this problem. Removing the one provided by Liferay seemed the simplest solution (and believe me, I tried many of the ones suggested here and elsewhere before that! .

One other crucial tip for WebLogic 10 if you are deploying an archive war file: add

		<show-archived-real-path-enabled>true</show-archived-real-path-enabled>

to your weblogic.xml. This compensates for the fact that context.getRealPath sometimes returns null on Weblogic when you deploy an archive war file. That's a problem for Liferay because it calls that function when it loads images and other startup stuff. There is a bunch of commentary on Weblogic's treatment of that function on the Internet. But we couldn't get Liferay completely working on WL10 until we set that setting.

[Ashley Mort, modificado 15 Anos atrás.]

Plamen Petrov:

Hi,

Let's go back to the original question... Can lifeRay work on Weblogic 10?

I tried to deploy Liferay 5.0.1 on WebLogic 10.0. I downloaded the WAR file (Servlet 2.4) and the additional files
After fixing weblogic.xml (according to the instructions in this thread) to give priority to the local jars I started getting this compilation error:

An unexpected system error occurred.

weblogic.servlet.jsp.CompilationException: Failed to compile JSP /html/portal/render_portlet.jsp render_portlet.jsp:385:131: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlConfiguration = new PortletURLImpl(request, PortletKeys.PORTLET_CONFIGURATION, plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^ render_portlet.jsp:407:111: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlEdit = new PortletURLImpl(request, portletDisplay.getId(), plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^ render_portlet.jsp:430:119: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlEditDefaults = new PortletURLImpl(request, portletDisplay.getId(), plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^ render_portlet.jsp:453:116: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlEditGuest = new PortletURLImpl(request, portletDisplay.getId(), plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^ render_portlet.jsp:476:111: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlHelp = new PortletURLImpl(request, portletDisplay.getId(), plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^ render_portlet.jsp:499:35: Type javax.portlet.PortletRequest contains no field with this name. String lifecycle = PortletRequest.RENDER_PHASE; ^----------^ render_portlet.jsp:502:29: Type javax.portlet.PortletRequest contains no field with this name. lifecycle = PortletRequest.ACTION_PHASE; ^----------^ render_portlet.jsp:516:37: Type javax.portlet.PortletRequest contains no field with this name. if (lifecycle.equals(PortletRequest.RENDER_PHASE)) { ^----------^ render_portlet.jsp:554:112: Type javax.portlet.PortletRequest contains no field with this name. PortletURLImpl urlPrint = new PortletURLImpl(request, portletDisplay.getId(), plid.longValue(), PortletRequest.RENDER_PHASE); ^----------^

(sorry for the bad formating, but this is exactly how the message is displayed on the screen).
Please, note, that there is no javax.portlet.* in the WLS distribution, so it is not a question of having the wromg jar in the classpath.

I submitted it also as a bug report, LEP-5923.

Any ideas how to proceed?

Regards,
Plamen

It's probably finding javax/portlet/PortletRequest.class from Weblogic's netuix_common.jar instead of Liferay's portlet.jar. Try getting netuix_common.jar out of your WebLogic classpath. I think netuix_common.jar is used by WebLogic Portal and/or WLI so maybe it's only present if you select certain components during WebLogic installation. That's probably why that other guy's WebLogic 10/Liferay5 setup works...he just selected different components (none of which use netuix_common.jar) upon WebLogic installation.

[Mike Robins, modificado 15 Anos atrás.]

Mark Townsend:

praveen kumar:

OfCourse townsend ,themes provided by liferay is also not working and portlet initializing also slow .....

Praveen, et. al.

It seems that Liferay 4.4.2 only works with WebLogic Server 10.0.0.0 and NOT 10.0.0.1.

And you are correct, the themes don't seem to work and the portlets load extremely slow..

You are correct about the problem affected 10MP1 and not 10.0.

After working with BEA support they eventually traced the cause and provided the following fix:

Add 'Class-Path: com.bea.core.apache.commons.logging.api_1.1.0.jar' to the MANIFEST.MF file in the 'com.bea.core.logging_1.0.1.0.jar' supplied with WebLogic.


Mike.

[The Meurwinn Concept, modificado 15 Anos atrás.]

Hi,
my Liferay 5.1.1 is now working on a Weblogic 10.0 !!!


So it was really hard.

I deployed an "ear" unzipped with a weblogic-application.xml descriptor to override the wml parser, and a lot of modifications.

But Weblogic has a strange class loader !

[test test test, modificado 15 Anos atrás.]

The Meurwinn Concept:

Hi,
my Liferay 5.1.1 is now working on a Weblogic 10.0 !!!


So it was really hard.

I deployed an "ear" unzipped with a weblogic-application.xml descriptor to override the wml parser, and a lot of modifications.

But Weblogic has a strange class loader !

Hi The Meurwinn Concept,

Can you PLEASE post your weblogic-application.xml to this forum. I would like to see how you got it to work!

I am having problems with conflicting classes and would like to implement the weblogic filter classloader to get Liferay 5.X running on Weblogic 10.

Or anyone else that has managed to get the packages in netuix_common.jar to not load. Setting <prefer-web-inf-classes> in weblogic.xml does not work. Please post your weblogic-application.xml files that managed to filter out the files that conflict with liferay.

Note: I have got liferay to work on weblogic 10, but I had to remove the jar file netuix_common.jar from my weblogic server, this isn't a good solution because then the weblogic console that relies on the portal classes in that jar file no longer works. I need to set it up so that my application filters these classes before loading the files with namespace conflicts.

This is what I have tried so far for my weblogic-application.xml:

<!--?xml version="1.0"?-->

<weblogic-application xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <prefer-application-packages>
    <package-name>javax.portlet.*</package-name> 
  </prefer-application-packages>

</weblogic-application>

Here is the error I get:

SEVERE: Current URL /web/guest/home generates exception: java.lang.NoSuchMethodError: javax.portlet.PortletResponse.getNa
mespace()Ljava/lang/String;
Dec 2, 2008 5:01:21 PM com.liferay.portal.log.CommonsLogImpl error
SEVERE: java.lang.NoSuchMethodError: javax.portlet.PortletResponse.getNamespace()Ljava/lang/String;




Thanks!!!

[The Meurwinn Concept, modificado 15 Anos atrás.]

Hi, i've try to install Liferay without EAR solution.

So :
- add dependancies in the domain lib
- create the datasource
- unzip the Liferay war file for tomcat
- add a weblogic.xml with prefer web inf classes to tru

And it works fine !

I don't know why it is working fine now because i've try it a lot of time... You don't need an ear. Only follow the Liferay Admin documentation.

Send us you error logs.

[test test test, modificado 15 Anos atrás.]

This is the error I get after adding a weblogic.xml with prefer web inf classes to true:


<Dec 3, 2008 11:09:06 AM CST> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.portal.container.service.Servi
ceManagerContextListenerImpl failed: java.lang.LinkageError: Class javax/xml/namespace/QName violates loader constraints.

java.lang.LinkageError: Class javax/xml/namespace/QName violates loader constraints
at com.sun.portal.container.service.coordination.impl.ContainerEventServiceImpl.initContainerEvents(ContainerEven
tServiceImpl.java:169)
at com.sun.portal.container.service.coordination.impl.ContainerEventServiceImpl.init(ContainerEventServiceImpl.ja
va:65)
at com.sun.portal.container.service.ServiceManager.addService(ServiceManager.java:128)
at com.sun.portal.container.service.ServiceManager.addStandardServices(ServiceManager.java:179)
at com.sun.portal.container.service.ServiceManager.init(ServiceManager.java:109)





Thanks.

[The Meurwinn Concept, modificado 15 Anos atrás.]

I had thisn error but i don't remember what was the solution.

Did you try to follow the documentation as i said in my previous post ?
We had a lot of problems with "class cast parsing exception". So we deploy xerces.jar as a library in the weblogic server and targeted it on our instance.

[praveen kumar, modificado 14 Anos atrás.]

Hi d g b,


I have deployed the liferay 5.2.3 in weblogic 10.3 successfully but i created the WAR from the Liferay5.2.3 source code. here is my weblogic.xml

Add the dependencies jars and
portlet-container.jar,portlet.jar,container.jar,annotations.jar to Weblogic AS domain lib directory.

if you are using weblogic10.3 use this weblogic.xml

<weblogic-web-app
xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd"
>
<jsp-descriptor>
<keepgenerated>true</keepgenerated>
<page-check-seconds>60</page-check-seconds>
<precompile>true</precompile>
<precompile-continue>true</precompile-continue>
</jsp-descriptor>
<container-descriptor>
<optimistic-serialization>true</optimistic-serialization>
<show-archived-real-path-enabled>true</show-archived-real-path-enabled>
</container-descriptor>
<context-root>/</context-root>
</weblogic-web-app>


if you want to use the previous version (i.e. weblogic 9.2) :

<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">

<weblogic-web-app>
<jsp-descriptor>
<jsp-param>
<param-name>keepgenerated</param-name>
<param-value>true</param-value>
</jsp-param>
<jsp-param>
<param-name>debug</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
<context-root>/</context-root>
</weblogic-web-app>



try the above and send me your replies.....