Re: Inconsistent HTTP response code returned for WS-RM scenarios

Hi, regarding this HTTP 202 problem for a piggybacked WS-RM ack response, I created the jira entry: CXF-3004 Inconsistent HTTP response code 202 returned for WS-RM piggybacked Ack response message regards, aki

Re: Status of WS-RM

On Mon, Nov 15, 2010 at 8:21 PM, Daniel Kulp wrote: > On Monday 15 November 2010 12:05:56 pm Scott Came wrote: >> Thanks, Daniel. >> What about the potential to leverage Sandesha or the implementation in >> Metro?  My research has indicated that some time ago there was discussion >> about trying t

Adding more controls to the current WS-RM component

Hi, I have been using the CXF WS-RM component for a while. And I can say, I am enjoying it. Right now, among others, I am experimenting with some ideas to get more control over its behavior and more robustness in certain situation. I would like to share these ideas. In particular, I am describing t

Re: Adding more controls to the current WS-RM component

2011/3/17 Dennis Sosnoski : > On 03/17/2011 12:40 PM, Aki Yoshida wrote: >> >> ... >> >> 1. Retry Behavior at Source Sequence >> Currently, there is no maximum retry count and a retry can run forever >> if the message is not acknowledged. I would like t

Using CachedOutputStream insted of byte[] in WS-RM

Hi, In working on the issue to remove the byte array from RMMessage (CXF-1100), I changed RMMessage to use CachedOutputStream instead of the byte[]. I understand that there will be an additional change required in the future to move the persistence before the WS-Security processing step so that the

Re: Adding value to WS-RM feature

Hi Dennis, I don't know what you are exactly intending to do. Does this mean we are going to have the WS-RM 1.1? My understanding was that the current CXF WS-RM implementation used the 2004/08 WSA NS (or in other words, it internally uses the 2005/08 WSA NS but converts it to the 2004/08 WSA versi

Re: Adding value to WS-RM feature

Hi Dennis, Do you want to add a plain string content element in the wsrm-mgr:reliableMessging element? In that case, you can add the element declaration in rmElements group then you add the setAddressingNamespace method in RMFeature public void setAddressingNamespace(String addressingNa

Re: Adding value to WS-RM feature

s M. Sosnoski >> Java SOA and Web Services Consulting <http://www.sosnoski.com/consult.html> >> Axis2/CXF/Metro SOA and Web Services Training >> <http://www.sosnoski.com/training.html> >> Web Services Jump-Start <http://www.sosnoski.com/jumpstart.html> >>

Re: Adding value to WS-RM feature

ing beyond what is described in the XML schema, this is a valid option to consider. regards, aki 2011/3/28 Aki Yoshida : > Hi Dennis, > okay. I got what you mean. I think there is no simple way to generate > a single JAXB class to have the same named element to have more than > one spec

Re: Adding value to WS-RM feature

re else in > CXF where this approach has been used? If there's a precedent, I'm willing > to give it a try. > >  - Dennis > > > On 03/28/2011 11:38 PM, Aki Yoshida wrote: >> >> Hi Dennis, >> on the second thought, I think option 4 isn't complica

Re: Adding value to WS-RM feature

/3/29 Dennis Sosnoski : > Hi Aki, > > On 03/29/2011 04:19 AM, Aki Yoshida wrote: >> >> ... >> But in any case, if we don't go for this modified class approach, we >> might take option 2. >> I think this option isn't bad, considering that we need to du

Re: [RESULT] [VOTE] Aki Yoshida for CXF committer

Wednesday 06 April 2011 12:03:35 PM Daniel Kulp wrote: >> I'd like to call a vote on adding Aki Yoshida as a committer for CXF. >> >> Aki has been active with CXF for almost a year now.   In that time, he's >> submitted patches to 8 JIRA issues, including one th

Re: Any idea why ws.rm.ServerPersistenceTest fails from time to time?

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 also thought the cause to be some timing issue. I needed to have this test case to succeed more reliably. But sometimes e

Re: FileUtils.getStringFromFile issue when using XML

Hi, you are right. The normalizeCRLF() method should not add an extra space at the begining. We can fix this particular issue. But there is one open question, as the exact purpose (use case) of this method is not clear to me. Why do we need this normalization method that just removes all the CRs a

Re: FileUtils.getStringFromFile issue when using XML

Sorry, I realized this method has actually nothing to do with XML. please ignore my comments on XML normalization. regards, aki 2011/5/3 Aki Yoshida : > Hi, > you are right. The normalizeCRLF() method should not add an extra > space at the begining. We can fix this particular issue. >

Re: FileUtils.getStringFromFile issue when using XML

testing as well. Let me know what > you'd like me to do. > > Thanks again, > Tom Eastmond > > On Tue, May 3, 2011 at 6:19 AM, Aki Yoshida wrote: >> Sorry, >> I realized this method has actually nothing to do with XML. >> please ignore my comments on XML norma

org.apache.cxf.endpoint.EndpointImpl may not be used as a hash map key

Hi, While analyzing a problem in WS-RM, which I describe later, I discovered this problem. I will mention it on this dev@cxf list because potentially other components may be affected as well depending on how they are using the instances of this class. This EndpointImpl class extends AbstractAttrib

Re: org.apache.cxf.endpoint.EndpointImpl may not be used as a hash map key

th the original usage intention of this Endpoint object and I would like to hear your comments before creating a jira ticket to fix the mentioned WS-RM issue. For details, please refer to the below message, sorry for its length. Thanks. regards, aki 2011/5/13 Aki Yoshida : > Hi, > While anal

Re: org.apache.cxf.endpoint.EndpointImpl may not be used as a hash map key

as the key. But calling this method creates a new string, so I think we can rather stay with the fixed Endpoint or try to see if EndpointInfo can be used as the key. Regards, aki 2011/5/18 Daniel Kulp : > On Tuesday, May 17, 2011 10:23:29 AM Aki Yoshida wrote: >> Hi CXF-developers, >

jenkins build problem with jaxrs tests CXF-Trunk-​JDK15 #2084

Hi, My change in DestinationRegistrationImpl to fix CXF 3510 was indicated to be the reason for this jaxrs test problem. I will investigate this. Regards, aki

Re: jenkins build problem with jaxrs tests CXF-Trunk- JDK15 #2084

ter a clean build. regards, aki 2011/5/23 Sergey Beryozkin : > Hi Aki > > On Mon, May 23, 2011 at 10:23 AM, Aki Yoshida wrote: >> Hi, >> My change in DestinationRegistrationImpl to fix CXF 3510 was indicated >> to be the reason for this jaxrs test problem. >> I will

Re: jenkins build problem with jaxrs tests CXF-Trunk- JDK15 #2084

the problem has disappeared. Regards, aki 2011/5/23 Sergey Beryozkin : > Hi Aki > > On Mon, May 23, 2011 at 12:17 PM, Aki Yoshida wrote: >> Hi Sergey, >> I need to set up my xchat. Somehow I am having a problem connecting to >> irc.codehaus.org. >> > Here ar

Using different DB drivers for RMTxStore?

Hi, My question is about whether we have a statement about which DB drivers are supported by RMTxStore. I saw CXF-3534 that complains the 2.4.0 version of RMTxStore no longer works for the Oracle driver because of the change in one of the SQL types used in the table definition. The previous versi

Re: Move trunk to 2.5 after 2.4.1?

sounds very good. regards, aki 2011/6/7 Dennis Sosnoski : > 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 > kep

Re: Build failed in Jenkins: CXF-Trunk-JDK15 #2140

hi, sorry. i'll be fixing it. regards, aki 2011/6/8 Sergey Beryozkin : > Hi, > >> [INFO] - >> [ERROR] COMPILATION ERROR : >> [INFO] - >> [ERROR] >>

Re: Build failed in Jenkins: CXF-Trunk-JDK15 #2140

look right). Regards, aki 2011/6/8 Sergey Beryozkin : > Hi Aki > > On Wed, Jun 8, 2011 at 11:33 AM, Aki Yoshida wrote: >> hi, >> sorry. >> i'll be fixing it. > > np at all; by the way - I'm not sure I'm right there about dropping > explicit SOAPM

Oneway CXF service having problem with Gemini-Web/Tomcat-catalina

Hi, There seems to be some IO handling problem in oneway CXF services on equinox with the latest gemini-web. It think I have identified the cause of the problem and that we could fix it in CXF. But I would like to get your comments. The problem happens sporadically for oneway services when the Sta

server-side endpoint cleanup problem in spring based CXF scenarios in OSGi

Hi, There seems to be a problem in working with a spring based CXF server-side endpoint in OSGi that can lead to a serious stability issue. I would like to bring up this problem here for discussion so that we can find a solution to it. We can expect that an endpoint bundle (or a CXF scenario bundl

Re: server-side endpoint cleanup problem in spring based CXF scenarios in OSGi

2011/7/6 Willem Jiang : > On 7/6/11 8:39 PM, Aki Yoshida wrote: >> >> Hi, >> There seems to be a problem in working with a spring based CXF >> server-side endpoint in OSGi that can lead to a serious stability >> issue. I would like to bring up this problem here

Re: Build failed in Jenkins: CXF-Trunk-JDK15 #2226

hi, I replaced the usage of this jdk1.6 string method with the classical version to avoid this build error. regards, aki 2011/7/19 Apache Jenkins Server : > See > > Changes: > > [sergeyb] [CXF-3662] Better support for multiple response e

Re: Build failed in Jenkins: CXF-Trunk-JDK15 #2262

i'll be submitting the fix shortly. sorry. regards, aki 2011/7/28 Apache Jenkins Server : > See > > Changes: > > [coheigea] [CXF-3693] - SecurityTokenServiceProvider does not handle > exceptions properly > > [ay] [CXF-3692] enhacing inT

Re: Process id or similar in org.apache.cxf.message.Message?

Hi, if you want to distinguish your scenario based on, for example, the endpoint information, you can get the endpoint object from the message by Endpoint ep = message.getExchange().get(Endpoint.class) regards, aki 2011/8/2 chandrasekhares : > I'm using AbstractPhaseInterceptor to implement In/O

best practice for setting order constraints among interceptors

Hi, If you have two interceptors A and B that go into the same phase and additionally you want to make sure A must precede B, you can either write addBefore(B) in A's constructor or addAfter(A) in B's constructor. But is there a good rule for deciding which one to choose? The concrete case that I

Re: best practice for setting order constraints among interceptors

axOut and others > that "transform" the stream from InputStream type things to XMLStreamWriter > things would live.   (FIStax, TransformOut, etc....) > > Dan > > > On Tuesday, August 16, 2011 6:51:19 PM Aki Yoshida wrote: >> Hi, >> If you have two intercep

a quesiton on CXF 2.5 WS-RM's protocol variation handling

Hi Dennis, I am trying to adjust my JMX code for the CXF 2.5 WS-RM and I have a question. RMManager now manages endpoints under each supported protocol variation using Map>. Does this mean that an Endpoint can be used in several protocol variations? The background to my question is that I want to

Re: a quesiton on CXF 2.5 WS-RM's protocol variation handling

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 >> variation using Map>. >> Does this mean that an Endpoint can be used in several

Re: CXF-Trunk-JDK15 - Build # 2338 - Failure

Hi, I checked in yesterday an jmx instrumentation for ws-rm and this contained some jdk15 incompatibility code. I will be fixing it now. regards, aki 2011/8/24 Apache Jenkins Server : > The Apache Jenkins build system has built CXF-Trunk-JDK15 (build #2338) > > Status: Failure > > Check console o

JMX instrumentation for WS-RM checked in

Hi, I checked in an implementation of JMX instrumentation for the WS-RM components in trunk. In short, RMManager and RMEndpoint objects have their instrumentation beans and various inspection methods into the internal states of the runtime artifacts such as RM source and destination sequences, the

Re: JMX instrumentation for WS-RM checked in

Thanks. I will still be working on it for a while and finalize some details. I thought it would be nice to get some feedback. By the way, do you already have some specific time in your mind for 2.5.0? Regards, aki 2011/8/24 Daniel Kulp : > On Wednesday, August 24, 2011 1:30:30 PM Aki Yosh

Re: [jira] [Commented] (CXF-3768) HTTP response code 202 is not set for WS-Addressing partial responses

                Key: CXF-3768 >>                 URL: https://issues.apache.org/jira/browse/CXF-3768 >>             Project: CXF >>          Issue Type: Bug >>          Components: WS-* Components >>    Affects Versions: 2.4.2 >>            Reporter: Dmytro Rud &g

Re: [jira] [Commented] (CXF-3768) HTTP response code 202 is not set for WS-Addressing partial responses

esses). So I need another change in the AbstractHTTPDestination's response status logic to catch this case. regards, aki 2011/8/29 Aki Yoshida : > Hi Dan, > yes. The content and status should match. > > It's good that you brought up this decoupled client endpoint case. I >

Re: [jira] [Commented] (CXF-3768) HTTP response code 202 is not set for WS-Addressing partial responses

k behavior option because the problem will happen only when those very old clients are talking to the patched 2.4 and 2.5 servers. And those old clients will certainly have ineroperability issues with other servers as well. How do you think? Thanks. regards, aki 2011/8/29 Aki Yoshida : > Hi Dan,

Adjusting WS-RM systests for http 202

Hi, I would like to hear your opinion on the following issue which I encountered while fixing CXF-3768. The original problem reported in CX-3768 is not related to WS-RM. However, fixing this issue has some relevance to the CXF’s WS-RM behavior. Basically, this patch will make the CXF server endpoi

Re: Adjusting WS-RM systests for http 202

2011/9/1 Daniel Kulp : > On Wednesday, August 31, 2011 11:27:20 PM Aki Yoshida wrote: >> Hi, >> I would like to hear your opinion on the following issue which I >> encountered while fixing CXF-3768. The original problem reported in >> CX-3768 is not related to WS-RM. &g

Re: Adjusting WS-RM systests for http 202

2011/9/1 Dennis Sosnoski : > 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  sim

Re: Adjusting WS-RM systests for http 202

2011/9/2 Dennis Sosnoski : > 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

Re: Adjusting WS-RM systests for http 202

2011/9/2 Daniel Kulp : > On Friday, September 02, 2011 10:41:56 AM Aki Yoshida wrote: >> Thanks. I looked at some examples of Axis2 and the new behavior can >> interoperate with them. But I noticed one thing in the create sequence >> behavior for a decoupled endpoint case. >

Re: Adjusting WS-RM systests for http 202

Hi Dan, I submitted the patch for this CXF-3768 in trunk. As this issue was raised for 2.4.2., I was thinking of integrating this patch into 2.4.x. But after reading your question, I was not sure about how you thought. Would you prefer to keep the old behavior in 2.4? Technically, the behavior can

Re: Adjusting WS-RM systests for http 202

2011/9/6 Daniel Kulp : > On Tuesday, September 06, 2011 3:22:39 PM Aki Yoshida wrote: >> Hi Dan, >> I submitted the patch for this CXF-3768 in trunk. >> As this issue was raised for 2.4.2., I was thinking of integrating >> this patch into 2.4.x. >> >> But

Re: a quesiton on CXF 2.5 WS-RM's protocol variation handling

ndling 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/2011 11:32 PM, Aki Yo

Re: [DISCUSS] how to handle ws_security/interopfest example

2011/9/15 Freeman Fang : > Not sure we can download and ship the wsdl with CXF kit per license reason. > I was thinking about what to do with WS-RM tests and wanted to ask about the licencing condition for those interoperabiliy lab's WSDLs. Another thing I wanted to ask was whether we are allowed

Re: [DISCUSS] how to handle ws_security/interopfest example

2011/9/15 Daniel Kulp : > On Thursday, September 15, 2011 2:25:55 PM Aki Yoshida wrote: >> 2011/9/15 Freeman Fang : >> > Not sure we can download and ship the wsdl with CXF kit per license >> > reason. >> I was thinking about what to do with WS-RM tests and wan

Re: [VOTE] Release Apache CXF 2.5.0

+1 Aki 2011/10/29 Daniel Kulp : > > 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.org/content/repositories/org

problem of importing/including schemas using relative paths in a schema read by blueprint's namespace handler

Hi, Sorry for the long subject. I didn't know how to describe the problem better. I was wondering if you need to do something extra to be able to import or include a schema located at some relative path when you let the blueprint namespace handler fetch the parent schema. I wanted to make the ws-

Re: problem of importing/including schemas using relative paths in a schema read by blueprint's namespace handler

. But I cannot load locally available schemas using their relative URLs, as sometimes done in some of the spring versions of cxf schemas. regards, aki > > > Something on my todo list to fix once things calm down a bit for me with other > work related things. > > Dan > > >

Re: problem of importing/including schemas using relative paths in a schema read by blueprint's namespace handler

2011/11/5 Aki Yoshida : > 2011/11/5 Daniel Kulp : >> >> It's a bug in Aries: >> >> https://issues.apache.org/jira/browse/ARIES-626 > > Thanks for this info. I also noticed this issue. The solution will > probably require some kind of catalog files like spr

Re: [VOTE] Release Apache CXF 2.4.4-3rd try

+1 Aki 2011/11/4 Freeman Fang : > Hi All, > > We've resolved over 35 issues since 2.4.3 and thus is time for a release. > List of issues: > 2.4.4: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12318347 > > The Maven staging areas are at: > 2.4.4: > https://rep

Re: Async http requests and workqueue....

2011/10/11 Daniel Kulp : > On Sunday, October 09, 2011 9:27:09 AM Willem Jiang wrote: >> Hi Dan, >> >> I think the first option is OK, and it can let the user know what's >> wrong immediately. >> The other two option will be confused to the user if he just see the >> error and the call is succeed.

Re: WS-MakeConnection operation structuring

Hi Dennis, The response to the MakeConnection request may be arbitrary, but the client that wants to initiate a particular MakeConnection request might know what response to expect? I haven't thought about it and maybe I am missing the details. Regards, aki 2011/11/16 Dennis Sosnoski : > I'm ha

Re: WS-MakeConnection operation structuring

or sending > the saved message, implementing all the processing that should be done as > per the message's interceptor chain (including security processing). I've > been trying to figure out how to do that, but I'm pretty much lost. > > Dan, can you offer any suggestions

Jaxws's provider's null response behavior

Hi, as I briefly mentioned this in today's IRC, I created a ticket CXF-3926 to fix or improve the current behavior. jaxws 2.2 section 5.1.1 states: "When an invoke method returns null, it is considered that no response needs to be sent by service." CXF currently does not support this dynamic beha

Re: Jaxws's provider's null response behavior

I have to look into it deeper tomorrow. Do you have some idea? Thanks. regards, aki > > Dan > > > On Monday, November 21, 2011 6:09:03 PM Aki Yoshida wrote: >> Hi, >> as I briefly mentioned this in today's IRC, I created a ticket >> CXF-3926 to fix or improve

thought on spring and blueprint configuration schemas

hi, Is it allowed to merge the spring and blueprint versions of configuration schemas and use the resulting schema for both cases? If the answer is a definitive no, the rest of this mail can be ignored. If the answer is yes or maybe, I would like to explain why I am asking this question. For the

Re: thought on spring and blueprint configuration schemas

In this way we could reuse the module class as much as possible. > > [1]https://svn.apache.org/repos/asf/camel/trunk/components/camel-blueprint/pom.xml > > > On Tue Dec  6 21:00:26 2011, Aki Yoshida wrote: >> >> hi, >> Is it allowed to merge the spring and blue

Re: Different namespaces for CXF Blueprint and Spring schemas

Hi Sergey, I think there is a possibility to use one schema that works for both of them, thereby making things a lot simpler. You will lose some degree of strictness in the combined schemas (i.e., certain attributes are available but have no associated semantics and simply ignored when configured

Re: Different namespaces for CXF Blueprint and Spring schemas

hose specific base types. We lose the strictness in xml validation. But there is typically always a room between what syntactically valid and what semantically valid. So, I think it is an option to loosen the syntactic validation to gain some other benefits. I will start trying out this approach fo

Re: svn commit: r1212726 - in /cxf/trunk: api/src/main/java/org/apache/cxf/buslifecycle/BusCreationListener.java rt/core/src/main/java/org/apache/cxf/bus/CXFBusImpl.java rt/core/src/main/java/org/apac

Hi Dan, I have a suspicion that one of r1212724, r1212725, r1212726 from today has introduced some problem. A very simple osgi cxf spring bundle that worked before is suddenly getting the following exception at its start-up. osgi> Exception in thread "SpringOsgiExtenderThread-16" org.springframewo

Re: svn commit: r1212726 - in /cxf/trunk: api/src/main/java/org/apache/cxf/buslifecycle/BusCreationListener.java rt/core/src/main/java/org/apache/cxf/bus/CXFBusImpl.java rt/core/src/main/java/org/apac

2011/12/11 Daniel Kulp : > On Sunday, December 11, 2011 1:37:46 AM Aki Yoshida wrote: >> Hi Dan, >> I have a suspicion that one of r1212724, r1212725, r1212726 from today >> has introduced some problem. A very simple osgi cxf spring bundle that >> worked before is sud

Re: svn commit: r1213179 - in /cxf/trunk/rt/ws/rm/src/main: java/org/apache/cxf/ws/rm/blueprint/ resources/schemas/configuration/ resources/schemas/configuration/blueprint/

Hi Dan, okay. you are right. I just removed the bp reference but forgot the same problem can happen in the other end as well. i will remove the spring schema reference too. thanks. regards, aki 2011/12/12 Daniel Kulp : > On Monday, December 12, 2011 9:43:37 AM a...@apache.org wrote: >>          

Re: [VOTE] Apache CXF 2.5.1/2.4.5/2.3.8

+1 Aki 2011/12/15 Daniel Kulp : > > > We've resolved over 75 issues since 2.5.0 and thus is time for a release. > We've also ported back over 40 of the fixes to 2.4.5 and 30 of those to 2.3.8. > > List of issues: > 2.3.8: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511

bus extensions association under multiple buses

There is a problem in the bus extension association under multiple buses that may result in some concrete problem in some cases. I have a possible fix for this problem but there is also a related question to it. So, I would like to get your opinion about how we should proceed. Concretely, the prob

Re: bus extensions association under multiple buses

2011/12/19 Daniel Kulp : > > Inline > > On Monday, December 19, 2011 4:30:08 PM Aki Yoshida wrote: >> There is a problem in the bus extension association under multiple >> buses that may result in some concrete problem in some cases. I have a >> possible fix for

Re: bus extensions association under multiple buses

nager within the bus configuration. In this way, you don't need to refer to this instrumentation manager impl class in your configuration. regards, aki 2011/12/20 Aki Yoshida : > 2011/12/19 Daniel Kulp : >> >> Inline >> >> On Monday, December 19, 2011 4:30:08 PM

Re: [VOTE] Apache CXF 2.3.9/2.4.6/2.5.2

+1 Aki 2012/1/20 Daniel Kulp : > > > We've resolved over 45 issues since 2.5.1.  Most importantly, several of them > were regressions since 2.5.0 and thus we need to get a new release out.  We've > also ported back over 25 of the fixes to 2.4.6 and 8 of those to 2.3.9. > > List of issues: > 2.3.9

Re: [VOTE] Apache CXF 2.3.9/2.4.6/2.5.2

Hi Christian, you are right. I had some automatic tests that didn't report this problem (or was not pulling 2.5.2 correctly, maybe) :-( I saw the problem now after manually trying some scenarios. regards, aki 2012/1/20 Christian Schneider : > Alexey Markevich found a critical bug that prevents

Re: [VOTE] Apache CXF 2.3.9/2.4.6/2.5.2 - take 2

+1 Aki 2012/1/20 Daniel Kulp : > > We've resolved over 45 issues since 2.5.1.  Most importantly, several of them > were regressions since 2.5.0 and thus we need to get a new release out.  We've > also ported back over 25 of the fixes to 2.4.6 and 8 of those to 2.3.9. > > This is the second attemp

Re: svn commit: r1227691

2012/1/24 Sergey Beryozkin : > Hi Aki > > On 05/01/12 16:49, a...@apache.org wrote: >> >> Author: ay >> Date: Thu Jan  5 16:49:56 2012 >> New Revision: 1227691 >> >> URL: http://svn.apache.org/viewvc?rev=1227691&view=rev >> Log: >> [CXF-4013] Enhancing the element-append and drop options of >> OutT

Re: Transform Feature Improvements (Was: Re: svn commit: r1227691)

2012/1/25 Sergey Beryozkin : > Hi Aki > > I've changed the subject, hope you are ok with it > > On 25/01/12 10:04, Aki Yoshida wrote: >> >> 2012/1/24 Sergey Beryozkin: >>> >>> Hi Aki >>> >>> On 05/01/12 16:49, a...@apache.org

Re: Transform Feature Improvements (Was: Re: svn commit: r1227691)

2012/1/26 Sergey Beryozkin : > Hi, > > > On 26/01/12 09:52, Aki Yoshida wrote: >> >> 2012/1/25 Sergey Beryozkin: >>> >>> Hi Aki >>> >>> I've changed the subject, hope you are ok with it >>> >>> On 25/01/12 10:04,

Re: [VOTE] Apache DOSGi 1.3 Release

+1 Aki 2012/2/2 Sergey Beryozkin : > Apache CXF DOSGI subproject is a Reference Implementation of the OSGI Remote > Services Specification which offers an alternative approach toward > dynamically deploying and updating remote service endpoints and consumers > using the OSGI programming model. >

An option for performing oneway calls synchronously to be able to handle errors consistently

Hi, I would like to have an option to be able to invoke oneway calls synchronously so that the caller will get an HTTP 202 when no error occurs at the provider side but it will get an HTTP 500 SOAP fault when some error occurs. There seems to be no option available to enforce this behavior. Curren

Re: [jira] [Created] (CXF-4084) Blueprint http

Hi Dan, I can look into this item using a similar approach used in ws-rm using the merged schemas. Let me know if you see some issues. thanks. regards, aki 2012/2/3 Tony Su (Created) (JIRA) : > Blueprint http > -- > >                 Key: CXF-4084 >                 URL: https://issues

Re: An option for performing oneway calls synchronously to be able to handle errors consistently

2012/2/6 Daniel Kulp : > On Monday, February 06, 2012 11:39:24 AM Aki Yoshida wrote: >> Hi, >> I would like to have an option to be able to invoke oneway calls >> synchronously so that the caller will get an HTTP 202 when no error >> occurs at the provider side but i

Re: [jira] [Created] (CXF-4084) Blueprint http

Hi Johan, Dan mentioned that you might have started working on this item. Please let me know whether I can help here. Thanks. Regards, aki 2012/2/6 Daniel Kulp : > On Monday, February 06, 2012 1:16:20 PM Aki Yoshida wrote: >> Hi Dan, >> I can look into this item using a simila

Re: [jira] [Created] (CXF-4084) Blueprint http

nents. Dan once talked about using the apache http client. I wanted to look into the current status of this work. regards aki > /je > > On Feb 6, 2012, at 9:59 AM, Aki Yoshida wrote: > >> Hi Johan, >> >> Dan mentioned that you might have started working on this it

Re: [jira] [Created] (CXF-4084) Blueprint http

ou. Regards, aki > > The client side stuff would not necessarily have to interfere with that, the > osgi servlet, now that is > a potential different discussion, what is the right handling of SSL on that > side? > > > > On Feb 6, 2012, at 4:55 PM, Aki Yoshida wrote: &g

Re: An option for performing oneway calls synchronously to be able to handle errors consistently

forgot to cc on dev@cxf. doing it now so that i can link the whole thread in a jira ticket. 2012/2/6 Aki Yoshida : > 2012/2/6 Daniel Kulp : >> On Monday, February 06, 2012 5:50:05 PM Aki Yoshida wrote: >>> 2012/2/6 Daniel Kulp : >>> > On Monday, February 06, 2012

Re: [jira] [Created] (CXF-4084) Blueprint http

Hi Johan, Dan, I just added the HTTPConduit part in trunk. Not everything is in yet, though. regards, aki 2012/2/7 Aki Yoshida : > 2012/2/7 Johan Edstrom : >> Heh :) >> >> Not 100% sure we said the same thing here. >> I'm gone for about the next 4 days, I might

Re: svn commit: r1293413 - in /cxf/trunk/systests/rs-security: pom.xml src/test/java/org/apache/cxf/systest/jaxrs/security/oauth/TemporaryCredentialServiceTest.java

Hi Sergey, I was having a problem in building 2.5.x and trunk in a restricted fresh environment, then I noticed that systests/rs-security was still referring to cxf-rt-rs-security-oauth-test which no longer existed in 2.5.x and trunk. I saw the corresponding classes now exist in systests/rs-securi

Re: svn commit: r1295714

Hi Sergey, Dan, thanks for the background information. There were a few things I noticed too late. I added back the original uri handling for CXF-3958 so that all test cases are working. Although my second fix handles the existing jaxrs systests and Oli's new test case that I added for CXF-4150 ye

Transform feature to preserve prefix values (Re: svn commit: r1295714

setting is inactive. For the inbound, the prefixes are not preserved at all. Do you think we should add this prefix preserving mode as an explicit option or as the default behavior? regards, aki 2012/3/2 Aki Yoshida : > Hi Sergey, Dan, > thanks for the background information. There were

Re: svn commit: r1297370 - in /cxf/branches/2.5.x-fixes: ./ rt/ws/rm/src/main/java/org/apache/cxf/ws/rm/ systests/ws-specs/src/test/java/org/apache/cxf/systest/ws/rm/

2012/3/6 Dennis Sosnoski : > 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

Re: svn commit: r1300342 - /cxf/trunk/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/JettyHTTPDestination.java

Hi Dan, I thought it is strange that the setHeadFalse method is setting the head to true. Maybe there is a typo there? regards, aki 2012/3/13 : > Author: dkulp > Date: Tue Mar 13 20:34:14 2012 > New Revision: 1300342 > > URL: http://svn.apache.org/viewvc?rev=1300342&view=rev > Log: > [CXF-4175] m

Re: CORS: removing allowOrigins from the annotation only

Hi Sergey, I am not familiar with this stuff, so what I am saying may not make sense, though :-) But can you use the different default value so that you can distinguish between the null (i.e., interpreted as allowAllOrigins=true) and an empty allowOrigins (i.e., allowAllOrigins=false) ? regards,

Re: Can we require maven 3 to build CXF 2.6?

sounds good. I like the idea of requiring maven 3 to keep the number of supported build variations small. aki 2012/3/15 Daniel Kulp : > > I just discovered an issue with Maven 2.2.1 that is preventing the OSGi > manifest in the little bundles from being correct.   I'm not really sure > what the is

Re: svn commit: r1301636 - in /cxf/branches/2.5.x-fixes: ./ rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/JAXWSMethodInvoker.java systests/jaxws/src/test/java/org/apache/cxf/systest/provider/In

this was my first time to use DoMerge and somehow I make a mistake. After the merge operation, I didn't commit directly from DoMerge because I thought I should verify the merge result. After verifying the result, I used the old fashioned svn ci -F svnmerge-commit-messsage.txt I thought DoMerge u

server side protocol variation handling in WS-RM again

Hi Dennis, While ago, I mentioned the problem that I was having with the protocol variations in WS-RM. http://cxf.547215.n5.nabble.com/a-quesiton-on-CXF-2-5-WS-RM-s-protocol-variation-handling-td4710027.html I would like to come back to this problem, as I am having a few problems with server sid

Re: Issue CXF-4181

Hi, I attached a unit test for this problem to your jira ticket. I thought a quick solution is to copy all the namespace bindings from the reader object to the root dom element but the public API does not have an iterator to access all the bindings. So, that didn't work. Someone might have a simp

Re: [VOTE] Apache DOSGi 1.3.1 Release

+1 aki 2012/3/27 David Bosschaert : > The Apache CXF DOSGi subproject is the Reference Implementation of the > OSGi Remote Services and Remote Services Admin Service specifications > [1] which provide a distributed computing model based around OSGi > Services. > > We have been working on CXF-DOS

Re: server side protocol variation handling in WS-RM again

as wondering if this is still okay because of the shortly planned 2.6.0 release. Any thought? Thanks. Regards, aki 2012/3/22 Aki Yoshida : > Hi Dennis, > > While ago, I mentioned the problem that I was having with the protocol > variations in WS-RM. > > http://cxf.547215.n5.nabbl

  1   2   3   >