EJB integration for JAX-RS2.0 in CXF

Hi, Does current CXF support EJB based JAX-RS 2.0 application? If yes, is there requirement for EJB container? any additional configuration needed for application server? Thanks. Spec for EJB support: In a product that supports EJBs, an implementation MUST support the use of stateless and single

Re: Failed to create service. Trying to connect to a ssl connection

Did you specify the required CXF jars in your classpath? e.g. cxf-rt-transports-http If there is no jar missing, it would be helpful if you can post all the app and test case. 2013/8/19, gwena : > Hi, > > I'm trying to connect to a webservice on a secured connection > > The certificate has already

Re: no WebServiceException caught when invoking a method which returns null using the rpc/literal style

rev > > > － > Freeman(Yue) Fang > > Red Hat, Inc. > FuseSource is now part of Red Hat > Web: http://fusesource.com | http://www.redhat.com/ > Twitter: freemanfang > Blog: http://freemanfang.blogspot.com > http://blog.sina.com.cn/u/1473905042 >

Re: service location in WSDL generated by CXF

at the patch I've attached to CXF-4695, I believe > that should be fine for both your scenario and mine (the patch you > previously attached to 4677 was not ok for me). > If the patch is fine I'll likely add a testcase and commit. > Cheers > Alessio > > On 12/10/

Re: service location in WSDL generated by CXF

has been started in the meantime. > Cheers > Alessio > > On 12/07/2012 09:28 AM, Bin Zhu wrote: > > Hi Alessio, > > > > I've attached the patch here > > https://issues.apache.org/jira/secure/attachment/12559830/CXF-4677.patch > > Can you help review

Re: SOAPFault message improvement in CXF when there is unchecked NPE

t least modify this method. But we can't use Fault(Message message, Throwable throwable) to replace the Fault(ex) here since there is no the message object. After the comparison, the first correction method is preferred. Any thoughts? 2012/12/4 Bin Zhu > Thanks for the discussion and

Re: service location in WSDL generated by CXF

e the upcoming release ;-) > > Alessio > > On 12/06/2012 08:23 AM, Bin Zhu wrote: > > Hi, > > > > Thanks for the quick response. I've tried this patch but it doesn't > update > > all the soapaddress locations in my test. > > > > Looked in

Re: service location in WSDL generated by CXF

gt; On 12/05/2012 11:51 AM, Andrei Shakirin wrote: > > Issue https://issues.apache.org/jira/browse/CXF-4677 is created. > > Would you like to deliver the patch yourself? > > > > Cheers, > > Andrei. > > > >> -Original Message- > >> From:

Re: service location in WSDL generated by CXF

> >>> Proposed update of all services endpoints can be in some cases > incorrect. > >>> The absolute endpoint URL can be determined only from incoming request. > >> As > >>> far as you request InventoryService, not InventoryProvider; only &

Re: SOAPFault message improvement in CXF when there is unchecked NPE

ageCauseEnabled property? By > > >> default, the exception cause is not written out in the fault for > > >> security concerns. But you can set this property to true to change > > >> this behavior. I think this is what you are looking for, no? > > >> &g

Re: How does CXF build the soap address location in the WSDL?

In org.apache.cxf.frontend.WSDLGetUtils, there is a updateDoc method which is used to update the WSDL including the soap address location. 2012/11/29 Glen Mazza > Note #2 shows the algorithm: http://www.jroller.com/gmazza/** > entry/web_service_tutorial#**notes