Issues with Attachments: week of 2012-06-25
CXF - Monday, June 25, 2012 4 Issues with Attachments (sorted oldest to newest) [CXF-4360] NPE in org.apache.cxf.interceptor.WrappedOutInterceptor when WS-RM is enabled - Created: 2012-06-06 - Updated: 2012-06-14 - Type: Bug - Fix Versions: [2.6.2, 2.7.0] - Reporter: Richard Opalka - Assigned: Aki Yoshida - Attachments: [CXF4360.patch, ReliableService.wsdl, cxf-4360.zip] - https://issues.apache.org/jira/browse/CXF-4360 [CXF-4368] LoggingInterceptors don't encourage reuse - Created: 2012-06-09 - Updated: 2012-06-09 - Type: Improvement - Fix Versions: [] - Reporter: Yaytay - Assigned: Unassigned - Attachments: [CXF-4368.diff] - https://issues.apache.org/jira/browse/CXF-4368 [CXF-4388] Using wsdl2java maven goal with and in the same pom fails - Created: 2012-06-19 - Updated: 2012-06-19 - Type: Bug - Fix Versions: [] - Reporter: Anders Olsson - Assigned: Unassigned - Attachments: [greeter.log, greeter.zip] - https://issues.apache.org/jira/browse/CXF-4388 [CXF-4392] Easier customization of log messages in Logging[In|Out]Interceptor - Created: 2012-06-22 - Updated: 2012-06-22 - Type: Improvement - Fix Versions: [] - Reporter: Tore Eide Andersen - Assigned: Unassigned - Attachments: [CXF-4392-customized-logging-format.patch] - https://issues.apache.org/jira/browse/CXF-4392
[jira] [Created] (CXF-4394) should add dependency='true' for spec bundles in cxf features.xml
Freeman Fang created CXF-4394: - Summary: should add dependency='true' for spec bundles in cxf features.xml Key: CXF-4394 URL: https://issues.apache.org/jira/browse/CXF-4394 Project: CXF Issue Type: Improvement Reporter: Freeman Fang should add dependency='true' for the spec bundles like jaxws-api/jaxb-api/saaj-api. So that it can work with obr resolver when OSGi container endorse jaxws-api/jaxb-api/saaj-api to prevent those bundles get installed from features.xml, hence we use the one from endorsed folder(in system bundle 0) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CXF-4394) should add dependency='true' for spec bundles in cxf features.xml
[ https://issues.apache.org/jira/browse/CXF-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-4394: - Assignee: Freeman Fang > should add dependency='true' for spec bundles in cxf features.xml > - > > Key: CXF-4394 > URL: https://issues.apache.org/jira/browse/CXF-4394 > Project: CXF > Issue Type: Improvement >Reporter: Freeman Fang >Assignee: Freeman Fang > > should add dependency='true' for the spec bundles like > jaxws-api/jaxb-api/saaj-api. So that it can work with obr resolver when OSGi > container endorse jaxws-api/jaxb-api/saaj-api to prevent those bundles get > installed from features.xml, hence we use the one from endorsed folder(in > system bundle 0) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4383) Some temporary files are not deleted after WS-RM scenarios
[ https://issues.apache.org/jira/browse/CXF-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-4383. -- Resolution: Fixed Fix Version/s: 2.6.2 2.5.5 2.4.9 > Some temporary files are not deleted after WS-RM scenarios > -- > > Key: CXF-4383 > URL: https://issues.apache.org/jira/browse/CXF-4383 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 2.4.8, 2.5.4, 2.6.1 >Reporter: Aki Yoshida >Assignee: Aki Yoshida > Fix For: 2.4.9, 2.5.5, 2.6.2 > > > Some of the temporary files created by CachedOuputStream in WS-RM scenarios > are not deleted and remain on the file system even under a normal completion > of the scenario (i.e., a successful transmission or a normal endpoint > shutdown). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4354) RMTxStore should explicitly close ResultSet objects
[ https://issues.apache.org/jira/browse/CXF-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-4354. -- Resolution: Fixed Fix Version/s: 2.6.2 2.5.5 2.4.9 > RMTxStore should explicitly close ResultSet objects > --- > > Key: CXF-4354 > URL: https://issues.apache.org/jira/browse/CXF-4354 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Reporter: Aki Yoshida >Assignee: Aki Yoshida > Fix For: 2.4.9, 2.5.5, 2.6.2 > > > RMTxStore should explicitly close the ResultSet objects to avoid any > potential memory issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4360) NPE in org.apache.cxf.interceptor.WrappedOutInterceptor when WS-RM is enabled
[
https://issues.apache.org/jira/browse/CXF-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida resolved CXF-4360.
--
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.7.0)
(was: 2.6.2)
Hi Richard,
As I noted in my previous comment, I was not able to reproduce the problem
using your example (the unit test maven project attached) and requested your
feedback.
Since I haven't heard from you, I would like to mark this issue as "cannot
reproduce".
Please reopen this issue when you have a concrete test case that demonstrates
this problem.
Regards, Aki
> NPE in org.apache.cxf.interceptor.WrappedOutInterceptor when WS-RM is enabled
> -
>
> Key: CXF-4360
> URL: https://issues.apache.org/jira/browse/CXF-4360
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
>Affects Versions: 2.6.1
> Environment: Reproducible on every environment.
>Reporter: Richard Opalka
>Assignee: Aki Yoshida
> Attachments: CXF4360.patch, ReliableService.wsdl, cxf-4360.zip
>
>
> 09:52:29,353 WARNING [org.apache.cxf.phase.PhaseInterceptorChain]
> (http-localhost/127.0.0.1:8080-1) Interceptor for
> {http://www.jboss.org/jbossws/ws-extensions/wsrm}ReliableService#{http://www.jboss.org/jbossws/ws-extensions/wsrm}writeLogMessage
> has thrown exception, unwinding now: java.lang.NullPointerException
> at
> org.apache.cxf.interceptor.WrappedOutInterceptor.handleMessage(WrappedOutInterceptor.java:65)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at
> org.apache.cxf.ws.addressing.impl.InternalContextUtils.rebaseResponse(InternalContextUtils.java:156)
> at
> org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl.mediate(MAPAggregatorImpl.java:467)
> at
> org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl.handleMessage(MAPAggregatorImpl.java:141)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:122)
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:211)
> at
> org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:91)
> at
> org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:187)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:110)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
> [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final]
> at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
> [jbossws-spi-2.1.0.Beta1.jar:2.1.0.Beta1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
> [jbossweb-7.0.16.Final.jar:]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
> [jbossweb-7.0.16.Final.jar:]
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
> [jbossweb-7.0.16.Final.jar:]
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
> [jbossweb-7.0.16.Final.jar:]
> at
> org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:156)
> [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
> [jbossweb-7.0.16.Final.jar:]
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> [jbossweb-7.0.16.Final.jar:]
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> [jbossweb-7.0.16.Final.jar:]
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
> [jbossweb-7.0.16.Final.jar:]
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
> [jbossweb-7.0.16.Final.jar:]
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
> [jbossweb-7.0.16.Final.jar:]
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.jav
[jira] [Resolved] (CXF-4394) should add dependency='true' for spec bundles in cxf features.xml
[ https://issues.apache.org/jira/browse/CXF-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-4394. --- Resolution: Fixed Fix Version/s: 2.7.0 2.6.2 2.5.5 2.4.9 commit fix http://svn.apache.org/viewvc?rev=1353452&view=rev for trunk http://svn.apache.org/viewvc?rev=1353489&view=rev for 2.6.x branch http://svn.apache.org/viewvc?rev=1353491&view=rev for 2.5.x branch http://svn.apache.org/viewvc?rev=1353492&view=rev for 2.4.x branch > should add dependency='true' for spec bundles in cxf features.xml > - > > Key: CXF-4394 > URL: https://issues.apache.org/jira/browse/CXF-4394 > Project: CXF > Issue Type: Improvement >Reporter: Freeman Fang >Assignee: Freeman Fang > Fix For: 2.4.9, 2.5.5, 2.6.2, 2.7.0 > > > should add dependency='true' for the spec bundles like > jaxws-api/jaxb-api/saaj-api. So that it can work with obr resolver when OSGi > container endorse jaxws-api/jaxb-api/saaj-api to prevent those bundles get > installed from features.xml, hence we use the one from endorsed folder(in > system bundle 0) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4325) ws?js not working with Spring based config in JBoss 7.1
[ https://issues.apache.org/jira/browse/CXF-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401075#comment-13401075 ] Charmine Azajar commented on CXF-4325: -- Timothy, can you help share the pom.xml file? Can you also provide the sample link you were using to check that the problem was resolved. Thanks. > ws?js not working with Spring based config in JBoss 7.1 > --- > > Key: CXF-4325 > URL: https://issues.apache.org/jira/browse/CXF-4325 > Project: CXF > Issue Type: Bug > Components: JavaScript Client, JAX-WS Runtime >Affects Versions: 2.6 > Environment: Linux + JBoss 7.1 > project in Netbeans 7.1.2. Simple WAR (clean project) >Reporter: Timothy Heider >Priority: Minor > Fix For: NeedMoreInfo > > > I have everything working except for the one thing I really want: ?js code > rendering. It returns this: > http://schemas.xmlsoap.org/soap/envelope/";> > > > soap:Server > > No such operation: null (HTTP GET PATH_INFO: /pbx/pbxnull) > > > > > which is the same as if the JS wasn't hooked in at all. > Here is my beans.xml file: > http://www.springframework.org/schema/beans"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:jaxws="http://cxf.apache.org/jaxws"; > xmlns:jaxrs="http://cxf.apache.org/jaxrs"; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-2.0.xsd > http://cxf.apache.org/jaxws > http://cxf.apache.org/schemas/jaxws.xsd > http://cxf.apache.org/jaxrs > http://cxf.apache.org/schemas/jaxrs.xsd";> > > > >resource="classpath:META-INF/cxf/cxf-extension-javascript-client.xml"/> > implementor="realise.pbx.core.PbxCoreImpl" > address="/pbx"/> > > I am able to get wsdl's by ?wsdl and execute services using > JaxWsProxyFactoryBean. > The beverages sample works with the same jar's to generate JS so I know the > feature works. I'm somewhat baffled. I built the 2.6.0 source today but I > thought before I dig in too much more I would see if you knew about something > like this already being a problem. > Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
