+1
- Dennis
On 06/06/2015 08:49 AM, Daniel Kulp wrote:
3.1.1 fixes a bunch of issues in 3.1.0 that would prevent it from working
properly in several normal use cases, particularly in OSGi.
Staging area:
https://repository.apache.org/content/repositories/orgapachecxf-1044/
Tag:
https://git-
+1
- Dennis
On 05/02/2015 05:30 AM, Daniel Kulp wrote:
It’s been a year since the 3.0.0 release and we’ve made a bunch of significant
improvements. We really need to get this out. :-)
This also include the latest cxf-build-utils which allows CXF to import into
the latest Eclipse plugi
+1
- Dennis
On 05/02/2015 05:26 AM, 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:
https:/
+1
- Dennis
On 02/12/2015 02:53 PM, 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:
https:
+1
- Dennis
On 12/04/2014 05:20 AM, 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
att
+1
- Dennis
On 10/09/2014 06:37 AM, Jeff Genender wrote:
+1
Jeff
On Oct 8, 2014, at 11:30 AM, 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;
+1
- Dennis
On 10/08/2014 08:59 AM, 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 i
+1
- Dennis
On 09/11/2014 08:53 PM, Willem Jiang wrote:
Hi,
As there is no plan for support jibx with JDK8[1], and some system tests failed
with JDK8.
I’m planing to move these JiBX related system tests into the other module
called JiBX, so we can skip the module when using JDK8.
Any thou
+1
- Dennis
On 07/16/2014 07:57 AM, Daniel Kulp wrote:
This is a vote to release the latest patch releases on all three branches.
There are over 80 fixes for 3.0.1 with most back ported to 2.7.12 and some to
2.6.15.
Note: this is expected to be the last release of the 2.6.x branch.
Tags:
+1
- Dennis
On 05/31/2014 09:31 AM, Christian Schneider wrote:
+1
Christian
Am 30.05.2014 21:10, schrieb Daniel Kulp:
This is a vote to release a 3.0.0 version of our XJC utils.
This fixes a bunch of issues that I’ve found and users have found.
It also updates to the latest JAXB which w
I don't think the JiBX support should be any concern. I haven't been
maintaining the JiBX code for some time, and the Java 8 issue is
probably the last nail in the coffin.
A new release of BCEL might let JiBX limp along a little longer, but
BCEL has been obsolete for a long time. I would have
+1
- Dennis
On 05/15/2014 08:13 AM, Daniel Kulp wrote:
This is a vote to release CXF 3.0.0.It’s been a long time coming, but I
think it’s ready to be released. :-)
Staging area:
https://repository.apache.org/content/repositories/orgapachecxf-1019/
Tag:
https://git-wip-us.apache.org/r
t’s left. :-)
Dan
On May 12, 2014, at 2:58 PM, Dennis Sosnoski wrote:
Hi Dan,
RM is broken for oneway operations with a decoupled endpoint at present. I'm
trying to track the problem down, and Aki has also taken a look. If I can't fix
it myself I'll add a test case so you ca
I reverted the change yesterday, so let me know if you're still seeing
any problems. I don't know why I didn't see the issues with the
integration tests, which led to Dan changing the order, before I checked
in the original change. Normally I run the RM integration tests before
every commit. So
andling, I
discovered that that special handling is needed for RM 1.0. because RM
1.0. has a pseudo CloseSequence behavior using its lastMessage action.
I'll run some more tests with the corrected modification and submit
this change if everything is fine.
regards, aki
2014-05-14 3:53 GMT+02:00
Hi Aki,
We definitely don't want that Sequence header on the CloseSequence
message. That code has been in place since I split the interceptors, so
it's probably just a mistake from when I was doing the split. I'll take
out the added clause on the if.
Thanks for catching this, Aki!
- Denni
ime on it today, but if you're ready to go with 3.0.0 it can
probably wait for 3.0.1.
Thanks,
- Dennis
On 05/14/2014 03:07 AM, Daniel Kulp wrote:
Dennis,
Any updates? Just trying to figure out what’s left. :-)
Dan
On May 12, 2014, at 2:58 PM, Dennis Sosnoski wrote:
Hi Dan,
Hi Dan,
RM is broken for oneway operations with a decoupled endpoint at present.
I'm trying to track the problem down, and Aki has also taken a look. If
I can't fix it myself I'll add a test case so you can take a look.
I don't know that this would qualify as a show stopper, but it's pretty
its behavior by
passing
some properties in the client context and that won't work if those
properties are not copied into the new client's context.
regards, aki
2014-04-24 13:28 GMT+02:00 Dennis Sosnoski mailto:d...@sosnoski.com>>:
&g
Hi Jim,
Which version of the code are you using? I've been working on combining
WS-RM and WS-Security in the 3.0 code. There are still some pieces that
need to be put in place (especially persisting the security properties
so messages can be retransmitted), but the basic security+rm operation
+1
- Dennis
On 04/09/2014 03:44 PM, Daniel Kulp wrote:
It’s been 2 months since the last releases… This is a vote to release 2.7.11
and 2.6.14.
There are over 60 issues fixed for 2.7.11 and more than 20 ported back to
2.6.14.
This second attempt fixes the blueprint parsing issues that A
+1
- Dennis
On 04/07/2014 04:34 AM, Daniel Kulp wrote:
It’s been 2 months since the last releases… This is a vote to release 2.7.11
and 2.6.14.
There are over 60 issues fixed for 2.7.11 and more than 20 ported back to
2.6.14.
Staging area:
https://repository.apache.org/content/repositori
+1 removing SOAP TCP
+1 (to warning people for now, dropping Java 6 in an upcoming 3.x release)
+1 2.6 final
- Dennis
On 03/25/2014 07:49 AM, Jeff Genender wrote:
+1 to removing the unfinished GSOC… makes no sense to keep it.
+1 to Java 6, but I would mark it as deprecated and be removed i
, aki
2014-02-17 22:13 GMT+01:00 Dennis Sosnoski :
I guess the question is whether we want to duplicate the JMX functionality.
My thought was to keep this callback really simple, but still supply the
essential information (basically, that the message has made it through to
the far end) to the clie
umber and even some control over the messages
and sequences it created?
Or I am not sure if we should give the sequence info back in the
callback and let the client use jmx to get more info and exercise
control over the sequence?
regards, aki
2014-02-14 8:15 GMT+01:00 Dennis Sosnoski :
It's
+1
- Dennis
On 02/15/2014 03:01 PM, Daniel Kulp wrote:
This is a vote to release 3.0.0-milestone2
This has a bunch of more updates targeting 3.0 including a fully revamped JMS
transport, fully revamped WS-RM system, updates to WS-Security, JAX-RS updates,
some more deprecated API’s removed
It's important for clients using WS-RM to know when all the messages
they've sent have been acknowledged, because it's not safe for them to
terminate until this has been done. Right now we're able to use JMX to
monitor WS-ReliableMessaging operation and see when messages are
acknowledged. But t
MUST be
integrity protected."
Anyway, that’s my reading of it.
Dan
On Feb 13, 2014, at 6:43 PM, Dennis Sosnoski wrote:
In testing Metro interop I noticed that if I only specified:
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";>
In testing Metro interop I noticed that if I only specified:
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";>
CXF happily generated messages signing only the Body, but Metro
apparently requires the WS-A headers (at least MessageID) to be signed
+1
- Dennis
On 02/07/2014 07:29 AM, Daniel Kulp wrote:
This is a vote to release 2.6.13 and 2.7.10.
For 2.7.10, this is mostly to fix the JAX-WS 2.2 problems in the 2.7.9 release
that would not allow it to work as a 2.2 runtime. Also has a couple other
minor fixes.
Both builds also hav
+1
- Dennis
On 02/05/2014 04:08 PM, Daniel Kulp wrote:
This is a vote to release 2.7.10. This is mostly to fix the JAX-WS 2.2
problems in the 2.7.9 release that would not allow it to work as a 2.2 runtime.
Also has a couple other minor fixes.
Staging area:
https://repository.apache.org
+1
- Dennis
On 01/30/2014 11:03 AM, Daniel Kulp wrote:
We've resolved over 60 issues since 2.7.8 and almost 40 ported back to 2.6.12.
List of issues:
2.6.12
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12325599
2.7.9
https://issues.apache.org/jira/secur
+1
I'm using git-svn now, would love to have git direct.
- Dennis
On 01/22/2014 10:20 PM, Christian Schneider wrote:
Recently many apache projects switched from svn to git (like Camel and
Karaf).
As git has many advantages compared to svn (especially for back ports)
I think it makes sense t
+1
- Dennis
On 11/27/2013 06:26 AM, Daniel Kulp wrote:
This is a vote for the actually distributions to go along with the
3.0.0-milestone1 release that is already in central.
Staging area:
https://repository.apache.org/content/repositories/orgapachecxf-008/
Now already part of the 3.0.0-mi
+1
- Dennis
On 11/21/2013 10:28 AM, Daniel Kulp wrote:
We’ve done quite a lot of work toward 3.0.0. While we still have work to do, I
think it’s a good idea to get a stable milestone release out that users can
depend on to start testing some of the new stuff and provide feedback about
som
+1
- Dennis
On 11/21/2013 05:20 AM, Daniel Kulp wrote:
We've resolved over 75 issues since 2.7.7 and almost 35 ported back to 2.6.11.
List of issues:
2.6.11
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12325006
2.7.8
https://issues.apache.org/jira/secure
On 10/12/2013 11:23 AM, Dennis Sosnoski wrote:
On 10/12/2013 05:17 AM, Daniel Kulp wrote:
On Oct 11, 2013, at 7:46 AM, Dennis Sosnoski wrote:
I recently made some changes to support WS-RM operating over
WS-SecureConversation. As part of this I needed to do some policy
manipulation supported
On 10/12/2013 05:17 AM, Daniel Kulp wrote:
On Oct 11, 2013, at 7:46 AM, Dennis Sosnoski wrote:
I recently made some changes to support WS-RM operating over
WS-SecureConversation. As part of this I needed to do some policy manipulation
supported by the EndpointPolicyImpl class but not in the
I recently made some changes to support WS-RM operating over
WS-SecureConversation. As part of this I needed to do some policy
manipulation supported by the EndpointPolicyImpl class but not in the
EndpointPolicy interface (which also required PolicyEngineImpl rather
than PolicyEngine, and the s
+1
- Dennis
On 09/19/2013 05:08 AM, Daniel Kulp wrote:
We've resolved over 90 issues since 2.7.6 and almost 50 ported back to 2.6.10.
This second attempt fixes some regressions in the JAX-WS TCK as well as some
issues within Eclipse RCP framework.
This also includes an update release o
I'm working on implementing WS-I Reliable Secure Profile
(http://www.ws-i.org/Profiles/ReliableSecureProfile-1.0.html), which
sets out rules for how to use WS-ReliableMessaging over
WS-SecureConversation. One of the rules is that the WS-RM CreateSequence
message needs to reference the security
+1
- Dennis
On 09/15/2013 12:36 AM, Daniel Kulp wrote:
We've resolved over 90 issues since 2.7.6 and almost 50 ported back to 2.6.10.
This also includes an update release of our build-utils to get the PMD stuff
needed to work with the latest Eclipse.
List of issues:
2.6.10
https://issue
managedEndpoint.getObjectName();
instrumentationManager.register(rtMBean, name);
Then I can just call the sendNotification() method on the
RequiredModelMBean to pass notifications on to the client.
- Dennis
On 09/11/2013 08:34 PM, Dennis Sosnoski wrote:
I'm trying to get JMX notifications working from the WS-RM code, t
I'm trying to get JMX notifications working from the WS-RM code, to
allow the application to monitor message acknowledgments. If I just
implement the notification handling in the managed class
(ManagedRMEndpoint) it looks like this doesn't get picked up by the
dynamic proxy generated by the man
this seems to be
'as designed'. Maybe a bit of topic but wanted to mention this while you
guys are looking into the terminate sequence.
regards,
John
On Mon, Sep 2, 2013 at 11:49 PM, Dennis Sosnoski wrote:
On 09/03/2013 02:48 AM, Aki Yoshida wrote:
...
I think, as long as the
On 09/03/2013 02:48 AM, Aki Yoshida wrote:
...
I think, as long as the client either terminates each unused old
sequence or keeps reusing the old sequence, it is well behaved. In
contrast, when the client keeps creating a new sequence and never
terminates those sequences, it's a bad client for h
let the ws-rm runtime terminate
the sequences periodically.
regards, aki
2013/9/1 Dennis Sosnoski :
Right now WS-RM handling allows the user to configure sequence termination
on shutdown, but defaults to no termination of sequences. This looks like an
incorrect default, since WS-RM relies on ha
Right now WS-RM handling allows the user to configure sequence
termination on shutdown, but defaults to no termination of sequences.
This looks like an incorrect default, since WS-RM relies on having a
TerminateSequence message in order to free up resources at the
destination. I'd like to chang
+1
- Dennis
On 07/18/2013 04:57 AM, Daniel Kulp wrote:
We've resolved over 75 issues since 2.7.5 and almost 50 ported back to 2.5.11
and 2.6.9.
This also includes an minor 2.6.2 release of xjc-utils to get the update to the
boolean getter plugin that was requested.
List of issues:
2.5.1
Perhaps John can tell you what he did to get it working. I'll check into
that myself next week.
Thanks,
- Dennis
On 07/16/2013 11:54 PM, Carlos Aza wrote:
Hello,
Thank you for your response.
John said in his very first comment "After a struggle the createSequence
call is
successfully fini
Although there are problems in using WS-RM and WS-Security together with
the existing code I don't think this is one of them. If you look back to
John's original post, his issue was that the timestamp was not being
updated on retransmissions. This looks like more of a configuration issue.
I'm
Hi Carlos,
I'm working on fixing these issues now, specifically on the combination
of WS-RM with WS-SecureConversation. This is the configuration specified
by the WS-I Reliable Secure Profile
(http://www.ws-i.org/Profiles/ReliableSecureProfile-1.0-2010-11-09.html).
But you left out the error
Any idea when we're going to have a 3.0.0 release off trunk? I've
implemented WS-RMP 1.2 support and I'm now working on cleaning up the
WS-RM 1.2 operation. Could backport to 2.7.x (with some work - there are
a lot of changes), but there are probably going to be some minor API
changes so just i
+1
- Dennis
On 07/04/2013 06:39 AM, Daniel Kulp wrote:
For 3.0, I'd like to combine both cxf-api and cxf-rt-core into a single
jar/bundle. I'd likely just call it cxf-core, but I'm open to other
suggestions (cxf-kernel?).
We originally tried to have a separate jar for "api" to make javad
b the latest WSS4J
snapshot. That usually works. Maven normally checks once a day, but you may
have just missed a deploy of a snapshot or similar, particularly in your
timezone. :-)
Dan
On Jun 11, 2013, at 9:05 PM, Dennis Sosnoski wrote:
Over the weekend I was unable to build due to ma
Over the weekend I was unable to build due to massive failures in
cxf-rt-ws-security. They cleared up for a while yesterday, but now
they're back again, basically NoSuchMethod errors on all the Stax tests:
...
testEncryptConfig(org.apache.cxf.ws.security.wss4j.StaxToDOMRoundTripTest)
Time elap
+1
- Dennis
On 05/11/2013 01:22 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/S
+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/S
+1
- Dennis
On 05/05/2013 12: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/
+1
- Dennis
On 03/29/2013 10:09 AM, Daniel Kulp wrote:
We've resolved over 80 issues since 2.7.3, which is a bunch
List of issues:
2.5.10
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12324007
2.6.7
https://issues.apache.org/jira/secure/ReleaseNote.jspa?
+1
- Dennis
On 02/14/2013 07:05 AM, Daniel Kulp wrote:
There is a problem with the features.xml file for 2.6.6 where a property wasn't
expanded. This is a vote to release a 2.6.6.1 versioned features file only
that pulls in the 2.6.6 bundles, but correct the property expansion.
Staging
Hi John,
I did most of the work required for WS-RMP support last year, when I
opened https://issues.apache.org/jira/browse/CXF-4139. But I got
distracted by other projects, and my work-in-progress was outdated by
other changes. It's coming up on the one year anniversary, so probably
time to g
+1
- Dennis
On 01/30/2013 03:30 AM, Daniel Kulp wrote:
We've resolved over 35 issues since 2.7.2. Not a huge number, but sufficient.
List of issues:
2.5.9
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12323912
2.6.6
https://issues.apache.org/jira/secu
+1
- Dennis
On 05/31/2012 06:15 AM, Daniel Kulp wrote:
We've resolved over 90 issues since 2.6.0 was released. We've back ported
over 70 of them to 2.5.4 and 40 to 2.4.8 and 25 to 2.3.11.
List of issues:
2.3.11:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&ver
+1
- Dennis
On 04/13/2012 08:26 AM, Daniel Kulp wrote:
It's been 6 months since the 2.5.0 release and thus it's time for the 2.6
release. We've been VERY busy with many new features, lots of refactoring,
bunch of OSGi enhancements, etc... The migration guide at:
http://cxf.apache.org/doc
+1
- Dennis
On 04/13/2012 08:23 AM, Daniel Kulp wrote:
We've resolved over 110 issues since 2.5.2 which is a very large amount.
We've back ported over 75 of them to 2.4.7 and 25 to 2.3.10. These patch
releases are certainly overdue.
List of issues:
2.3.10:
https://issues.apache.org/jira/
Hi Aki,
On reviewing the code, I think you'll also need to make a change to
Destination.acknowledge() for this to work correctly. Right now
Destination.acknowledge() is what persists the received message to the
store, so if it's not called until processing is complete messages will
never be persis
SecurityTokenReference, as you pointed out. I have just committed a
> fix for this here:
>
> http://svn.apache.org/viewvc?view=revision&revision=1243996
>
> Could you try with WSS4J 1.6.5-SNAPSHOT and let me know how you get
> on? You will also need Santuario 1.5.0 if you a
I've checked in fixes for broken tests when run offline in tools/javato
and services/wsn/wsn-core. The former needed swaref.xsd for the
http://ws-i.org/profiles/basic/1.1/xsd namespace, while the latter
needed addressing.xsd for the http://www.w3.org/2006/03/addressing
namespace.
In both cases I u
t;>
2012-02-10T11:53:52.568Z
2012-02-10T11:58:52.568Z
http://www.w3.org/2001/04/xmlenc#";
Id="EK-3325E85711A0FD3C1013288748329521">
http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"/>
http://www.w3.org/2000/09/xmld
On 11/19/2011 10:55 AM, Daniel Kulp wrote:
> ...
> How about something along the lines of: create some sort of response message
> thing in the ServiceModel to make sure it's not treated as a one-way. Then
> likely add an interceptor on the out chain (at the very beginning) that would
> grab th
n't thought about it and maybe I am missing the details.
Regards, aki
2011/11/16 Dennis Sosnoski:
I'm having trouble implementing the WS-MakeConnection MakeConnection
operation, and I'm hoping somebody can give me some pointers. The problem is
that even though this looks like a S
I'm having trouble implementing the WS-MakeConnection MakeConnection
operation, and I'm hoping somebody can give me some pointers. The
problem is that even though this looks like a SOAP operation, it really
is not - the response can be anything that's waiting for the endpoint,
with no predefine
+1 (non-binding)
- Dennis
On 10/29/2011 12:32 PM, Daniel Kulp wrote:
It's been over 6 month since 2.4.0 was released. Since then, we've added
quite a bit of new functionality, new features, enhancements, etc... Thus,
time for a release!
The maven staging area:
https://repository.apache.
Hi Dan,
I'm working on getting the WS-MakeConnection support in place, and
expect to have that working by the end of the week.
Aside from that, I saw you'd fixed some issues in the interface to JiBX,
and mentioned having to work around some issues in the JiBX code itself.
What were the JiBX
strom wrote:
I'd really like to get the blueprint httpj: stuff in for that.
On Oct 7, 2011, at 9:23 PM, Dennis Sosnoski wrote:
How do people feel about getting out a 2.5.0 release? It looks like we've got
some very nice new features either added or in the process of being added to
the tru
How do people feel about getting out a 2.5.0 release? It looks like
we've got some very nice new features either added or in the process of
being added to the trunk, and it'd be good to have a timeline in place
for the release.
- Dennis
+1
- Dennis
On 10/05/2011 07:09 AM, Daniel Kulp wrote:
We've resolved over 94 issues since 2.4.2 and thus is time for a release and
over 40 issues ported back for 2.3.7.
List of issues:
2.4.3:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12317593
2.3.7
Dennis Sosnoski:
Hi Aki,
I added the test code to verify proper server-side handling of different
protocol variations (http://svn.apache.org/viewvc?rev=1166927&view=rev) so
if you want to try changing how RMEndpoint works, go ahead.
- Dennis
On 08/25/2011 05:30 PM, Dennis Sosnoski wrote:
Hi Aki,
I added the test code to verify proper server-side handling of different
protocol variations (http://svn.apache.org/viewvc?rev=1166927&view=rev)
so if you want to try changing how RMEndpoint works, go ahead.
- Dennis
On 08/25/2011 05:30 PM, Dennis Sosnoski wrote:
On 08/18/
On 09/01/2011 09:15 PM, Aki Yoshida wrote:
> As Dennis says in his reply, the RM spec doesn't talk about this
> transportation binding specific part. The reason, I suppose, is that
> this is implicitly covered by the normal WS BP profile that recommends
> the use of HTTP 202 if there is nothing to
On 09/01/2011 12:51 PM, Daniel Kulp wrote:
> On Wednesday, August 31, 2011 11:27:20 PM Aki Yoshida wrote:
>
>> For example, when a WS-RM client with a decoupled endpoint sends an
>> application message, the WS-RM server returns simply an HTTP 202
>> response with no content, as the real response i
On 08/18/2011 11:32 PM, Aki Yoshida wrote:
> Hi Dennis,
>
> 2011/8/17 Dennis Sosnoski :
>> Hi Aki,
>>
>> On 08/18/2011 09:25 AM, Aki Yoshida wrote:
>>> ...
>>>
>>> RMManager now manages endpoints under each supported protocol
>>> v
Hi Aki,
On 08/18/2011 09:25 AM, Aki Yoshida wrote:
> ...
>
> RMManager now manages endpoints under each supported protocol
> variation using Map>.
> Does this mean that an Endpoint can be used in several protocol variations?
Yes. I decided to take this approach because I wanted the WS-RM
serversi
Hi Freeman,
It seems like WS-Notification really is just a web service application
that can run on CXF. Do you see a reason for it to be integrated into
the CXF codebase?
- Dennis
On 07/08/2011 09:36 PM, Freeman Fang wrote:
Hi Team,
Recently we're discussing on Servicemix Dev mailling l
JiBX/WS (http://www.jibx.org/jibxws) may be a better choice for you, if
you're just doing web services without WS-Security and such. Android
includes an XmlPullParser
(http://developer.android.com/reference/org/xmlpull/v1/XmlPullParser.html),
which is the only runtime dependency for JiBX and Ji
you say which other stacks this is being tested against?
>
> Dan
>
>
>
> On Saturday, June 18, 2011 2:04:24 PM Dennis Sosnoski wrote:
>> I've finally managed to catch up with updates long enough to check a
>> working version of my restructured WS-ReliableMe
I've been dealing with a lot of EasyMock unit tests in the WS-RM
restructuring, and found what I'd consider to be a design flaw with
EasyMock (or a flaw in the way the unit tests are using it, however you
want to see it). When you use EasyMock.expect(...) by default EasyMock
requires one and only o
I've finally managed to catch up with updates long enough to check a
working version of my restructured WS-ReliableMessaging code into trunk.
Some of the unit tests and systests are commented out for now due to
other changes in the code base from the version I was using for
development, but I'll ge
;m wondering if the others are cached somewhere or are
being provided to Spring via some configuration mechanism.
Thanks for any suggestions,
- Dennis
On 06/12/2011 01:25 PM, Dennis Sosnoski wrote:
> Ok, I'll try to get this set up.
>
> - Dennis
>
>
> On 06/12/2011 01:2
ap remote url to the local one.
>
> Freeman
>
> On 2011-6-12, at 上午6:28, Dennis Sosnoski wrote:
>
>> I've been trying to fix some sys test problems with new code while
>> running offline, and have run into problems with Spring apparently
>> trying to load schem
I've been trying to fix some sys test problems with new code while
running offline, and have run into problems with Spring apparently
trying to load schema definitions. Here's a typical exception:
Caused by: org.apache.cxf.binding.soap.SoapFault:
org.springframework.beans.factory.xml.XmlBeanDefini
+1
- Dennis
On 06/10/2011 02:38 PM, Daniel Kulp wrote:
> We've resolved over 100 issues since 2.4.1 and thus is time for a release.
>
> This is take #2 fixing the attachment issue I found while testing with Camel.
>
> List of issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?pro
+1
- Dennis
On 06/10/2011 02:37 PM, Daniel Kulp wrote:
>
> We've resolved over 58 issues since 2.3.4 and thus is time for a release.
>
> This is take #2 fixing the attachment issue I found while testing with Camel.
>
>
> List of issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
+1
- Dennis
On 06/10/2011 05:55 AM, Daniel Kulp wrote:
> We've resolved over 100 issues since 2.4.1 and thus is time for a release.
>
> List of issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12316354
>
> The Maven staging areas are at:
> https://rep
+1
- Dennis
On 06/10/2011 05:53 AM, Daniel Kulp wrote:
> We've resolved over 58 issues since 2.3.4 and thus is time for a release.
>
> List of issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12316355
>
> The Maven staging areas are at:
> https://repo
I've (mostly) completed a restructuring of the WS-RM code and tests to
allow interoperability with other stacks using WS-Addressing 1.5 with
WS-RM 1.0, and to add support for WS-RM 1.1/1.2. To avoid any
compatibility issues I've kept the CXF defaults to WS-RM 1.0 using the
submission (http://sc
Sounds great, Aki. Why don't you go ahead and commit your fix?
- Dennis
On 04/22/2011 10:20 AM, Aki Yoshida wrote:
Hi,
this is an old issue discussed in
http://cxf.547215.n5.nabble.com/Any-idea-why-ws-rm-ServerPersistenceTest-fails-from-time-to-time-td3298549.html
and tracked in CXF-3179.
I
+1
- Dennis
On 04/13/2011 07:51 PM, Daniel Kulp wrote:
> It's been about 6 months since the release of 2.3 and we've done a fantastic
> job implenting new features and cleaning up various parts of the code and
> integrating new versions of libraries like WSS4J, Neethi, XmlSchema, etc...
>
+1
- Dennis
On 04/13/2011 07:42 PM, Daniel Kulp wrote:
>
> We've resolved over 59 issues since 2.3.3 and thus is time for a release.
>
> List of issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12316074
>
> The Maven staging areas are at:
> https://re
1 - 100 of 163 matches
Mail list logo
