Re: [VOTE] CXF 2.7.5/2.6.8 - take 2

[Freeman Fang]

+1
－
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
weibo: @Freeman小屋

On 2013-5-8, at 上午8:57, Daniel Kulp wrote:

> 
> We've resolved over 40 issues since 2.7.4.   Not a lot, but it includes an 
> OSGi fix that is blocking a Camel issues which may also be causing issues 
> with the ServiceMix release.  This also affects CXF 2.6.x which affects Camel 
> 2.10.x/ServiceMix 4.5.1 so I decided to do a 2.6.x release as well.
> 
> This second build fixes the 3 issues in JAX-RS that were identified as well 
> as an issue in StaxUtils when using the in-jdk parser and an issue in the 
> WS-Discovery service.
> 
> 
> 
> List of issues:
> 2.6.8
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324276
> 2.7.5
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324277
> 
> The Maven staging areas are at:  
> 2.6.8
> https://repository.apache.org/content/repositories/orgapachecxf-172/
> 2.7.5
> https://repository.apache.org/content/repositories/orgapachecxf-018/
> 
> The distributions are in the org/apache/cxf/apache-cxf/ directory of the 
> Maven staging areas.
> 
> This releases are tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.6.8
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.7.5
> 
> This vote will be open for at least 72 hours.
> 
> 
> -- 
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com

Re: [VOTE] CXF 2.7.5/2.6.8 - take 2

[Dennis Sosnoski]

+1

  - Dennis

On 05/08/2013 12:57 PM, Daniel Kulp wrote:

We've resolved over 40 issues since 2.7.4.   Not a lot, but it includes an OSGi 
fix that is blocking a Camel issues which may also be causing issues with the 
ServiceMix release.  This also affects CXF 2.6.x which affects Camel 
2.10.x/ServiceMix 4.5.1 so I decided to do a 2.6.x release as well.

This second build fixes the 3 issues in JAX-RS that were identified as well as 
an issue in StaxUtils when using the in-jdk parser and an issue in the 
WS-Discovery service.



List of issues:
2.6.8
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324276
2.7.5
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324277

The Maven staging areas are at:
2.6.8
https://repository.apache.org/content/repositories/orgapachecxf-172/
2.7.5
https://repository.apache.org/content/repositories/orgapachecxf-018/

The distributions are in the org/apache/cxf/apache-cxf/ directory of the Maven 
staging areas.

This releases are tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.6.8
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.7.5

This vote will be open for at least 72 hours.

Re: [VOTE] CXF 2.7.5/2.6.8 - take 2

[Johan Edstrom]

Did some simple testing, +1 - non binding and Thanks to the CXF guys!

On May 7, 2013, at 7:01 PM, Jeff Genender  wrote:

> +1 
> 
> Jeff
> 
> On May 7, 2013, at 8:57 PM, Daniel Kulp  wrote:
> 
>> 
>> We've resolved over 40 issues since 2.7.4.   Not a lot, but it includes an 
>> OSGi fix that is blocking a Camel issues which may also be causing issues 
>> with the ServiceMix release.  This also affects CXF 2.6.x which affects 
>> Camel 2.10.x/ServiceMix 4.5.1 so I decided to do a 2.6.x release as well.
>> 
>> This second build fixes the 3 issues in JAX-RS that were identified as well 
>> as an issue in StaxUtils when using the in-jdk parser and an issue in the 
>> WS-Discovery service.
>> 
>> 
>> 
>> List of issues:
>> 2.6.8
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324276
>> 2.7.5
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324277
>> 
>> The Maven staging areas are at:  
>> 2.6.8
>> https://repository.apache.org/content/repositories/orgapachecxf-172/
>> 2.7.5
>> https://repository.apache.org/content/repositories/orgapachecxf-018/
>> 
>> The distributions are in the org/apache/cxf/apache-cxf/ directory of the 
>> Maven staging areas.
>> 
>> This releases are tagged at:
>> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.6.8
>> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.7.5
>> 
>> This vote will be open for at least 72 hours.
>> 
>> 
>> -- 
>> Daniel Kulp
>> dk...@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
> 

Re: [VOTE] CXF 2.7.5/2.6.8 - take 2

[Jeff Genender]

+1 

Jeff

On May 7, 2013, at 8:57 PM, Daniel Kulp  wrote:

> 
> We've resolved over 40 issues since 2.7.4.   Not a lot, but it includes an 
> OSGi fix that is blocking a Camel issues which may also be causing issues 
> with the ServiceMix release.  This also affects CXF 2.6.x which affects Camel 
> 2.10.x/ServiceMix 4.5.1 so I decided to do a 2.6.x release as well.
> 
> This second build fixes the 3 issues in JAX-RS that were identified as well 
> as an issue in StaxUtils when using the in-jdk parser and an issue in the 
> WS-Discovery service.
> 
> 
> 
> List of issues:
> 2.6.8
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324276
> 2.7.5
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324277
> 
> The Maven staging areas are at:  
> 2.6.8
> https://repository.apache.org/content/repositories/orgapachecxf-172/
> 2.7.5
> https://repository.apache.org/content/repositories/orgapachecxf-018/
> 
> The distributions are in the org/apache/cxf/apache-cxf/ directory of the 
> Maven staging areas.
> 
> This releases are tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.6.8
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.7.5
> 
> This vote will be open for at least 72 hours.
> 
> 
> -- 
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com

Re: [VOTE] CXF 2.7.5/2.6.8 - take 2

[Jason Pell]

+1 (non binding)


On Wed, May 8, 2013 at 10:57 AM, Daniel Kulp  wrote:

>
> We've resolved over 40 issues since 2.7.4.   Not a lot, but it includes an
> OSGi fix that is blocking a Camel issues which may also be causing issues
> with the ServiceMix release.  This also affects CXF 2.6.x which affects
> Camel 2.10.x/ServiceMix 4.5.1 so I decided to do a 2.6.x release as well.
>
> This second build fixes the 3 issues in JAX-RS that were identified as
> well as an issue in StaxUtils when using the in-jdk parser and an issue in
> the WS-Discovery service.
>
>
>
> List of issues:
> 2.6.8
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324276
> 2.7.5
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324277
>
> The Maven staging areas are at:
> 2.6.8
> https://repository.apache.org/content/repositories/orgapachecxf-172/
> 2.7.5
> https://repository.apache.org/content/repositories/orgapachecxf-018/
>
> The distributions are in the org/apache/cxf/apache-cxf/ directory of the
> Maven staging areas.
>
> This releases are tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.6.8
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.7.5
>
> This vote will be open for at least 72 hours.
>
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>

[VOTE] CXF 2.7.5/2.6.8 - take 2

[Daniel Kulp]

We've resolved over 40 issues since 2.7.4.   Not a lot, but it includes an OSGi 
fix that is blocking a Camel issues which may also be causing issues with the 
ServiceMix release.  This also affects CXF 2.6.x which affects Camel 
2.10.x/ServiceMix 4.5.1 so I decided to do a 2.6.x release as well.

This second build fixes the 3 issues in JAX-RS that were identified as well as 
an issue in StaxUtils when using the in-jdk parser and an issue in the 
WS-Discovery service.



List of issues:
2.6.8
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324276
2.7.5
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324277

The Maven staging areas are at:  
2.6.8
https://repository.apache.org/content/repositories/orgapachecxf-172/
2.7.5
https://repository.apache.org/content/repositories/orgapachecxf-018/

The distributions are in the org/apache/cxf/apache-cxf/ directory of the Maven 
staging areas.

This releases are tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.6.8
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.7.5

This vote will be open for at least 72 hours.


-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

IndexOutOfBoundsException in WrappedOutInterceptor$WrappedOutEndingInterceptor

[Mikhail GRUSHINSKIY]

Hello,

After upgrade to CXF 2.7.4 (from very old CXF version) I'm getting 
IndexOutOfBoundsException
in WrappedOutInterceptor$WrappedOutEndingInterceptor . What could be the issue?
How can CXF mismatch writeStartElement and writeEndElement?

Thanks,
--MG

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.LinkedList.entry(LinkedList.java:365)
at java.util.LinkedList.remove(LinkedList.java:357)
at 
org.apache.cxf.staxutils.OverlayW3CDOMStreamWriter.writeEndElement(OverlayW3CDOMStreamWriter.java:57)
at 
org.apache.cxf.interceptor.WrappedOutInterceptor$WrappedOutEndingInterceptor.handleMessage(WrappedOutInterceptor.java:102)
at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
at 
org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:77)
at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
at 
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at 
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
at 
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
at 
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:158)


This message and any attachments (the "message") is intended solely for 
the addressees and is confidential. If you receive this message in error, 
please delete it and immediately notify the sender. Any use not in accord 
with its purpose, any dissemination or disclosure, either whole or partial, 
is prohibited except formal approval. The internet can not guarantee the 
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) 
not therefore be liable for the message if modified. Please note that certain 
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.

Some minor (ok, not so minor) thoughts for CXF 3.0

[Daniel Kulp]

I'd like to do a couple refactoring things for 3.0 to simplify the class 
structure a little bit:

1) Bus -> CXFBusImpl -> ExtensionManagerBus -> Spring/BlueprintBus
We originally had Spring and Blueprint subclass CXFBusImpl.  However, with the 
refactorings in the 2.4 timeframe, we made everything extend the 
ExtensionMangerBus.  Thus, CXFBusImpl is pretty much not needed.   I'd like to 
push whatever is left there into ExtensionMangerBus and remove a level of the 
hierarchy. (alternatively, push the stuff in ExtensionMangerBus down into 
CXFBusImpl).   Thoughts?   

2) Interceptor ->  PhaseInterceptor and InterceptorChain -> 
PhaseInterceptorChain
We originally (in 2005) thought about having the interceptor be more 
independent of the phases.  However, that never really worked and pretty much 
all interceptors used in CXF have to be of the PhaseInterceptor variety.   
Additionally, the only "chain" we've had is the PhaseInterceptorChain.   Almost 
all the interfaces use "Interceptor<…>" or "InterceptorChain".   Thus, I'd like 
to just push everything down into Interceptor/InterceptorChain and get rid of 
the others to remove that level and reduce  confusion so people know there 
needs to be a phase there.   

3) QueryHandlers -> these were originally used for the ?wsdl processing (and is 
still used for ?js).  However, that stuff is better done directly on the 
interceptor chains as interceptors to allow user supplied interceptors to also 
handle them.   I'd like to just remove these.  (obviously update the ?js stuff) 
  Would simplify the CXFServlet a bit.

4) Merge "PropertiesAwareDatabinding"  into DataBinding.   The "properties 
aware" version was introduced just to be able to add a method without breaking 
binary compatibility.  Might as well push it in now.

5) BaseDataReader/DataReader and the same for the writer.   Not really sure why 
they are separated but EVERYTHING uses just "DataReader". Get rid of 
BaseData*.

6) Remove all the "WSDL" based things from cxf-api and cxf-rt-core.   I need to 
play with this more.  Likely rename cxf-rt-frontend-simple to 
cxf-rt-frontend-wsdl (or similar) and move all of it there as that would be the 
base for everything that is WSDL related.   That would leave api/core free of 
WSDL stuff to make the JAX-RS stuff lighter.   Either that or create a new 
bundle that would live between rt-core and rt-frontent-simple and the wsdl 
based bindings/technologies.   Likewise, find a way for transports (like http) 
to not need any WSDL things.This will likely also require some of the 
interceptors in org.apache.cxf.interceptor to move a bit, but that's probably a 
good thing as there is too much stuff in there that should be in more specific 
sub packages or something.


Obviously a lot of that has some compatibility impact, user impact, etc..., but 
that's why I think doing it for 3.0 is the best option.   I'd love peoples 
thoughts on any of it. Mostly just trying to simplify a few things, clarify 
things, remove/move some deps around.


-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: XKMS donation

[Daniel Kulp]

Andrei,

The patch is a bit bigger than I kind of expected.   That's not a bad thing.   
However, I think this might fall into the realm of requiring a grant due to 
it's size and complexity.   I'll start the process tomorrow.   FYI: it's 
documented at:

http://incubator.apache.org/ip-clearance/

Dan



On May 7, 2013, at 12:30 PM, Andrei Shakirin  wrote:

> Hi,
> 
> As it was already announced in "Thoughts about a 2.8 release" thread, Talend 
> is happy to donate the initial XKMS 2.0 implementation to CXF.
> 
> The Jira issue https://issues.apache.org/jira/browse/CXF-5001 contains patch 
> with initial draft of XKMS code.
> 
> 
> The use case, architecture and design of XKMS Service is described in CXF 
> wiki:
> 
> https://cwiki.apache.org/confluence/display/CXF20DOC/XML+Key+Management+Service+%28XKMS%29
> 
> and in the blog: 
> http://ashakirin.blogspot.de/2013/04/cxf-security-getting-certificates-from.html.
> 
> 
> 
> Any feedback for this code is welcome. The next tasks will be support 
> revocation lists, complete validate operation for trusted chains, extend 
> system tests, support other types of  keys and keys storages.
> 
> 
> 
> Regards,
> 
> Andrei.
> 

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

XKMS donation

[Andrei Shakirin]

Hi,

As it was already announced in "Thoughts about a 2.8 release" thread, Talend is 
happy to donate the initial XKMS 2.0 implementation to CXF.

The Jira issue https://issues.apache.org/jira/browse/CXF-5001 contains patch 
with initial draft of XKMS code.


The use case, architecture and design of XKMS Service is described in CXF wiki:

https://cwiki.apache.org/confluence/display/CXF20DOC/XML+Key+Management+Service+%28XKMS%29

and in the blog: 
http://ashakirin.blogspot.de/2013/04/cxf-security-getting-certificates-from.html.



Any feedback for this code is welcome. The next tasks will be support 
revocation lists, complete validate operation for trusted chains, extend system 
tests, support other types of  keys and keys storages.



Regards,

Andrei.

Re: [CANCEL] [VOTE] CXF 2.7.5/2.6.8

[Sergey Beryozkin]

On 07/05/13 17:11, Daniel Kulp wrote:


The Talend QA team (as well as Glen and a few others) have found some backwards 
compatibility issues with 2.7.5 that are causing issues.   Another example is 
Syncope not being able to update due to a compatibility problem.

Thus, I'm canceling this vote to resolve those few issues and I'll rebuild 
later tonight once I can verify those fixes are in place.

Sorry about that, but definitely give the testers some credit for finding the 
issues.


And the real 'culprit' is CXF JAX-RS front-end, sorry to all.

3 migration issues have been reported:
- JAX-RS Response copy does not work if 1.1 API happens to be on the 
classpath
- Legacy custom ResourceComparators extending CXF 
OperationResourceInfoComparator will 'find' the super constructor missing
- Finally, CXF JAX-RS clients are now adapted to CXF core Client 
interface so that their lifecycle can be managed with 
ClientLifeCycleListener interface expecting the latter. The custom 
listeners expecting Client.getEndpoint working will get NPE


First 2 issues have been resolved, the last one will be shortly

Apologies all for the hassle,
Sergey


Dan



On May 4, 2013, at 8:14 AM, Daniel Kulp  wrote:




We've resolved over 40 issues since 2.7.4.   Not a lot, but it includes an OSGi 
fix that is blocking a Camel issues which may also be causing issues with the 
ServiceMix release.  This also affects CXF 2.6.x which affects Camel 
2.10.x/ServiceMix 4.5.1 so I decided to do a 2.6.x release as well.


List of issues:
2.6.8
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324276
2.7.5
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324277

The Maven staging areas are at:
2.6.8
https://repository.apache.org/content/repositories/orgapachecxf-172/
2.7.5
https://repository.apache.org/content/repositories/orgapachecxf-174/

The distributions are in the org/apache/cxf/apache-cxf/ directory of the Maven 
staging areas.

This releases are tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.6.8
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.7.5

This vote will be open for at least 72 hours.


--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

[CANCEL] [VOTE] CXF 2.7.5/2.6.8

[Daniel Kulp]

The Talend QA team (as well as Glen and a few others) have found some backwards 
compatibility issues with 2.7.5 that are causing issues.   Another example is 
Syncope not being able to update due to a compatibility problem.  

Thus, I'm canceling this vote to resolve those few issues and I'll rebuild 
later tonight once I can verify those fixes are in place.

Sorry about that, but definitely give the testers some credit for finding the 
issues.  

Dan



On May 4, 2013, at 8:14 AM, Daniel Kulp  wrote:

> 
> 
> We've resolved over 40 issues since 2.7.4.   Not a lot, but it includes an 
> OSGi fix that is blocking a Camel issues which may also be causing issues 
> with the ServiceMix release.  This also affects CXF 2.6.x which affects Camel 
> 2.10.x/ServiceMix 4.5.1 so I decided to do a 2.6.x release as well.
> 
> 
> List of issues:
> 2.6.8
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324276
> 2.7.5
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324277
> 
> The Maven staging areas are at:  
> 2.6.8
> https://repository.apache.org/content/repositories/orgapachecxf-172/
> 2.7.5
> https://repository.apache.org/content/repositories/orgapachecxf-174/
> 
> The distributions are in the org/apache/cxf/apache-cxf/ directory of the 
> Maven staging areas.
> 
> This releases are tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.6.8
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.7.5
> 
> This vote will be open for at least 72 hours.
> 
> 
> -- 
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
> 

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: Cxf CDI and Jersey integration (No SPRING)

[Nicolae Petridean]

Hi Romain,
we already defined the architecture, and for now we stick to our decisions
, we cannot just add EJB to our project :). I also had a look into delta
spike project (i've noticed you commited for delta spike also), and i like
that better, because it is simple and pluggable, unfortunatelly it is not
mature enough for us. Tomee would be great if we would deploy this only in
Tomcat, and of course if we would have EJB in our technology stack, but
that is not the case.

Thanks for your suggestions though, Nicu !


On Tue, May 7, 2013 at 2:46 PM, Romain Manni-Bucau wrote:

> @Nicolae: if you use cdi that's even worse, you basically have the same
> than tomee but done by yourselfand it doesn't answer the question
> "what's the issue with EJBs"?
>
> PS: we can talk about it on IRC if you want/can to avoid to bother cxf
> list, freenode #openejb for instance
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau *
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/5/7 Nicolae Petridean 
>
> > Hi,
> > we do not want to use EJB :). We use CDI for now, and even if we would
> > change that, we would choose Spring.
> >
> > Thanks, Nicu
> >
> >
> > On Tue, May 7, 2013 at 2:38 PM, Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >wrote:
> >
> > > @Nicolae:  Hi "too much EJB"? what does it mean? The EJB code is
> > basically
> > > less than cxf one
> > >
> > > *Romain Manni-Bucau*
> > > *Twitter: @rmannibucau *
> > > *Blog: **http://rmannibucau.wordpress.com/*<
> > > http://rmannibucau.wordpress.com/>
> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > *Github: https://github.com/rmannibucau*
> > >
> > >
> > >
> > > 2013/5/7 Nicolae Petridean 
> > >
> > > > Hi Sergey,
> > > > thanks for the quick answer.
> > > > Tomee is not an option for us...too much EJB inside.
> > > > The oAuth 2.0 resources will help.
> > > >
> > > > Nicu
> > > >
> > > >
> > > > On Tue, May 7, 2013 at 12:29 PM, Sergey Beryozkin <
> > sberyoz...@gmail.com
> > > > >wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > On 07/05/13 09:50, Nicolae Petridean wrote:
> > > > >
> > > > >> Hi guys,
> > > > >> we are buidling an application that uses Jersey for exposing rest
> > > > services
> > > > >> and CDI for services management.
> > > > >> We need to integrate this app with a 3rd party identity provider
> but
> > > > we're
> > > > >> also consider the opportunity to replace jersey with CXF. The
> > problem
> > > is
> > > > >> we
> > > > >> do not have Spring in the application big picture. Can you help us
> > > with
> > > > >> some examples or advise about how and if we should do it
> (integrate
> > > with
> > > > >> jersey and CDI (Weld ) ? The security protocol we will use is also
> > not
> > > > >> clear yet. There is a possibility to use Oauth 2.0.
> > > > >>
> > > > > I'd recommend to ask a question about Jersey & CDI at the Jersey
> > users
> > > > > list, I'm pretty sure they support it in Glassfish.
> > > > >
> > > > > We do not have an explicit support for CDI in CXF. I think you can
> > get
> > > > CDI
> > > > > + CXF working well in TomEE+ distro. See what we have about OAuth2
> at
> > > the
> > > > > moment:
> > > > >
> > > > > http://cxf.apache.org/docs/**jax-rs-oauth2.html<
> > > > http://cxf.apache.org/docs/jax-rs-oauth2.html>
> > > > >
> > > > > Also check Apache Oltu for OAuth2 - that should work with
> Jersey/CXF
> > > too.
> > > > >
> > > > >
> > > > >
> > > > >> If you cannot answer fully to my question, maybe you can guide us
> > to a
> > > > CXF
> > > > >> example without Spring.
> > > > >>
> > > > >>  You can use CXFNonSpringJaxrsServlet, see
> > > > >
> http://cxf.apache.org/docs/**jaxrs-services-configuration.**html#**
> > > > > JAXRSServicesConfiguration-**ConfiguringJAXRSservicesincont**
> > > > > ainerwithoutSpring<
> > > >
> > >
> >
> http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAXRSservicesincontainerwithoutSpring
> > > > >
> > > > >
> > > > > HTH, Sergey
> > > > >
> > > > >
> > > > >  Thanks in advance, Nicu
> > > > >>
> > > > >>
> > > > >
> > > > > --
> > > > > Sergey Beryozkin
> > > > >
> > > > > Talend Community Coders
> > > > > http://coders.talend.com/
> > > > >
> > > > > Blog: http://sberyozkin.blogspot.com
> > > > >
> > > >
> > >
> >
>

Re: Cxf CDI and Jersey integration (No SPRING)

[Romain Manni-Bucau]

@Nicolae: if you use cdi that's even worse, you basically have the same
than tomee but done by yourselfand it doesn't answer the question
"what's the issue with EJBs"?

PS: we can talk about it on IRC if you want/can to avoid to bother cxf
list, freenode #openejb for instance

*Romain Manni-Bucau*
*Twitter: @rmannibucau *
*Blog: **http://rmannibucau.wordpress.com/*
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*



2013/5/7 Nicolae Petridean 

> Hi,
> we do not want to use EJB :). We use CDI for now, and even if we would
> change that, we would choose Spring.
>
> Thanks, Nicu
>
>
> On Tue, May 7, 2013 at 2:38 PM, Romain Manni-Bucau  >wrote:
>
> > @Nicolae:  Hi "too much EJB"? what does it mean? The EJB code is
> basically
> > less than cxf one
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau *
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/5/7 Nicolae Petridean 
> >
> > > Hi Sergey,
> > > thanks for the quick answer.
> > > Tomee is not an option for us...too much EJB inside.
> > > The oAuth 2.0 resources will help.
> > >
> > > Nicu
> > >
> > >
> > > On Tue, May 7, 2013 at 12:29 PM, Sergey Beryozkin <
> sberyoz...@gmail.com
> > > >wrote:
> > >
> > > > Hi
> > > >
> > > > On 07/05/13 09:50, Nicolae Petridean wrote:
> > > >
> > > >> Hi guys,
> > > >> we are buidling an application that uses Jersey for exposing rest
> > > services
> > > >> and CDI for services management.
> > > >> We need to integrate this app with a 3rd party identity provider but
> > > we're
> > > >> also consider the opportunity to replace jersey with CXF. The
> problem
> > is
> > > >> we
> > > >> do not have Spring in the application big picture. Can you help us
> > with
> > > >> some examples or advise about how and if we should do it (integrate
> > with
> > > >> jersey and CDI (Weld ) ? The security protocol we will use is also
> not
> > > >> clear yet. There is a possibility to use Oauth 2.0.
> > > >>
> > > > I'd recommend to ask a question about Jersey & CDI at the Jersey
> users
> > > > list, I'm pretty sure they support it in Glassfish.
> > > >
> > > > We do not have an explicit support for CDI in CXF. I think you can
> get
> > > CDI
> > > > + CXF working well in TomEE+ distro. See what we have about OAuth2 at
> > the
> > > > moment:
> > > >
> > > > http://cxf.apache.org/docs/**jax-rs-oauth2.html<
> > > http://cxf.apache.org/docs/jax-rs-oauth2.html>
> > > >
> > > > Also check Apache Oltu for OAuth2 - that should work with Jersey/CXF
> > too.
> > > >
> > > >
> > > >
> > > >> If you cannot answer fully to my question, maybe you can guide us
> to a
> > > CXF
> > > >> example without Spring.
> > > >>
> > > >>  You can use CXFNonSpringJaxrsServlet, see
> > > > http://cxf.apache.org/docs/**jaxrs-services-configuration.**html#**
> > > > JAXRSServicesConfiguration-**ConfiguringJAXRSservicesincont**
> > > > ainerwithoutSpring<
> > >
> >
> http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAXRSservicesincontainerwithoutSpring
> > > >
> > > >
> > > > HTH, Sergey
> > > >
> > > >
> > > >  Thanks in advance, Nicu
> > > >>
> > > >>
> > > >
> > > > --
> > > > Sergey Beryozkin
> > > >
> > > > Talend Community Coders
> > > > http://coders.talend.com/
> > > >
> > > > Blog: http://sberyozkin.blogspot.com
> > > >
> > >
> >
>

Re: Cxf CDI and Jersey integration (No SPRING)

[Nicolae Petridean]

Hi,
we do not want to use EJB :). We use CDI for now, and even if we would
change that, we would choose Spring.

Thanks, Nicu


On Tue, May 7, 2013 at 2:38 PM, Romain Manni-Bucau wrote:

> @Nicolae:  Hi "too much EJB"? what does it mean? The EJB code is basically
> less than cxf one
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau *
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/5/7 Nicolae Petridean 
>
> > Hi Sergey,
> > thanks for the quick answer.
> > Tomee is not an option for us...too much EJB inside.
> > The oAuth 2.0 resources will help.
> >
> > Nicu
> >
> >
> > On Tue, May 7, 2013 at 12:29 PM, Sergey Beryozkin  > >wrote:
> >
> > > Hi
> > >
> > > On 07/05/13 09:50, Nicolae Petridean wrote:
> > >
> > >> Hi guys,
> > >> we are buidling an application that uses Jersey for exposing rest
> > services
> > >> and CDI for services management.
> > >> We need to integrate this app with a 3rd party identity provider but
> > we're
> > >> also consider the opportunity to replace jersey with CXF. The problem
> is
> > >> we
> > >> do not have Spring in the application big picture. Can you help us
> with
> > >> some examples or advise about how and if we should do it (integrate
> with
> > >> jersey and CDI (Weld ) ? The security protocol we will use is also not
> > >> clear yet. There is a possibility to use Oauth 2.0.
> > >>
> > > I'd recommend to ask a question about Jersey & CDI at the Jersey users
> > > list, I'm pretty sure they support it in Glassfish.
> > >
> > > We do not have an explicit support for CDI in CXF. I think you can get
> > CDI
> > > + CXF working well in TomEE+ distro. See what we have about OAuth2 at
> the
> > > moment:
> > >
> > > http://cxf.apache.org/docs/**jax-rs-oauth2.html<
> > http://cxf.apache.org/docs/jax-rs-oauth2.html>
> > >
> > > Also check Apache Oltu for OAuth2 - that should work with Jersey/CXF
> too.
> > >
> > >
> > >
> > >> If you cannot answer fully to my question, maybe you can guide us to a
> > CXF
> > >> example without Spring.
> > >>
> > >>  You can use CXFNonSpringJaxrsServlet, see
> > > http://cxf.apache.org/docs/**jaxrs-services-configuration.**html#**
> > > JAXRSServicesConfiguration-**ConfiguringJAXRSservicesincont**
> > > ainerwithoutSpring<
> >
> http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAXRSservicesincontainerwithoutSpring
> > >
> > >
> > > HTH, Sergey
> > >
> > >
> > >  Thanks in advance, Nicu
> > >>
> > >>
> > >
> > > --
> > > Sergey Beryozkin
> > >
> > > Talend Community Coders
> > > http://coders.talend.com/
> > >
> > > Blog: http://sberyozkin.blogspot.com
> > >
> >
>

Re: Cxf CDI and Jersey integration (No SPRING)

[Romain Manni-Bucau]

@Nicolae:  Hi "too much EJB"? what does it mean? The EJB code is basically
less than cxf one

*Romain Manni-Bucau*
*Twitter: @rmannibucau *
*Blog: **http://rmannibucau.wordpress.com/*
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*



2013/5/7 Nicolae Petridean 

> Hi Sergey,
> thanks for the quick answer.
> Tomee is not an option for us...too much EJB inside.
> The oAuth 2.0 resources will help.
>
> Nicu
>
>
> On Tue, May 7, 2013 at 12:29 PM, Sergey Beryozkin  >wrote:
>
> > Hi
> >
> > On 07/05/13 09:50, Nicolae Petridean wrote:
> >
> >> Hi guys,
> >> we are buidling an application that uses Jersey for exposing rest
> services
> >> and CDI for services management.
> >> We need to integrate this app with a 3rd party identity provider but
> we're
> >> also consider the opportunity to replace jersey with CXF. The problem is
> >> we
> >> do not have Spring in the application big picture. Can you help us with
> >> some examples or advise about how and if we should do it (integrate with
> >> jersey and CDI (Weld ) ? The security protocol we will use is also not
> >> clear yet. There is a possibility to use Oauth 2.0.
> >>
> > I'd recommend to ask a question about Jersey & CDI at the Jersey users
> > list, I'm pretty sure they support it in Glassfish.
> >
> > We do not have an explicit support for CDI in CXF. I think you can get
> CDI
> > + CXF working well in TomEE+ distro. See what we have about OAuth2 at the
> > moment:
> >
> > http://cxf.apache.org/docs/**jax-rs-oauth2.html<
> http://cxf.apache.org/docs/jax-rs-oauth2.html>
> >
> > Also check Apache Oltu for OAuth2 - that should work with Jersey/CXF too.
> >
> >
> >
> >> If you cannot answer fully to my question, maybe you can guide us to a
> CXF
> >> example without Spring.
> >>
> >>  You can use CXFNonSpringJaxrsServlet, see
> > http://cxf.apache.org/docs/**jaxrs-services-configuration.**html#**
> > JAXRSServicesConfiguration-**ConfiguringJAXRSservicesincont**
> > ainerwithoutSpring<
> http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAXRSservicesincontainerwithoutSpring
> >
> >
> > HTH, Sergey
> >
> >
> >  Thanks in advance, Nicu
> >>
> >>
> >
> > --
> > Sergey Beryozkin
> >
> > Talend Community Coders
> > http://coders.talend.com/
> >
> > Blog: http://sberyozkin.blogspot.com
> >
>

Re: [VOTE] CXF 2.7.5/2.6.8

[Glen Mazza]

+1

Glen



--
View this message in context: 
http://cxf.547215.n5.nabble.com/VOTE-CXF-2-7-5-2-6-8-tp5727223p5727340.html
Sent from the cxf-dev mailing list archive at Nabble.com.

Re: Cxf CDI and Jersey integration (No SPRING)

[Nicolae Petridean]

Hi Sergey,
thanks for the quick answer.
Tomee is not an option for us...too much EJB inside.
The oAuth 2.0 resources will help.

Nicu


On Tue, May 7, 2013 at 12:29 PM, Sergey Beryozkin wrote:

> Hi
>
> On 07/05/13 09:50, Nicolae Petridean wrote:
>
>> Hi guys,
>> we are buidling an application that uses Jersey for exposing rest services
>> and CDI for services management.
>> We need to integrate this app with a 3rd party identity provider but we're
>> also consider the opportunity to replace jersey with CXF. The problem is
>> we
>> do not have Spring in the application big picture. Can you help us with
>> some examples or advise about how and if we should do it (integrate with
>> jersey and CDI (Weld ) ? The security protocol we will use is also not
>> clear yet. There is a possibility to use Oauth 2.0.
>>
> I'd recommend to ask a question about Jersey & CDI at the Jersey users
> list, I'm pretty sure they support it in Glassfish.
>
> We do not have an explicit support for CDI in CXF. I think you can get CDI
> + CXF working well in TomEE+ distro. See what we have about OAuth2 at the
> moment:
>
> http://cxf.apache.org/docs/**jax-rs-oauth2.html
>
> Also check Apache Oltu for OAuth2 - that should work with Jersey/CXF too.
>
>
>
>> If you cannot answer fully to my question, maybe you can guide us to a CXF
>> example without Spring.
>>
>>  You can use CXFNonSpringJaxrsServlet, see
> http://cxf.apache.org/docs/**jaxrs-services-configuration.**html#**
> JAXRSServicesConfiguration-**ConfiguringJAXRSservicesincont**
> ainerwithoutSpring
>
> HTH, Sergey
>
>
>  Thanks in advance, Nicu
>>
>>
>
> --
> Sergey Beryozkin
>
> Talend Community Coders
> http://coders.talend.com/
>
> Blog: http://sberyozkin.blogspot.com
>

Re: Cxf CDI and Jersey integration (No SPRING)

[Sergey Beryozkin]

Hi
On 07/05/13 09:50, Nicolae Petridean wrote:

Hi guys,
we are buidling an application that uses Jersey for exposing rest services
and CDI for services management.
We need to integrate this app with a 3rd party identity provider but we're
also consider the opportunity to replace jersey with CXF. The problem is we
do not have Spring in the application big picture. Can you help us with
some examples or advise about how and if we should do it (integrate with
jersey and CDI (Weld ) ? The security protocol we will use is also not
clear yet. There is a possibility to use Oauth 2.0.
I'd recommend to ask a question about Jersey & CDI at the Jersey users 
list, I'm pretty sure they support it in Glassfish.


We do not have an explicit support for CDI in CXF. I think you can get 
CDI + CXF working well in TomEE+ distro. See what we have about OAuth2 
at the moment:


http://cxf.apache.org/docs/jax-rs-oauth2.html

Also check Apache Oltu for OAuth2 - that should work with Jersey/CXF too.



If you cannot answer fully to my question, maybe you can guide us to a CXF
example without Spring.


You can use CXFNonSpringJaxrsServlet, see
http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAXRSservicesincontainerwithoutSpring

HTH, Sergey



Thanks in advance, Nicu




--
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Blog: http://sberyozkin.blogspot.com

Re: How to skip style check for some special files when making local CXF build>

[Freeman Fang]

Hi,

FYI, all checkstyle configuration files are in a separate CXF project[1], you 
can checkout and tweak there for yourself use, 

[1]https://svn.apache.org/repos/asf/cxf/build-utils/trunk/
－
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
weibo: @Freeman小屋

On 2013-5-7, at 下午1:42, Bin Zhu wrote:

> Hi All,
> 
> I want to skip the style check for some special files(not all the files)
> when making local  CXF build.
> It is found that it can be done by adding something like below in the check
> style config files.(
> http://stackoverflow.com/questions/1012407/how-do-i-suppress-all-checks-for-a-file-in-checkstyle
> )
> 
> 
>
> 
> 
> 
> But The check style files seem to be dynamically created during the build
> process. (e.g. cxf-2.6.x/api/target/)
> I've looked the pom.xml in CXF-2.6.x, but didn't quite clear on how to add
> a customized module into the generated check style config file.
> 
> Does any one know how to do this? Thanks in advance.

Cxf CDI and Jersey integration (No SPRING)

[Nicolae Petridean]

Hi guys,
we are buidling an application that uses Jersey for exposing rest services
and CDI for services management.
We need to integrate this app with a 3rd party identity provider but we're
also consider the opportunity to replace jersey with CXF. The problem is we
do not have Spring in the application big picture. Can you help us with
some examples or advise about how and if we should do it (integrate with
jersey and CDI (Weld ) ? The security protocol we will use is also not
clear yet. There is a possibility to use Oauth 2.0.

If you cannot answer fully to my question, maybe you can guide us to a CXF
example without Spring.

Thanks in advance, Nicu