[jira] [Updated] (CXF-3424) LoadDistributorFeature for CXF
[ https://issues.apache.org/jira/browse/CXF-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaytay updated CXF-3424: Attachment: LoadDistributor1.diff Patch attached. A full build fails tests in jax-rs, but they seem to be failing anyway, without my code. This version does not attempt to establish an Exchange-independent list of endpoints to distribute between (whereas it does attempt to establish an Exchange-independent list of addresses). It would be possible to modify AbstractStaticFailoverStrategy to cache the endpoint list and return that if a null Exchange is passed to getAlternateEndpoints, but I'm not sure about the validity of doing so and I'm only going to use it with multiple addresses :) Any comments gratefully received. > LoadDistributorFeature for CXF > -- > > Key: CXF-3424 > URL: https://issues.apache.org/jira/browse/CXF-3424 > Project: CXF > Issue Type: New Feature > Components: Core >Affects Versions: 2.3.3 >Reporter: Yaytay >Priority: Minor > Attachments: LoadDistributor1.diff > > > The FailoverTargetSelector in CXF takes effect only when a transport failure > occurs, so it provides no way to spread the load across a number of addresses > or endpoints. > By subclassing the FailoverTargetSelector and the FailoverFeature it is > possible to provide a load distributor that works for most circumstances. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[
https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011951#comment-13011951
]
Ivan Vitoria commented on CXF-3418:
---
Hi Sergey,
It works, it's amazing!
I've needed to add the other context elements because an exception was thrown.
The new interface looks like this:
public interface IContext {
@Context
void setUriInfo(UriInfo uriInfo);
@Context
void setMessageContext(MessageContext mc);
@Context
void setServletContext(ServletContext sc);
}
Many thanks, again.
Best regards,
Ivan
> Transactional JAX-RS Service (Spring 3 + Hibernate 3)
> -
>
> Key: CXF-3418
> URL: https://issues.apache.org/jira/browse/CXF-3418
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.3.2
>Reporter: Ivan Vitoria
>Priority: Critical
> Attachments: JaxrsTransactional.part1.rar,
> JaxrsTransactional.part2.rar
>
>
> Hello,
> I have some JAX-RS servers configured through Spring. Also, i'm using
> Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no
> problem when I add the @Transactional annotation to the DAO layer, but i
> would like to have the REST methods in the same transaction, so i've annoated
> the services. But I can't do it, neither annotating the interface nor the
> classes. A ServiceConstructionException is throwed as soon as I add the
> @Transactional to the service...
> A sample NetBeans project is attached.
> Thanks in advance
> Ivan
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Issues with Attachments: week of 2011-03-28
CXF - Monday, March 28, 2011 6 Issues with Attachments (sorted oldest to newest) [CXF-1940] WS-Trust support in CXF - Created: 2008-12-11 - Updated: 2011-03-24 - Type: Task - Fix Versions: [] - Reporter: Mayank Mishra - Assigned: Unassigned - Attachments: [BinarySecret.java, Entropy.java, RequestSecurityToken.java, RequestSecurityTokenResponse.java, STS.java, STSClient27Jan.patch, STSImpl.java, SecurityConstants.java, model.zip, sts_provider.zip, sts_provider2.zip, sts_provider3.zip] - https://issues.apache.org/jira/browse/CXF-1940 [CXF-2716] Collection Support for JSONProvider - Created: 2010-03-15 - Updated: 2011-03-21 - Type: Improvement - Fix Versions: [] - Reporter: Uttam Phalnikar - Assigned: Unassigned - Attachments: [JSONProvider.java, JSONUtils.java, json-collections.patch, patch.txt] - https://issues.apache.org/jira/browse/CXF-2716 [CXF-3366] Avoid parsing the SOAP Body to DOM in WS-Security processing unless necessary - Created: 2011-02-25 - Updated: 2011-03-10 - Type: Improvement - Fix Versions: [2.4] - Reporter: Colm O hEigeartaigh - Assigned: Colm O hEigeartaigh - Attachments: [cxf-3366-example.patch, cxf-3366.patch, newpatch.txt] - https://issues.apache.org/jira/browse/CXF-3366 [CXF-3405] Error reading XMLStreamReader. - Created: 2011-03-16 - Updated: 2011-03-17 - Type: Bug - Fix Versions: [NeedMoreInfo] - Reporter: Prasad Deshpande - Assigned: Unassigned - Attachments: [TestApplet.java, TestWSServerHandler.java, WSTestService.java, WSTestServiceImpl.java] - https://issues.apache.org/jira/browse/CXF-3405 [CXF-3418] Transactional JAX-RS Service (Spring 3 + Hibernate 3) - Created: 2011-03-24 - Updated: 2011-03-28 - Type: Bug - Fix Versions: [] - Reporter: Ivan Vitoria - Assigned: Unassigned - Attachments: [JaxrsTransactional.part1.rar, JaxrsTransactional.part2.rar] - https://issues.apache.org/jira/browse/CXF-3418 [CXF-3424] LoadDistributorFeature for CXF - Created: 2011-03-26 - Updated: 2011-03-28 - Type: New Feature - Fix Versions: [] - Reporter: Yaytay - Assigned: Unassigned - Attachments: [LoadDistributor1.diff] - https://issues.apache.org/jira/browse/CXF-3424
[jira] [Resolved] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-3418. --- Resolution: Not A Problem Moving Context setters to the dedicated interface fixes the problem > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > Attachments: JaxrsTransactional.part1.rar, > JaxrsTransactional.part2.rar > > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Vitoria reopened CXF-3418: --- Hi Sergey, I've noticed that if other class extends from GenericRestServiceImpl the MessageContext is not injected! However both ServletContext and UriInfo are correctly injected. Let me know if you need extra information. Regards, Ivan > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > Attachments: JaxrsTransactional.part1.rar, > JaxrsTransactional.part2.rar > > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[
https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011994#comment-13011994
]
Sergey Beryozkin commented on CXF-3418:
---
So, you have the following case.
{code}
public interface IContext {
@Context void setUriInfo(UriInfo uriInfo);
@Context void setMessageContext(MessageContext mc);
@Context void setServletContext(ServletContext sc); }
{code}
{code}
public class GenericRestServiceImpl implements IRestService, IContext {
}
public class GenericRestServiceImpl2 extends GenericRestServiceImpl {
}
{code}
and only MessageContext is not injected ?
Can you double check please ? Have you updated the model to reference the
IRestService interface only ?
> Transactional JAX-RS Service (Spring 3 + Hibernate 3)
> -
>
> Key: CXF-3418
> URL: https://issues.apache.org/jira/browse/CXF-3418
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.3.2
>Reporter: Ivan Vitoria
>Priority: Critical
> Attachments: JaxrsTransactional.part1.rar,
> JaxrsTransactional.part2.rar
>
>
> Hello,
> I have some JAX-RS servers configured through Spring. Also, i'm using
> Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no
> problem when I add the @Transactional annotation to the DAO layer, but i
> would like to have the REST methods in the same transaction, so i've annoated
> the services. But I can't do it, neither annotating the interface nor the
> classes. A ServiceConstructionException is throwed as soon as I add the
> @Transactional to the service...
> A sample NetBeans project is attached.
> Thanks in advance
> Ivan
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3413) IndexOutOfBoundsException in DocLiteralInInterceptor
[
https://issues.apache.org/jira/browse/CXF-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011995#comment-13011995
]
Andreas Gudian commented on CXF-3413:
-
The server side is a webMethods 7.x integration server.
I had to anonymize the WSDL a bit, the real one had some more operations, types
and elements, and different namespaces, service name and port name.
{code:xml}
http://schemas.xmlsoap.org/wsdl/";
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap12/";
xmlns:tns="http://www.xxx.yy/zzz";
xmlns:xmime="http://www.w3.org/2005/05/xmlmime";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsd1="http://www.xxx.yy/zzz/types/"; name="zzz.wsdl"
targetNamespace="http://www.xxx.yy/zzz";>
http://www.w3.org/2001/XMLSchema";
targetNamespace="http://www.xxx.yy/zzz/types/";>
http://www.w3.org/2005/05/xmlmime";
name="pdfPayload" type="xsd:base64Binary"
xmime:expectedContentTypes="application/octet-stream"/>
http://www.w3.org/2001/XMLSchema"; name="sendData">
http://www.w3.org/2001/XMLSchema";
name="authenticationHeaderType">
http://www.w3.org/2001/XMLSchema";
name="authentication" nillable="true" type="xsd1:authenticationHeaderType"/>
http://www.w3.org/2001/XMLSchema";
name="GeneratePreviewResponse">
...
http://schemas.xmlsoap.org/soap/http"/>
http://schemas.xmlsoap.org/ws/2004/09/policy"; URI="#wsmtom_policy"
required="true"/>
http://xxx/yyy"/>
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";
wsu:Id="wsmtom_policy">
http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization"/>
{code}
Please note that the response is not valid as far as the schema is concerned
(two mandatory elements are missing). However, I expected a validation
exception from JAXB for this (validation is turned on in my client).
> IndexOutOfBoundsException in DocLiteralInInterceptor
>
>
> Key: CXF-3413
> URL: https://issues.apache.org/jira/browse/CXF-3413
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.3.3
>Reporter: Andreas Gudian
>
> I am receiving the following response from a web service that I call using
> CXF 2.3.3:
> {code:xml}
>
> http://www.w3.org/2003/05/soap-envelope";
> xmlns:xml="http://www.w3.org/XML/1998/namespace";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> http://www.w3.org/2003/05/soap-envelope";
> xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding";>
> xmlns:xsd1="http://www.xxx.yy/zzz/types/";>-1
> http://www.xxx.yy/zzz/types/";>Some Status
> Message
> http://www.xxx.yy/zzz/types/";>
>
>
> {code}
> This results in the following exception:
> {code}
> java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> at java.util.ArrayList.get(ArrayList.java:322)
> at
> org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:188)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:755)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2335)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2193)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2037)
> at
> org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:47)
> at
> org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:188)
> at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:697)
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
>
[jira] [Commented] (CXF-3422) 'Cannot find target method' when certain hex-encoded characters are used in @PathParam in GET requests
[
https://issues.apache.org/jira/browse/CXF-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012001#comment-13012001
]
Karel Vlcek commented on CXF-3422:
--
Hi, yes, I confirm that it works correctly with 2.3.4-SNAPSHOT.
Thank you,
Karel
> 'Cannot find target method' when certain hex-encoded characters are used in
> @PathParam in GET requests
> --
>
> Key: CXF-3422
> URL: https://issues.apache.org/jira/browse/CXF-3422
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.3.1, 2.3.3
> Environment: Tomcat 6
>Reporter: Karel Vlcek
>Priority: Minor
>
> I have following simple JAX-RS service:
> {code}
> public interface RootService {
> @Path("data1")
> public DataService getDataService();
> }
> public interface DataService {
> @GET
> @Path("data2/{id}")
> public Data getData(@PathParam("id") String id);
> }
> {code}
> All works correctly as long as URL contains in position of @PathParam("id")
> ASCII characters and digits or hex-encoded spaces. These URLs work:
> GET /root/data1/data2/1
> GET /root/data1/data2/AAA2BBB
> GET /root/data1/data2/1%202
> However, when URL on position of the parameter {id} contains certain
> hex-encoded characters other than space (%20), like in this URL (this example
> contains digit '1' followed by 'latin capital letter d with caron'):
> GET /root/data1/data2/1%C4%8E
> I'll get following exception:
> {noformat}
> javax.ws.rs.WebApplicationException
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:399)
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:204)
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113)
> at
> org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:149)
> at
> org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:148)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
> {code}
> //
> // Simple implementations - just to complete the example...
> public class RootServiceImpl implements RootService {
> @Override
> public DataService getDataService() {
> return new DataServiceImpl();
> }
> }
> public class DataServiceImpl implements DataService {
> @Override
> public Data getData(final String id) {
> // ...
> }
> }
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[
https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012003#comment-13012003
]
Ivan Vitoria commented on CXF-3418:
---
Sorry, the three context elements were not been injected instead of just
MessageContext. My fault!
The problem was that the inherited class needed an explicit interface due to
the new methods, and this interface must be added to the new model.
{code:xml}
public class GenericRestServiceImpl2 extends GenericRestServiceImpl implements
IExtraBehaviour {
public void extraMethod() {...}
}
@Transactional
public interface IExtraBehaviour {
void extraMethod();
}
http://cxf.apache.org/jaxrs";>
{code}
> Transactional JAX-RS Service (Spring 3 + Hibernate 3)
> -
>
> Key: CXF-3418
> URL: https://issues.apache.org/jira/browse/CXF-3418
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.3.2
>Reporter: Ivan Vitoria
>Priority: Critical
> Attachments: JaxrsTransactional.part1.rar,
> JaxrsTransactional.part2.rar
>
>
> Hello,
> I have some JAX-RS servers configured through Spring. Also, i'm using
> Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no
> problem when I add the @Transactional annotation to the DAO layer, but i
> would like to have the REST methods in the same transaction, so i've annoated
> the services. But I can't do it, neither annotating the interface nor the
> classes. A ServiceConstructionException is throwed as soon as I add the
> @Transactional to the service...
> A sample NetBeans project is attached.
> Thanks in advance
> Ivan
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012005#comment-13012005 ] Sergey Beryozkin commented on CXF-3418: --- Hi - so can this issue be resolved again :-) ? Also if you have IExtraBehaviour extending IRestService then it should also work > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > Attachments: JaxrsTransactional.part1.rar, > JaxrsTransactional.part2.rar > > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3422) 'Cannot find target method' when certain hex-encoded characters are used in @PathParam in GET requests
[
https://issues.apache.org/jira/browse/CXF-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012006#comment-13012006
]
Sergey Beryozkin commented on CXF-3422:
---
Hi Karel, many thanks.
one possible problem was that Tomcat itself was not handling some of those
characters properly, and it in turn was exposing the brittleness of the
workaround to do with keeping the matrix params...
Either way, thanks for confirming it works with the snapshots
Cheers, Sergey
> 'Cannot find target method' when certain hex-encoded characters are used in
> @PathParam in GET requests
> --
>
> Key: CXF-3422
> URL: https://issues.apache.org/jira/browse/CXF-3422
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.3.1, 2.3.3
> Environment: Tomcat 6
>Reporter: Karel Vlcek
>Priority: Minor
> Fix For: 2.4, 2.3.4
>
>
> I have following simple JAX-RS service:
> {code}
> public interface RootService {
> @Path("data1")
> public DataService getDataService();
> }
> public interface DataService {
> @GET
> @Path("data2/{id}")
> public Data getData(@PathParam("id") String id);
> }
> {code}
> All works correctly as long as URL contains in position of @PathParam("id")
> ASCII characters and digits or hex-encoded spaces. These URLs work:
> GET /root/data1/data2/1
> GET /root/data1/data2/AAA2BBB
> GET /root/data1/data2/1%202
> However, when URL on position of the parameter {id} contains certain
> hex-encoded characters other than space (%20), like in this URL (this example
> contains digit '1' followed by 'latin capital letter d with caron'):
> GET /root/data1/data2/1%C4%8E
> I'll get following exception:
> {noformat}
> javax.ws.rs.WebApplicationException
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:399)
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:204)
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113)
> at
> org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:149)
> at
> org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:148)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
> {code}
> //
> // Simple implementations - just to complete the example...
> public class RootServiceImpl implements RootService {
> @Override
> public DataService getDataService() {
> return new DataServiceImpl();
> }
> }
> public class DataServiceImpl implements DataService {
> @Override
> public Data getData(final String id) {
> // ...
> }
> }
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3422) 'Cannot find target method' when certain hex-encoded characters are used in @PathParam in GET requests
[
https://issues.apache.org/jira/browse/CXF-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin resolved CXF-3422.
---
Resolution: Fixed
Fix Version/s: 2.3.4
2.4
Assignee: Sergey Beryozkin
Resolved in the snapshots
> 'Cannot find target method' when certain hex-encoded characters are used in
> @PathParam in GET requests
> --
>
> Key: CXF-3422
> URL: https://issues.apache.org/jira/browse/CXF-3422
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.3.1, 2.3.3
> Environment: Tomcat 6
>Reporter: Karel Vlcek
>Assignee: Sergey Beryozkin
>Priority: Minor
> Fix For: 2.4, 2.3.4
>
>
> I have following simple JAX-RS service:
> {code}
> public interface RootService {
> @Path("data1")
> public DataService getDataService();
> }
> public interface DataService {
> @GET
> @Path("data2/{id}")
> public Data getData(@PathParam("id") String id);
> }
> {code}
> All works correctly as long as URL contains in position of @PathParam("id")
> ASCII characters and digits or hex-encoded spaces. These URLs work:
> GET /root/data1/data2/1
> GET /root/data1/data2/AAA2BBB
> GET /root/data1/data2/1%202
> However, when URL on position of the parameter {id} contains certain
> hex-encoded characters other than space (%20), like in this URL (this example
> contains digit '1' followed by 'latin capital letter d with caron'):
> GET /root/data1/data2/1%C4%8E
> I'll get following exception:
> {noformat}
> javax.ws.rs.WebApplicationException
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:399)
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:204)
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:88)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113)
> at
> org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:461)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:149)
> at
> org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:148)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
> {code}
> //
> // Simple implementations - just to complete the example...
> public class RootServiceImpl implements RootService {
> @Override
> public DataService getDataService() {
> return new DataServiceImpl();
> }
> }
> public class DataServiceImpl implements DataService {
> @Override
> public Data getData(final String id) {
> // ...
> }
> }
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012011#comment-13012011 ] Ivan Vitoria commented on CXF-3418: --- Hi, Yes this issue is completely resolved :D. It would be interesting if there was inheritance in the definition of the models, such as the "parent" atribute of Spring... Thank you for your time Sergey! Regards, Ivan > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > Attachments: JaxrsTransactional.part1.rar, > JaxrsTransactional.part2.rar > > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3418) Transactional JAX-RS Service (Spring 3 + Hibernate 3)
[ https://issues.apache.org/jira/browse/CXF-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-3418. --- Resolution: Not A Problem thanks > Transactional JAX-RS Service (Spring 3 + Hibernate 3) > - > > Key: CXF-3418 > URL: https://issues.apache.org/jira/browse/CXF-3418 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.3.2 >Reporter: Ivan Vitoria >Priority: Critical > Attachments: JaxrsTransactional.part1.rar, > JaxrsTransactional.part2.rar > > > Hello, > I have some JAX-RS servers configured through Spring. Also, i'm using > Hibernate DAOs and the OpenSessionInViewFilter of Spring-ORM. I have no > problem when I add the @Transactional annotation to the DAO layer, but i > would like to have the REST methods in the same transaction, so i've annoated > the services. But I can't do it, neither annotating the interface nor the > classes. A ServiceConstructionException is throwed as soon as I add the > @Transactional to the service... > A sample NetBeans project is attached. > Thanks in advance > Ivan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-3428) Context closed twice with Spring setup
Context closed twice with Spring setup
--
Key: CXF-3428
URL: https://issues.apache.org/jira/browse/CXF-3428
Project: CXF
Issue Type: Bug
Affects Versions: 2.3.3, 2.3.2
Environment: Windows 7, Java 5 and 6
Reporter: Anders Båtstrand
Attachments: context-bug.zip
See the enclosed project (very minimal).
I have a cxf.cml and an applicationContext.xml, and loads both using
ContextLoaderListener in my web.xml. I have also a CXFServlet. Starting this
with Jetty, I get the following exception when I stop the server:
{code}
28.mar.2011 23:43:15
org.springframework.context.support.AbstractApplicationContext doClose
WARNING: Exception thrown from ApplicationListener handling ContextClosedEvent
java.lang.IllegalStateException: BeanFactory not initialized or already closed
- call 'refresh' before accessing beans via the ApplicationContext
at
org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:171)
at
org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1079)
at
org.apache.cxf.bus.spring.BusApplicationListener.onApplicationEvent(BusApplicationListener.java:66)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:97)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:303)
at
org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1007)
at
org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:970)
at
org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:378)
at
org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:78)
at
org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:683)
at
org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:143)
at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:458)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:80)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStop(HandlerCollection.java:247)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:80)
at
org.eclipse.jetty.server.handler.HandlerWrapper.doStop(HandlerWrapper.java:108)
at org.eclipse.jetty.server.Server.doStop(Server.java:319)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:80)
at Main.main(Main.java:19)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
{code}
To replicate, simply run the Main method in the attached project. Then switch
the CXF version in the pom.xml, and see it works with version 2.3.1. I
therefore thinks this is related to CXF-3213.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3428) Context closed twice with Spring setup
[
https://issues.apache.org/jira/browse/CXF-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anders Båtstrand updated CXF-3428:
--
Attachment: context-bug.zip
Added minimal project needed to replicate the error I am getting.
> Context closed twice with Spring setup
> --
>
> Key: CXF-3428
> URL: https://issues.apache.org/jira/browse/CXF-3428
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.3.2, 2.3.3
> Environment: Windows 7, Java 5 and 6
>Reporter: Anders Båtstrand
> Labels: context, spring
> Attachments: context-bug.zip
>
>
> See the enclosed project (very minimal).
> I have a cxf.cml and an applicationContext.xml, and loads both using
> ContextLoaderListener in my web.xml. I have also a CXFServlet. Starting this
> with Jetty, I get the following exception when I stop the server:
> {code}
> 28.mar.2011 23:43:15
> org.springframework.context.support.AbstractApplicationContext doClose
> WARNING: Exception thrown from ApplicationListener handling ContextClosedEvent
> java.lang.IllegalStateException: BeanFactory not initialized or already
> closed - call 'refresh' before accessing beans via the ApplicationContext
> at
> org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:171)
> at
> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1079)
> at
> org.apache.cxf.bus.spring.BusApplicationListener.onApplicationEvent(BusApplicationListener.java:66)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:97)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:303)
> at
> org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1007)
> at
> org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:970)
> at
> org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:378)
> at
> org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:78)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:683)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:143)
> at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:458)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:80)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.doStop(HandlerCollection.java:247)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:80)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.doStop(HandlerWrapper.java:108)
> at org.eclipse.jetty.server.Server.doStop(Server.java:319)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:80)
> at Main.main(Main.java:19)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> {code}
> To replicate, simply run the Main method in the attached project. Then switch
> the CXF version in the pom.xml, and see it works with version 2.3.1. I
> therefore thinks this is related to CXF-3213.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
cxf jaxrs:client and aop
Not sure if there is a bug or if I am not doing something correct.
I have defined a jaxrs:client in my jbossws-cxf.xml file as follows:
In my spring config file, I have defined an aspect bean called: AuditImpl
This extends an interface called: Audit
I have the auditClient as a property and within the AuditImpl, I define the
auditClient as:
private AuditInterface auditClient;
public void setAuditClient(AuditInterface auditClient) {
this.auditClient = auditClient;
}
I can define the aspect, via xml schema config, or through annotations
fine.. It will build and deploy to jboss fine. As soon as I define
@Before, it does not deploy any more. Whether I define the Before in the
xml schema or as an annotation, the defining of it kills the deployment.
Any help is appreciated. Is this a bug or am I doing something wrong? If I
am doing something wrong, can you please provide some help as to what?
Thank you.
I get the following error:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'auditClient': Initialization of bean failed; nested exception is
org.aspectj.weaver.reflect.ReflectionWorld$ReflectionWorldException: warning
can't determine superclass of missing type $Proxy388
[Xlint:cantFindType]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:527)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4393)
at
org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
at
org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)
at
org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
at org.jboss.web.deployers.WebModule.start(WebModule.java:97)..
(more)
--
View this message in context:
http://cxf.547215.n5.nabble.com/cxf-jaxrs-client-and-aop-tp4268741p4268741.html
Sent from the cxf-issues mailing list archive at Nabble.com.
Re: cxf jaxrs:client and aop
Additional information: I am using Spring 3.0.5 and jbossws cxf 3.4.0 I also had to put the cxf-rt-frontend-jaxrs-2.3.1 jar in the common/lib directory. Not sure if this is correct, but jaxrs:client did not deploy unless this jar was there. -- View this message in context: http://cxf.547215.n5.nabble.com/cxf-jaxrs-client-and-aop-tp4268741p4268747.html Sent from the cxf-issues mailing list archive at Nabble.com.
[jira] [Created] (CXF-3429) ServerImpl should shutdown Destination before setMessageObserver=null
ServerImpl should shutdown Destination before setMessageObserver=null
-
Key: CXF-3429
URL: https://issues.apache.org/jira/browse/CXF-3429
Project: CXF
Issue Type: Bug
Components: Core
Affects Versions: 2.2.10
Reporter: David Liu
Hi,
During shutdown the CXF server, we encounter the NullPointerException from
time to time.
The issue is that ServerImpl will set MessageObserver to null, and then it
shutdown desination. however, if the server is multi-thread and probably some
thread is runing, then it can result in NullPointerException because
MessageObserver is null.
Can we fix this bug by shutdown the Destination first and then set
MessageObserver to null?
{code}
public class ServerImpl implements Server {
public void stop() {
LOG.fine("Server is stopping.");
...
getDestination().setMessageObserver(null);
getDestination().shutdown();
}
{code}
David
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3429) ServerImpl should shutdown Destination before setMessageObserver=null
[
https://issues.apache.org/jira/browse/CXF-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Liu updated CXF-3429:
---
Description:
Hi,
During shutdown the CXF server, we encounter the NullPointerException from
time to time.
The issue is that ServerImpl will set MessageObserver to null, and then it
shutdown desination. however, if the server is multi-thread and probably some
thread is runing, then it can result in NullPointerException because
MessageObserver is null.
Can we fix this bug by shutdown the Destination first and then set
MessageObserver to null?
Also, do we have a workaround for this issue?
{code}
public class ServerImpl implements Server {
public void stop() {
LOG.fine("Server is stopping.");
...
getDestination().setMessageObserver(null);
getDestination().shutdown();
}
{code}
David
was:
Hi,
During shutdown the CXF server, we encounter the NullPointerException from
time to time.
The issue is that ServerImpl will set MessageObserver to null, and then it
shutdown desination. however, if the server is multi-thread and probably some
thread is runing, then it can result in NullPointerException because
MessageObserver is null.
Can we fix this bug by shutdown the Destination first and then set
MessageObserver to null?
{code}
public class ServerImpl implements Server {
public void stop() {
LOG.fine("Server is stopping.");
...
getDestination().setMessageObserver(null);
getDestination().shutdown();
}
{code}
David
> ServerImpl should shutdown Destination before setMessageObserver=null
> -
>
> Key: CXF-3429
> URL: https://issues.apache.org/jira/browse/CXF-3429
> Project: CXF
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.2.10
>Reporter: David Liu
>
> Hi,
> During shutdown the CXF server, we encounter the NullPointerException from
> time to time.
> The issue is that ServerImpl will set MessageObserver to null, and then it
> shutdown desination. however, if the server is multi-thread and probably some
> thread is runing, then it can result in NullPointerException because
> MessageObserver is null.
> Can we fix this bug by shutdown the Destination first and then set
> MessageObserver to null?
>
> Also, do we have a workaround for this issue?
> {code}
> public class ServerImpl implements Server {
> public void stop() {
> LOG.fine("Server is stopping.");
> ...
> getDestination().setMessageObserver(null);
> getDestination().shutdown();
> }
> {code}
> David
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
