+1
On 07/10/14 21:59, Daniel Kulp wrote:
This is a vote to release CXF 2.6.16. This release is JUST to fix the
problems running 2.6.15 with Java5. All the changes between 2.6.15 and 2.6.16
are directly related to getting it to build, run, and test with Java5. This
does include downgradin
The features file would only pull in the opensaml jar/bundle, not the wrong
xerces. We don’t use “cxf.opensaml.osgi.version” as a version for any sort of
wrote:
> I'm sorry to say I have to -1 for both.
>
> As both CXF 2.7.13 and 3.0.2 use
> 2.6.1_1
> however servicemix wrapped opensaml 2.6
On Oct 9, 2014, at 4:48 AM, Daniel Kulp wrote:
> The features file would only pull in the opensaml jar/bundle, not the wrong
> xerces. We don’t use “cxf.opensaml.osgi.version” as a version for any sort
> of
More importantly, the _2 bundle is completely broken. It’s missing all the
*.xml
-1
The 2.6.1_2 bundle is broken. This needs to be reverted.
Dan
On Oct 9, 2014, at 1:58 AM, ff...@apache.org wrote:
> Repository: cxf
> Updated Branches:
> refs/heads/2.7.x-fixes bfd939ce0 -> b8e305d75
>
>
> [CXF-6040]need use servicemix wrapped opensaml 2.6.1_2
>
>
> Project: http://gi
This can cause problem in downstream project like servicemix where use
maven-notices-plugin to merge all notices from dependencies in features-repo
folder, though not a showstopper for CXF itself.
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
On 2014-10-9, a
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
Ok, seems we need another _3 bundle to fix the problems you point out, create
SMX4-1877[1] to track it.
As I said in another mail, as this wrong dependency isn't a showstoper for CXF
itself and so I will revert change and won't block CXF release
[1]https://issues.apache.org/jira/browse/SMX4-18
+1 to both
Christian
On 08.10.2014 19:30, Daniel Kulp wrote:
This is a vote to release CXF 2.7.13 and 3.0.2.There are over 90 JIRA
issues resolved for 3.0.2 which is a lot.
Tags:
https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=tag;h=3ec631c97e9eccf62490b176aab61044b3b9ab9f
https://git
+1.
Colm.
On Thu, Oct 9, 2014 at 10:26 AM, Christian Schneider <
ch...@die-schneider.net> wrote:
> +1 to both
>
> Christian
>
> On 08.10.2014 19:30, Daniel Kulp wrote:
>
>> This is a vote to release CXF 2.7.13 and 3.0.2.There are over 90 JIRA
>> issues resolved for 3.0.2 which is a lot.
>>
>
For instance I want to force choosing username password token for one
method call and then a saml bearer token for all others.
I don't have enough info in the assertor http conduit
+1!
Andriy
On Thu, Oct 9, 2014 at 5:35 AM, Colm O hEigeartaigh
wrote:
> +1.
>
> Colm.
>
> On Thu, Oct 9, 2014 at 10:26 AM, Christian Schneider <
> ch...@die-schneider.net> wrote:
>
> > +1 to both
> >
> > Christian
> >
> > On 08.10.2014 19:30, Daniel Kulp wrote:
> >
> >> This is a vote to releas
Hi
On 09/10/14 10:06, Bin Zhu wrote:
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
Hi,
Following Sergey's e-mail, it is true, CXF does not have support for EJB
resource classes yet.
The work has been done to support CDI 1.1. That's being said, if the EJB
container integrates with CDI container (it should), the CXF can be used
and is going to work as expected.
Thanks.
Best Re
+1,
Andrei.
> -Original Message-
> From: Daniel Kulp [mailto:dk...@apache.org]
> Sent: Mittwoch, 8. Oktober 2014 19:31
> To: dev@cxf.apache.org
> Subject: [VOTE] CXF 2.7.13/3.0.2
>
>
> This is a vote to release CXF 2.7.13 and 3.0.2.There are over 90 JIRA
> issues
> resolved for 3.0
Hi,
Yes absolutely. TomEE supports CDI rest endpoints but also EJB endpoints.
Both are integrated and work together out of the box in TomEE.
Happy to hack on an hello world sample for you if you want.
jean Louis
Hi,
Following Sergey's e-mail, it is true, CXF does not have support for EJB
reso
On Oct 9, 2014, at 5:41 AM, Jason Pell wrote:
> For instance I want to force choosing username password token for one
> method call and then a saml bearer token for all others.
>
> I don't have enough info in the assertor http conduit
In the AlternativeSelector for CXF 3.0.x, we added the Mess
I can't upgrade to 3.x as yet. So I need to figure out a way to do this in
2.7.
On 10/10/2014 4:18 AM, "Daniel Kulp" wrote:
>
> On Oct 9, 2014, at 5:41 AM, Jason Pell wrote:
>
> > For instance I want to force choosing username password token for one
> > method call and then a saml bearer token f
I came up with a really dodgy solution that actually works :-)
https://github.com/pellcorp/cxf/blob/master/JavaFirst/src/main/java/com/pellcorp/client/HttpsConduitAlternativeSelector.java
I loaded up a list of all jaxws clients.
I used reflection to get hold of the endpoint info from the conduit
18 matches
Mail list logo
