Re: Concurrent Modification Exception on multiple runs using n-1 threads

there a danger of losing consistency? Will all threads that require the context property for "working" have them or we will see some of those under some timing conditions failing? regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/Concurrent-Modification

Concurrent Modification Exception for cxf-2.4.9

reposting...but seems related to .. http://mail-archives.apache.org/mod_mbox/cxf-commits/201002.mbox/%3c20100225012238.4853a2388...@eris.apache.org%3E it seems related to that checkin. however, dan, please confirm. creating cxf proxy and on multiple runs (~1) with executorservice threads seed

Re: Concurrent Modification Exception on multiple runs using n-1 threads

CXF version 2.4.9 surefire plugin version 2.16 (forkCount = 1, reuseFork = true ) running on jenkins on linux system can send you more details if required. -- View this message in context: http://cxf.547215.n5.nabble.com/Concurrent-Modification-Exception-on-multiple-runs-using-n-1-threads-

Concurrent Modification Exception on multiple runs using n-1 threads

org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:134) could you please look into this? regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/Concurrent-Modification-Exception-on-multiple-runs-using-n-1-threads-tp5738246.html Sent from the cxf-user mailing list archive at Nabble.com.

spring WebApplicationContext and CXF SpringBus

is is leading. is there a way to not let this happen? regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/spring-WebApplicationContext-and-CXF-SpringBus-tp5728816.html Sent from the cxf-user mailing list archive at Nabble.com.

JAX-RS QueryParam/FormParam is empty

the URL as bytes=@B[ . is this by design ( even when i have media-type defined as text/plain ) ? the cxf-version i am using is 2.4.0 ( but i have tried it with cxf-2.4.2,.., cxf-2.5.2 ) any pointers to this would be nice. regards, cogitate -- View this message in context: http://c

cxf-2.4.2 performance issue

; cxf-2.4.0 and commons-pool-1.5.5 used by cxf-2.4.0 and not used by cxf-2.4.2 ). anyone have a clue what went on? anyone else had similar issues? any pointers are greatly appreciated, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/cxf-2-4-2-performance-issue-tp569549

Re: InTransformReader Test possible enhancement?

to our case and might help others too. thanks and regards, -cogitate Hi Sergey, you are right. This use case is rather strange and actually not xml-compliant. It can be considered a non-xml legacy (ie., xml-looking but not xml) application connecting case. I heard of a similar use case for the outboun

Re: InTransformReader Test possible enhancement?

Just to clarify. The test case above fails today. The possible enhancement to InTransformReader is what i was suggesting thanks, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/InTransformReader-Test-possible-enhancement-tp5554151p458.html Sent from the cxf

InTransformReader Test possible enhancement?

generate may not even be specific.. from vendor - Y what we need - something like : http://schemas.w3c.org/W3C";>Y thanks in advance, -cogitate @Test public void testSpecificNS() throws Exception { String input = ""; InputStream i

Message Observer on Local destination

Aware( of course, the inner class extends ClientProxyFactoryBean ..) and still get the same exception. any ideas of would be helpful here. thanks and regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/Message-Observer-on-Local-destination-tp5534750p5534750.html S

Re: re:CXF with Sprint Integration

xception. any ideas of would be helpful here. thanks and regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/re-CXF-with-Sprint-Integration-tp5501007p5532889.html Sent from the cxf-user mailing list archive at Nabble.com.

re:CXF with Sprint Integration

nse objects - somewhat miraculously :) thanks and regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/re-CXF-with-Sprint-Integration-tp5501007p5501007.html Sent from the cxf-user mailing list archive at Nabble.com.

Re: CXF embedded within a SpringIntegration Context

ement some servlet lifecycle methods (doGet, doPost..?) -Cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/CXF-embedded-within-a-SpringIntegration-Context-tp5158465p5455592.html Sent from the cxf-user mailing list archive at Nabble.com.

CXF embedded within a SpringIntegration Context

host both of these endpoints within SI, so that i can run them w/o changing any of my code. there'd be no tomcat container( except maybe to bootstrap SI ). what's the best way i can do this? thanks and regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com

running cxf jaxws and jaxrs without cxfservlet

under AMQP broker. thanks and regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/running-cxf-jaxws-and-jaxrs-without-cxfservlet-tp4937089p4937089.html Sent from the cxf-user mailing list archive at Nabble.com.

Re: cxf-2.4.0 pattern match StaxTransformFeature?

Sergei : my apologies - and thank you for the correction !! i completely agree with you , for the input what we have currently suffices ( even adding of prefixes within cxf chain interceptors poses no threats as jaxb impls in cxf do what's required! ) You abzolutellly Rock!!! if you ever do make

Re: cxf-2.4.0 pattern match StaxTransformFeature?

paces. why can't we have this? regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/cxf-2-4-0-pattern-match-StaxTransformFeature-tp4381005p4814256.html Sent from the cxf-user mailing list archive at Nabble.com.

Re: cxf-2.4.0 pattern match StaxTransformFeature?

thanks sergei. in the case of enterprise where a payload has just one namespace, a prefix seems redundant. and yes , the response payload is huge..:( how does one add a defaultNamespace property for incoming messages? regards -- View this message in context: http://cxf.547215.n5.nabble.com

Re: cxf-2.4.0 pattern match StaxTransformFeature?

ok - just to close the loop . what was happening is specific to cxf-2.4.0 and it's a bug that's been fixed in cxf-2.4.1-SNAPSHOT as given below. http://cxf.547215.n5.nabble.com/quot-Stream-is-closed-quot-Exception-when-upgrade-from-CXF-2-3-3-to-CXF-2-4-0-td4385277.html cxf stream is closed early

StaxTransformFeature issues

. is there something i am missing? thanks and regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com/StaxTransformFeature-issues-tp4423934p4423934.html Sent from the cxf-user mailing list archive at Nabble.com.

Re: cxf-2.4.0 pattern match StaxTransformFeature?

Sergei: when i use the StaxTransformFeature for stripping out - the loggingoutbound interceptor displays the stripped out xml , but the outputstream has no data. is there something i am missing? thanks and regards, -cogitate -- View this message in context: http://cxf.547215.n5.nabble.com

Re: Spring Integration with Apache CXF

thank you willem. i am evaluating apache camel too. any idea how spring-integration differs from camel? it seems camel is also based on spring. while camel seems to be pure "connector" from one protocol to another with some processing capability , spring-integration seems to do a bit more? rega

Spring Integration with Apache CXF

i started looking at Spring Integration so that I can have AMQP support. however, currently i am fully invested in apache-cxf and working on providing jms support ( with cxf-2.4.0 ) on a framework code. so question : if i am using Spring Integration do i still need apache-cxf? if the answer is ye

Re: cxf-2.4.0 pattern match StaxTransformFeature?

Hi Sergey thanks for showing me what to do with the incoming message - on a side note is it not possible to have no prefixed based xml for incoming too , with just defaultNamespace ? i know cxf's parsers will handle the xml example you had...but if the xml is huge the readability is great withou

Re: cxf-2.4.0 pattern match StaxTransformFeature?

>Is there any reason you are not using inTransformElements property ? actually , i didn't get around to doing this since i was testing the outgoing functionality but , yes this is something i need to do. i configure an incoming XML Namespace Interceptor that will add a namespace to the root eleme

Re: cxf-2.4.0 pattern match StaxTransformFeature?

thanks sergey for the explanation - i use the StaxTransformFeature assymetrically as i illustrate below. in my scenario, the server is obviously pretending to be a soap service ( i.e it has wsdls ) but the payload doesn't comply to the xsds w.r.t namespaces. in fact , this is a third party vendor.

cxf-2.4.0 pattern match StaxTransformFeature?

hi sergey: thanks for valuable changes - in 2.2.4 i had custom stream writer to remove these namespaces by hijacking the output stream. with the StaxTransformFeature and at the USER_LOGICAL space adding message.put( "soap.env.ns.map" , nsMap); i am able to completely control what goes out and int

Re: Removing namespaces

hi sergei: thanks for these changes - in 2.2.4 i had custom stream writer to remove these namespaces by hijacking the output stream. with the StaxTransformFeature and at the USER_LOGICAL space adding message.put( "soap.env.ns.map" , nsMap); i am able to completely control what goes out and into t

Re: CXF with HATEOS or hypermedia

Sergey Beryozkin-5 wrote: > > Hi > > On Fri, Apr 29, 2011 at 12:07 AM, cogitate <monish.u...@gmail.com> > wrote: >> hi sergei : >>  i am thinking more in terms of >> 1. RESTfulie => >>    https://github.com/caelum/restfulie >>    ht

Re: CXF with HATEOS or hypermedia

hi sergei : i am thinking more in terms of 1. RESTfulie => https://github.com/caelum/restfulie http://restfulie.caelum.com.br/ yes which basically supports "links" with every entity or model. 2. Jersey => the support here is a bit more sophisticated , supports "Links" using header

CXF with HATEOS or hypermedia

We are fully invested in CXF for supporting payloads of various types - not just Webservices but also RESTful services. However , for RESTful services we want to have "hypermedia" support. Currently it seems CXF isn't supporting this and we are under pressure to go to "Jersey" - however, i wouldn

Re: removing namespaces and prefixes for Doc/Literal/Bare or pure xml service

commit some code like this so everyone having "namespace" "prefix" "Urinamespace" issues have a solution once and for all. regards. cogitate wrote: > > i am writing a pure-xml service and followed all the instructions for > writing an xml service > http:

removing namespaces and prefixes for Doc/Literal/Bare or pure xml service

i am writing a pure-xml service and followed all the instructions for writing an xml service http://cxf.apache.org/docs/pure-xml.html i have looked at this : http://old.nabble.com/Removing-XML-namespaces-and-prefixes-td24457677.html#a24457677 i have the service interface setup as Doc/Literal/Bar