You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Raghu Loganathan (JIRA)" <ji...@apache.org> on 2009/04/21 16:21:48 UTC

[jira] Created: (LOGGING-129) WebLogic 10.1 and Apache XML security and commons logging compatibility issue

WebLogic 10.1 and Apache XML security and commons logging compatibility issue
-----------------------------------------------------------------------------

                 Key: LOGGING-129
                 URL: https://issues.apache.org/jira/browse/LOGGING-129
             Project: Commons Logging
          Issue Type: Bug
    Affects Versions: 1.1.1
         Environment: Windows and Solaris 10
            Reporter: Raghu Loganathan


WebLogic 10.1, Java 5 & XML security compatibility issue. We have confirmed that we have the commons-logging-1.0.4.jar which has the LogFactory class in the WEB-INF/Lib directory.

Fails with the below error in the WL10.1/JDK 1.5_11 environment -

java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
	at org.apache.xml.security.Init.<clinit>(Unknown Source)
	at com.chase.treasury.ezpay.apps.efunds.topup.handlers.openSAMLSSOHandler.process(openSAMLSSOHandler.java:68)
	at com.chase.treasury.ezpay.apps.efunds.servlets.SSOServlet.dispatch(SSOServlet.java:231)
	at com.chase.treasury.ezpay.apps.efunds.servlets.SSOServlet.doPost(SSOServlet.java:79)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
	at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
	at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
	at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
	at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
	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) 



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (LOGGING-129) WebLogic 10.1 and Apache XML security and commons logging compatibility issue

Posted by "Joerg Schaible (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LOGGING-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701204#action_12701204 ] 

Joerg Schaible commented on LOGGING-129:
----------------------------------------

And then, why don't you use version 1.1.1 ?

> WebLogic 10.1 and Apache XML security and commons logging compatibility issue
> -----------------------------------------------------------------------------
>
>                 Key: LOGGING-129
>                 URL: https://issues.apache.org/jira/browse/LOGGING-129
>             Project: Commons Logging
>          Issue Type: Bug
>    Affects Versions: 1.0.4
>         Environment: Windows and Solaris 10
>            Reporter: Raghu Loganathan
>
> WebLogic 10.1, Java 5 & XML security compatibility issue. We have confirmed that we have the commons-logging-1.0.4.jar which has the LogFactory class in the WEB-INF/Lib directory.
> Fails with the below error in the WL10.1/JDK 1.5_11 environment -
> java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
> 	at org.apache.xml.security.Init.<clinit>(Unknown Source)
> 	at com.chase.treasury.ezpay.apps.efunds.topup.handlers.openSAMLSSOHandler.process(openSAMLSSOHandler.java:68)
> 	at com.chase.treasury.ezpay.apps.efunds.servlets.SSOServlet.dispatch(SSOServlet.java:231)
> 	at com.chase.treasury.ezpay.apps.efunds.servlets.SSOServlet.doPost(SSOServlet.java:79)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> 	at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
> 	at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
> 	at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
> 	at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
> 	at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
> 	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) 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (LOGGING-129) WebLogic 10.1 and Apache XML security and commons logging compatibility issue

Posted by "Joerg Schaible (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LOGGING-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joerg Schaible updated LOGGING-129:
-----------------------------------

    Affects Version/s:     (was: 1.1.1)
                       1.0.4

> WebLogic 10.1 and Apache XML security and commons logging compatibility issue
> -----------------------------------------------------------------------------
>
>                 Key: LOGGING-129
>                 URL: https://issues.apache.org/jira/browse/LOGGING-129
>             Project: Commons Logging
>          Issue Type: Bug
>    Affects Versions: 1.0.4
>         Environment: Windows and Solaris 10
>            Reporter: Raghu Loganathan
>
> WebLogic 10.1, Java 5 & XML security compatibility issue. We have confirmed that we have the commons-logging-1.0.4.jar which has the LogFactory class in the WEB-INF/Lib directory.
> Fails with the below error in the WL10.1/JDK 1.5_11 environment -
> java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
> 	at org.apache.xml.security.Init.<clinit>(Unknown Source)
> 	at com.chase.treasury.ezpay.apps.efunds.topup.handlers.openSAMLSSOHandler.process(openSAMLSSOHandler.java:68)
> 	at com.chase.treasury.ezpay.apps.efunds.servlets.SSOServlet.dispatch(SSOServlet.java:231)
> 	at com.chase.treasury.ezpay.apps.efunds.servlets.SSOServlet.doPost(SSOServlet.java:79)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> 	at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
> 	at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
> 	at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
> 	at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
> 	at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
> 	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) 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (LOGGING-129) WebLogic 10.1 and Apache XML security and commons logging compatibility issue

Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LOGGING-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg closed LOGGING-129.
-----------------------------------

    Resolution: Incomplete

No response from the author whether this works in  1.1.1 or not.

Please reopen if the problem exists in 1.1.1.

> WebLogic 10.1 and Apache XML security and commons logging compatibility issue
> -----------------------------------------------------------------------------
>
>                 Key: LOGGING-129
>                 URL: https://issues.apache.org/jira/browse/LOGGING-129
>             Project: Commons Logging
>          Issue Type: Bug
>    Affects Versions: 1.0.4
>         Environment: Windows and Solaris 10
>            Reporter: Raghu Loganathan
>
> WebLogic 10.1, Java 5 & XML security compatibility issue. We have confirmed that we have the commons-logging-1.0.4.jar which has the LogFactory class in the WEB-INF/Lib directory.
> Fails with the below error in the WL10.1/JDK 1.5_11 environment -
> java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
> 	at org.apache.xml.security.Init.<clinit>(Unknown Source)
> 	at com.chase.treasury.ezpay.apps.efunds.topup.handlers.openSAMLSSOHandler.process(openSAMLSSOHandler.java:68)
> 	at com.chase.treasury.ezpay.apps.efunds.servlets.SSOServlet.dispatch(SSOServlet.java:231)
> 	at com.chase.treasury.ezpay.apps.efunds.servlets.SSOServlet.doPost(SSOServlet.java:79)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> 	at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
> 	at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
> 	at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
> 	at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
> 	at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
> 	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) 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.