You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Rich Barndt (JIRA)" <ji...@apache.org> on 2011/06/16 13:49:47 UTC
[jira] [Created] (CXF-3595) CXF 2.4.X WebLogic 10.3.4 or 10.3.5
when processing WS-Sec
CXF 2.4.X WebLogic 10.3.4 or 10.3.5 when processing WS-Sec
----------------------------------------------------------
Key: CXF-3595
URL: https://issues.apache.org/jira/browse/CXF-3595
Project: CXF
Issue Type: Bug
Components: WS-* Components
Environment: Oracle WebLogic 10.3.4 or 10.3.5
Reporter: Rich Barndt
Priority: Blocker
When processing security headers after the CXF-3307 fix. Any version of cxf 2.3.4 or > seems to get this same error if I fall back to cxf 2.3.3 the error goes away.... The error is below in weblogic:
java.lang.AssertionError: UNIMPLEMENTED
at weblogic.xml.domimpl.NodeImpl.setPrefix(NodeImpl.java:173)
at org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:968)
at org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:947)
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:157)
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:118)
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:208)
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:205)
at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:113)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:184)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:163)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3717)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Maybe there is setting I am missing I did set<entry key="ws-security.ut.no-callbacks" value="false" /> I am processing JAX-WS endpoints using spring 3.0.5 CXF 2.3.4, 2.3.5 or 2.4 or 2.4.1 all seem to have the same result.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3595) CXF 2.4.X WebLogic 10.3.4 or 10.3.5
when processing WS-Sec
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-3595.
------------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
Assignee: Daniel Kulp
I'm marking this as "Won't fix". I started trying to see if I could remove the call to setPrefix, but it's called all over the place with many spots in CXF, a couple in Neethi, a few in OpenSAML, XmlSchema, etc....
The setPrefix call is required for DOM level 2 compliance which is what CXF requires. (in some cases, CXF need DOM level 3). I would suggest adding a very recent xercesImpl jar to your application or similar to see if you can get a fully compliant DOM implementation to be used. And log a bug with Weblogic.... :-)
> CXF 2.4.X WebLogic 10.3.4 or 10.3.5 when processing WS-Sec
> ----------------------------------------------------------
>
> Key: CXF-3595
> URL: https://issues.apache.org/jira/browse/CXF-3595
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Environment: Oracle WebLogic 10.3.4 or 10.3.5
> Reporter: Rich Barndt
> Assignee: Daniel Kulp
> Priority: Blocker
> Fix For: Invalid
>
>
> When processing security headers after the CXF-3307 fix. Any version of cxf 2.3.4 or > seems to get this same error if I fall back to cxf 2.3.3 the error goes away.... The error is below in weblogic:
> java.lang.AssertionError: UNIMPLEMENTED
> at weblogic.xml.domimpl.NodeImpl.setPrefix(NodeImpl.java:173)
> at org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:968)
> at org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:947)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:157)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:118)
> at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:208)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
> at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:205)
> at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:113)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:184)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:107)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:163)
> at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
> at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
> at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
> at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
> at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3717)
> at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
> at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
> at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
> at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
> at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
> Maybe there is setting I am missing I did set<entry key="ws-security.ut.no-callbacks" value="false" /> I am processing JAX-WS endpoints using spring 3.0.5 CXF 2.3.4, 2.3.5 or 2.4 or 2.4.1 all seem to have the same result.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira