+1
Cheers, Sergey
On 01/05/15 18:26, Daniel Kulp wrote:
This is a vote to release 3.0.5 and 2.7.16. It’s been over 2 months since the
last release and we’ve fixed more than 70 issues.
Staging areas:
2.7.16:
https://repository.apache.org/content/repositories/orgapachecxf-1039/
3.0.5:
archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
Hi Dan,
hoping to figure out why Francesco is seeing a regression asap...
Thanks, Sergey
On 29/04/15 14:13, Daniel Kulp wrote:
I’m planning on doing builds for 2.7.16/3.0.5 and 3.1.0 tomorrow. Speak up
fast if there are issues we need to address first.
Thanks!
Hi David
I'd like to ask you, are you still interested to see some CXF-level
integration done with Hystrix ?
Perhaps CXF Failover feature can be adjusted so that a Hystrix feature is
easily implemented on top of it,
Thanks, Sergey
--
View this message in context:
Hi
Thanks for this analysis, I'm looking at the docs, example
https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/javax/ws/rs/core/Response.html#getLink(java.lang.String)
it says:
A relative link is resolved with respect to the actual request URI that
produced this response.
What is the
One more option /post ?
So is it post, ../post, or /post ?
Sergey
On 28/04/15 10:26, Sergey Beryozkin wrote:
Hi
Thanks for this analysis, I'm looking at the docs, example
https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/javax/ws/rs/core/Response.html#getLink(java.lang.String)
it says
Hi - the fix has been done at the HTTP transport level
Thanks, Sergey
On 26/04/15 03:40, iris ding wrote:
CXF only calls asyncResponseImpl.setUnmappedThrowable if
the exception is thrown from ServiceInvokerInterceptor and no exception
mapper has been found for this exception:
Hi
Sure - please open JIRA issues to fix it.
Thanks, Sergey
On 23/04/15 15:35, venkatesham nalla wrote:
Hi
I have general question on JavaScript Web Service client support. Is
this something actively supported or experimental feature only in CXF? I
am working on JavaScript web service client
Hi Aki
Dan is off this week so may be next week it will all be finalized, may
be earlier
Cheers, Sergey
On 23/04/15 11:36, Aki Yoshida wrote:
Hi,
I see #apache-cxf available at freenode but there are much less people
in there than at #cxf at codehaus.
There are more people in #apache-camel
Hi
You are right, thanks for spotting this issue and for your patch
Cheers, Sergey
On 20/04/15 04:17, iris ding wrote:
Hi Sergey,
Let's take a look about the implementation details in
ServiceUnavailableException.getRetryTime():
public Date getRetryTime(Date requestTime)
{
Hi - this is not a CXF issue. Most likely an initialization issue of
this exception class which is part of the JAX-RS API. NPE is used in API
a lot...
Cheers, Sergey
On 18/04/15 04:04, iris ding wrote:
Hi, I have a resource method as below:
@GET
@Path(setmethod)
public String setMethod1()
{
Hi
Thanks for your patch and sorry I forgot to mention your name in the
commit message, the fact you did a patch was appreciated.
I'm not sure to be honest what does it mean to have multiple Links
without a relationship, how would you identify which URI points to what
? May be you use some
Hi
Interesting, we chatted with Aki where he did mention HTTP/2, and I opened
https://issues.apache.org/jira/browse/CXF-6349
I guess we are about to witness a higher demand for a need to push back
to a client a high amount of data real fast. HTTP/2 can be one option
there. We will need to
Hi
I'm not 100% sure but perhaps in some cases the exceptions go directly
to the out fault chain, so registering a custom out fault interceptor
may help
Sergey
On 07/04/15 15:14, Eirik Bjørsnøs wrote:
Hello,
We have implemented a set of interceptors for limiting the number of
concurrent
Hi Dan
On 02/04/15 16:32, Daniel Kulp wrote:
It’s been almost a year since 3.0 and I really thing we need to get 3.1 out.
We’ve done a ton of work getting some new features added in, updates to WSS4J
(and OpenSAML), bunch of JAX-RS enhancements around security, etc…
Thoughts? Other than
Hi Romain
Good observation, I have this JIRA opened for a while:
https://issues.apache.org/jira/browse/CXF-4826
but I got side-tracked into other work over the time...If
isReadable/isWriteable did not need to have a context info in scope then
services like below would not be affected. You
On 26/02/15 12:58, Mike Wilson wrote:
Ok, let's see if other believe TCCL usage is possible to remove altogether.
If not, I'll invest the time to create a ticket with the details of the bug.
In short, it happens when CXF logging is routed to Juli.
Do you have more details re why it breaks with
mailto:mgopinat...@avaya.com
| Chennai, India
The information contained in this e-mail message or messages (which includes
any attachments) is confidential and may be legally privileged. It is intended
only for the use of the person or entity to which it is addressed.
--
Sergey Beryozkin
Are you dealing with some specific side-effects or would just like to
see less of TCCL in CXF ?
I agree with what Christian said - in some cases CXF needs it as it is
not an OSGI-only framework. But if minimizing the use of TCCL is
possible then I guess it is a good idea.
Sergey
On 24/02/15
test.
Thanks, Sergey
On 24/02/15 13:00, Sergey Beryozkin wrote:
Hi Andriy,
David Karlsen is def not proposing to start supporting reactive client
API, it is more about about some advanced fault-tolerance support - we
should actually reply to him I guess.
Thanks for sharing a link though. We
Hi Andriy,
David Karlsen is def not proposing to start supporting reactive client
API, it is more about about some advanced fault-tolerance support - we
should actually reply to him I guess.
Thanks for sharing a link though. We will have to implement it as part
of JAX-RS 2.1 work, and we'd
Hi
On 17/02/15 10:00, David Karlsen wrote:
Hi.
We're going (gradually) from a CXF based JAX-WS world to a CXF based JAX-RS
world.
What is really good about CXF is that it can support combining both
worlds and migrating between the two well.
I have a number of Interceptors to do some custom
, I mean users of cxf 2.7
On Sat, Feb 14, 2015 at 9:30 AM, Jason Pell ja...@pellcorp.com wrote:
From a purely selfish point of view, I hope that 2.7 end of life is
announced well in advance, as a lot of customers will have to migrate to
3.x.
On Sat, Feb 14, 2015 at 4:20 AM, Sergey Beryozkin
On 13/02/15 16:09, Daniel Kulp wrote:
On Feb 13, 2015, at 11:04 AM, Sergey Beryozkin sberyoz...@gmail.com wrote:
On 13/02/15 15:54, Colm O hEigeartaigh wrote:
Can you release WSS4J 2.1 by the end of May/early June (3.5-4 months) ?
At this point I can't commit to it. So I will hold off
the first 3.1.0 6 months from now would probably
mean there will be only single 3.1.x release this year, not sure.
Sergey
Colm.
On Fri, Feb 13, 2015 at 3:45 PM, Sergey Beryozkin sberyoz...@gmail.com
wrote:
On 13/02/15 14:28, Colm O hEigeartaigh wrote:
Any thoughts on a CXF 3.1 release date
On 13/02/15 14:28, Colm O hEigeartaigh wrote:
Any thoughts on a CXF 3.1 release date? I'm updating WSS4J 2.1.0-SNAPSHOT
to use OpenSAML 3.0.x, and would like to merge the corresponding fixes to
CXF trunk. However, WSS4J 2.1 will probably not be released for at least
4-6 months or so I'd imagine,
Hi All,
We've had a brief chat with Dan earlier about the possibility of
introducing a Java 8 trunk after it was announced JAX-RS 2.1 API would
be Java 8 based.
I'd like to justify here why IMHO this would be a very good thing for CXF:
- Java 8 is recognized to have a lot of new language
+1
Sergey
On 12/02/15 01:53, Daniel Kulp wrote:
This is a vote to release 3.0.4 and 2.7.15. It’s been about 2 months since the
last release and we’ve fixed more than 70 issues.
Staging areas:
2.7.15:
https://repository.apache.org/content/repositories/orgapachecxf-1036/
3.0.4:
Hi
On 31/01/15 06:48, ellen wrote:
Hi dear all,
We plan use CXF to develop our JAX-RS 2.0 web service. But I would like to
know first:
Does CXF pass TCK for JAX-RS 2.0, I didn't see it in the page or forum.
If not, do you know when you plan to run the TCK test and get result?
The info is
Hi
Please forward such queries to the users list.
CXF reports whatever is coming in, it may be GET after all.
The best way to 100% validate CXF does not confuse GET with DELETE is to
get your client request passed through some TCP trace utility.
Sergey
On 27/01/15 08:44, jordan wrote:
And I
Hi Dan
On 27/01/15 18:00, Daniel Kulp wrote:
Chatted with Alessio about this on IRC. It looks like a bug in the JDK
introduced in Java7 update 40. A bug was logged:
https://bugs.openjdk.java.net/browse/JDK-8044726
but then closed a non-reproducible. Alessio will look into seeing if that
Hi Andriy
I've looked at IssuedTokenInterceptorProvider, I'm not sure how much
self-contained code we can reuse from that interceptor.
How would a JAXRS client interceptor would look like ? I guess it should
invoke on STSClient and set a SAML assertion on the current message ?
Thanks,
Hi Aki
Not sure about configuring this plugin, may be an alternative plugin
exists which can do the same but also accept the proxy properties ?
The other possible option for doing the local builds without the
internet access, predownload this file and update the build to check the
file from
Hi Thorsten, All,
I've updated OAuth2 SessionAuthenticityTokenProvider interface on the
trunk.
The reason for that is that at the moment the only way for
Redirection-based services to return the redirection state as part of
the authorization decision is to use form hidden fields. That would
Hi Freeman
Thanks, after looking at this code I've realized we can revert the
changes to CXFActivator too - those classes Spring Osgi deals with are
only making sense in OSGi so we can further polish the code - I'll play
a bit later on and let you know about the changes...
Cheers, Sergey
On
Have a look please at the latest commit - that should work...
Cheers, Sergey
On 04/12/14 10:08, Sergey Beryozkin wrote:
Hi Freeman
Thanks, after looking at this code I've realized we can revert the
changes to CXFActivator too - those classes Spring Osgi deals with are
only making sense in OSGi
+1
Sergey
On 03/12/14 16:20, Daniel Kulp wrote:
This is a vote to release CXF 2.7.14 and 3.0.3. These versions fix a bunch of
bugs users have encountered. They also provide some additional functionality
to make it easier to configure various SSL/TLS things to mitigate various
attacks.
Hi Freeman
Thanks for this effort, I did a minor update to avoid updating all of
ClasspathScanner client code (JAX-RS server client for now - but
possibly JAXWS Spring parsers in the future too).
Dan may likely have more comments but for now I have a couple of questions,
- is
.
ClasspathScanner, when instantiated, can figure out if it runs in OSGi
and create the right classpath scanner delegate (so
JAXRSServerFactoryBeanDefiniti__onParser will stay unchanged).
Thanks.
Best Regards,
Andriy Redko
On Wed, Dec 3, 2014 at 6:03 AM, Sergey Beryozkin sberyoz...@gmail.com
Hi
I've just tried, the test is OK, Ubuntu 14.04, Java 7 patch 67.
Can you please retry with the latest Java 7 patch ?
Thanks, Sergey
On 01/12/14 03:11, Jason Pell wrote:
With both Java 6 (patch 37) and Java 7 (patch 60)
On Mon, Dec 1, 2014 at 2:09 PM, Jason Pell ja...@pellcorp.com wrote:
I
something is incompatible with some Ubuntu or JDK version?
If Jason has a green light after rerunning with JDK 1.7.0_67 then I
guess it would be narrow it down to an earlier JDK.
Cheers, Sergey
2014-12-01 11:35 GMT+01:00 Sergey Beryozkin sberyoz...@gmail.com:
Hi
I've just tried, the test
Hi,
I got stuck this morning with releasing Jettison 1.3.7 which is needed
to address a JAXRS JSONProvider improvement issue. I was actually about
to release it yesterday, created a staging repo, but postponed till this
morning to finalize the release and now I'm stuck with Codehauz Nexus
Sonatype/Codehaus team has resolved it so I'll have the commit coming in
shortly
Sergey
On 28/11/14 10:49, Sergey Beryozkin wrote:
Hi,
I got stuck this morning with releasing Jettison 1.3.7 which is needed
to address a JAXRS JSONProvider improvement issue. I was actually about
to release
+1
Cheers, Sergey
On 14/11/14 16:33, Daniel Kulp wrote:
This is a vote to release version 3.0.3 of the XJC utils. The only changes in
this release are related to getting it working better on Windows. On Windows,
in fork mode, many the paths and such passed into the forked process did not
Hi
On 05/11/14 14:40, Daniel Kulp wrote:
For 3.1, I’m thinking about removing the dependencies on spring and spring-dm from
the features.xml file. Right now, if you do a feature:install cxf”, you
would get spring 3.2 and spring-dm forcibly installed even if you don’t need either
of them.
+1
Sergey
On 17/10/14 11:52, Colm O hEigeartaigh wrote:
This is a vote to release Apache CXF Fediz 1.1.2.
Issues fixed:
https://issues.apache.org/jira/browse/FEDIZ/fixforversion/12327120
Tag:
We've had 11 binding votes and one non binding vote, all +1.
This vote passes and I'm going to promote the artifacts on behalf of Dan
Cheers, Sergey
On 07/10/14 21:26, Sergey Beryozkin wrote:
+1
Cheers, Sergey
On 07/10/14 20:59, Daniel Kulp wrote:
This is a vote to release CXF 2.6.16
/201410.mbox/%3c7ff6ea5d-c62a-42fc-9ad4-c58f813ed...@gmail.com%3E
On 08/10/14 21:02, Sergey Beryozkin wrote:
+1
Cheers, Sergey
On 08/10/14 18: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
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 Dan,
The demo issue has been sorted out, sorry about it,
Cheers, Sergey
On 08/10/14 02:11, Daniel Kulp wrote:
Just an follow up…
I was able to fix all the java5 issues and build 2.6.15 and the vote is
started.2.7.13 is built and staged, but I want to look at the staging real
quick
Hi
Redirecting to the users list
Apparently supporting overlapping addresses was causing issues in other
cases where the Jetty transport was used and it was restricted in 3.0.1.
CXF 3.0.2 (the release process is about to start) has a
org.apache.cxf.transports.http_jetty.DontCheckUrl system
+1
Cheers, Sergey
On 08/10/14 18: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
+1
Cheers, Sergey
On 07/10/14 20: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
Hi
Luigi (FH Koln) suggested some good refactoring ideas for the original
oauth2-jwt module, now named oauth2-jose. Specifically, he correctly
pointed out that JWE/JWT is not depending on OAuth2 works, but it is the
other way around where OAuth2 applications may use JWT tokens for a
variety
Hi
Besides that I've started applying the patches on behalf of the FH-Köln
research team, I hope we will see a lot of contributions coming from
them going forward
Cheers, Sergey
On 30/09/14 15:26, Andrei Shakirin wrote:
Hi Jan,
Sergei is developing this topic very active in CXF now.
CXF has
it is becoming supported in Felix/etc
Thanks, Sergey
Christian
On 24.09.2014 15:12, Sergey Beryozkin wrote:
On 24/09/14 13:42, Christian Schneider wrote:
I would like to deploy two (or more) CXF based applications into the
same OSGi framework.
How can I enforce common rules per application while
On 25/09/14 15:07, Christian Schneider wrote:
On 25.09.2014 12:44, Sergey Beryozkin wrote:
Hi Christian
On 25/09/14 08:51, Christian Schneider wrote:
Having one servlet per bundle would definately work.
I see two problems though:
- Each servlet has its own base path where all services reside
segments composed together with only the the public parts of
such an URI contributing to the public endpoint URI; it is indeed
another unique idea to be explored :-)
Thanks, Sergey
On 25/09/14 15:18, Sergey Beryozkin wrote:
On 25/09/14 15:07, Christian Schneider wrote:
On 25.09.2014 12:44
On 24/09/14 13:42, Christian Schneider wrote:
I would like to deploy two (or more) CXF based applications into the
same OSGi framework.
How can I enforce common rules per application while keeping the
applications separate from each other?
I created a wiki page to show the scenario and describe
Hi
On 23/09/14 06:15, jordan wrote:
Hi Sergey,
Great thanks for your quickly response again! :)
I see you said in the end
Yes, if we talk about a JAX-RS 2.0 client invocation path, given that
the documentation for Client API does not require defaulting to some
specific media type if Accept is
This is a question for the users list, use outDropElements to completely
remove a given element
Cheers, Sergey
On 23/09/14 16:39, Nee wrote:
I wanted to remove a tag from the request xml using the below transformation
feature.But it doest not work.If I change the tag nameentry key=currency
.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
+1
Sergey
On 19/09/14 15:11, Jeff Genender wrote:
+1
Jeff
On Sep 19, 2014, at 7:42 AM, Daniel Kulp dk...@apache.org wrote:
This is a vote to release the 3.0.2 version of the XJC Utils.There are two
major changes:
1) Update the plugin to use all the repositories in the pom to find
-MessageBodyWritter-for-List-E-if-Resource-method-is-defined-under-async-y-tp5748709.html
Sent from the cxf-dev mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
Hi
I updated ConfigurableImpl to use LinledHashMap but you can not depend
on the order of filters with the same default priority being preserved
across multiple JAX-RS implementations, for example, in some cases the
filters can be auto-discovered and as a such the order can not be
Hi, no problems, thanks for reporting the issues.
It's in 3.0.2-SNAPSHOT, please test before early if you can, if some
issues are still there then we can fix them in time for 3.0.2
Cheers, Sergey
On 27/08/14 09:02, jordan wrote:
Hi Sergey,
Thanks for your help! You let me learn more. :)
into
Configuration API docs
Cheers, Sergey
On 21/08/14 16:55, Sergey Beryozkin wrote:
Hi,
Please see comments below.
On 21/08/14 13:26, jordan wrote:
Hi Sergey,
Great thanks for your quickly response! :)
I see you opened two defects yesterday:
1. Application context injection:
https://issues.apache.org/jira
Hi,
On 21/08/14 11:53, Michał Woś wrote:
Websocket upgrade request can be done from any origin and by anyone. I
can't find any security means to protect this particular request. Please
advise because I might be missing sth.
The HTTP headers available at the upgrade request will be available to
for your help good day! :)
--
View this message in context:
http://cxf.547215.n5.nabble.com/Configuration-and-Constructor-Context-Injection-problem-when-using-CXF-tp5747973p5748033.html
Sent from the cxf-dev mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http
Hi,
Thanks for sharing these results, let me comment, please see below
On 20/08/14 07:13, jordan wrote:
Hi dear all,
We would like to use JAXRS-2.0 and CXF in our project.
And we would like use some @Context injection in our test.
But I found the Configuration and Singleton Constructor
Cheers, Sergey
On 20/08/14 14:55, Sergey Beryozkin wrote:
Hi,
Thanks for sharing these results, let me comment, please see below
On 20/08/14 07:13, jordan wrote:
Hi dear all,
We would like to use JAXRS-2.0 and CXF in our project.
And we would like use some @Context injection in our test.
But I
Hi,
Your are right, please create a patch.
thanks, Sergey
On 12/08/14 03:34, iris ding wrote:
Hi Guys,
In ExceptionUtils.convertFaultToResponse(), it only catches Exception. So
CXF fails to process the request if we throw Error in our own
XXXExceptionMapper. The definition of ExceptionMapper
with password call back handler, we should add the
private key's password into password callback handler class to decrypt the
saml assertion.
Thanks
Rathnapandi
On Thu, Jul 31, 2014 at 12:15 PM, Sergey Beryozkin [via CXF]
ml-node+s547215n5747169...@n5.nabble.com wrote:
Looks like it's a configuration
Hi
It appears that a wrong DOM element was used to check the EncryptedKey
element which is actually a sibling of EncryptedData, not a child.
I know Colm has very extensively tested it against various IDPs but I
believe none of them were encrypting the SAMLP responses.
I've committed a
-restriction-tp5746712p5746890.html
Sent from the cxf-dev mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
OK, thanks for the clarification...
Note, there's some weakness in the current approach to do with the proxy
being injected for custom interfaces even if no provider for a given
non-standard interface exists, something that Andrey was working upon.
At the moment, in such cases, NPE will be
archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
Hi Alessio
In my new tests around JSON security I'm doing exactly what you propose,
checking if BC is needed, apparently not with Java 8 only as far as GCM
is concerned.
it may be more sensitive in case of WSS4J...
Cheers, Sergey
On 23/07/14 12:44, Alessio Soldano wrote:
Hi,
I've been
--
View this message in context:
http://cxf.547215.n5.nabble.com/context-injection-through-setter-method-method-name-restriction-tp5746712p5746796.html
Sent from the cxf-dev mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http
HttpSerletRequest/etc also have to be supported in mist cases...
Cheers, Sergey
On 23/07/14 15:22, Sergey Beryozkin wrote:
On 23/07/14 12:31, Grant Yang wrote:
This code makes me wonder what will happen if we just have
@Context
public void setString(String string) {
System.out.println(shall
On 23/07/14 17:35, iris ding wrote:
OK, Then Sergey if we want to allow custom context we need support it via
another way..
What do you mean ? CXF supports it its way, different from the Jersey way...
Thanks, Sergey
--
View this message in context:
+1
Thanks, Sergey
On 22/07/14 11:40, Andrei Shakirin wrote:
Hi Iris,
This restriction was already discussed in
http://cxf.547215.n5.nabble.com/Getting-hold-of-JAX-RS-MessageContext-tt5745816.html
.
Yes, it makes sense to relax / drop the restriction.
Could you please create an issue for
hours.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
Hi Chris
On 14/07/14 02:01, Chris Geer wrote:
Christian,
I'm not sure I have specific advice about how to approach Shiro
compatibility without spending some cycles on it. I think we could engage
Les and Shiro community to help though. One possible approach might just be
to have CXF use a
Hi Alessio
On 14/07/14 08:54, Alessio Soldano wrote:
Hi,
while running some performance benchmarks here, we noticed lot of time
spent computing the content-id of multipart MTOM/XOP messages, which is
quite unexpected (at least to me). We have a client consuming a wsdl
which references an
Hi Łukasz
On 10/07/14 12:38, Łukasz Dywicki wrote:
Hey Christian,
Great you brought this discussion. I already started working on
integration between spring security (SS) and cxf, mainly because JAAS
was not sufficient in all our cases and SS provides nice cover to it
such AccessDecisionManager
Hi
On 02/07/14 02:45, iris ding wrote:
Thanks Sergey for your fix for this issue.
But actually I have a question for the fix as it is against spec for support
of subclasses or concrete implementations for DataSource. I have put my
question in https://issues.apache.org/jira/browse/CXF-5835 as
On 02/07/14 10:58, Sergey Beryozkin wrote:
Hi
On 02/07/14 02:45, iris ding wrote:
Thanks Sergey for your fix for this issue.
But actually I have a question for the fix as it is against spec for
support
of subclasses or concrete implementations for DataSource. I have put my
question in https
On Wed, Jun 18, 2014 at 9:32 AM, Sergey Beryozkin sberyoz...@gmail.com
mailto:sberyoz...@gmail.com wrote:
Hi
Should we introduce 3.1.0 trunk and 3.0.x branch respectively ?
May be we should wait till 2.6.x is closed first...
Thanks, Sergey
Hi
Should we introduce 3.1.0 trunk and 3.0.x branch respectively ?
May be we should wait till 2.6.x is closed first...
Thanks, Sergey
Hi
On 11/06/14 21:33, Malintha Adikari wrote:
Hi all,
I am very interesting about getting involve Apache CXF project. As the very
first step I checked out the source code from git and tried to build it in
my local environment. I would like to help increasing the unit test
coverage for the CXF
the client in the old namespace via the
transformation feature will be too complicated in option (1), I would
prefer option (2) with keeping dependency client - frontend.
Regards,
Andrei.
-Original Message-
From: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
Sent: Freitag, 6. Juni 2014 11:57
-us.apache.org/repos/asf?p=cxf-fediz.git;a=commit;h=5500f3cbf061b8f5b2d763e020df35516823d4e6
Issues fixed:
https://issues.apache.org/jira/browse/FEDIZ/fixforversion/12325565/
Here is my +1.
Colm.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http
.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
Hi
In CXF 3.0.0 we've had a client element used to be defined in
jaxrs.xsd shipped with the rt/frontend/jaxrs module moved out (alongside
with the code supporting Client API) to a new jaxrs-client.xsd (with a
new target namespace http://cxf.apache.org/jaxrs-client) now shipped
with the
. So the public jaxrs.xsd will keep supporting CXF
2.x and CXF 3.0.0, jaxrs3x.xsd - CXF 3.0.1 and higher. CXF 3.0.1 will
ship jaxrs.xsd only except that its target namespace will be ending with
/jaxrs3x
Cheers, Sergey
regards, aki
2014-06-06 11:57 GMT+02:00 Sergey Beryozkin sberyoz
Hi Dan
On 06/06/14 17:14, Daniel Kulp wrote:
On Jun 6, 2014, at 11:44 AM, Sergey Beryozkin sberyoz...@gmail.com wrote:
Hi Aki,
thanks for the comments,
On 06/06/14 16:32, Aki Yoshida wrote:
Hi Sergey,
Maybe, I am not getting the down side of option 1 right. Option 1
means, the schema
Hi Dan
It appears the update has caused 3.0.1 effectively 'dropping' Java 6
support from CXF 3.0.1, I'm seeing the build errors like
[ERROR]
rt/ws/policy/target/generated/src/main/java/org/apache/cxf/ws/policy/v200607/OperatorContentType.java:[59,122]
cannot find symbol
[ERROR] symbol :
and 3.0.5. Both worked.
I’ll try on my Linux box later today.
Sorry, was just going to start a build with the latest java 6, I had the
build picking up Java6 26. Will get back shortly
Cheers, Sergey
Dan
Dan
On Jun 5, 2014, at 5:04 AM, Sergey Beryozkin sberyoz...@gmail.com wrote
All works with JDK 1.6.45, sorry about the noise :-), some bug with the
Java 6 26
Thanks, Sergey
On 05/06/14 14:33, Sergey Beryozkin wrote:
Hi Dan
On 05/06/14 14:30, Daniel Kulp wrote:
On Jun 5, 2014, at 8:15 AM, Daniel Kulp dk...@apache.org wrote:
Is anyone else able to reproduce
301 - 400 of 1210 matches
Mail list logo
