Hi Kiren
If it's a jar then you'd need to add cxf-core and cxf-rt-transports-http
and to the java classpath...
Cheers, Sergey
On 11/08/14 17:19, Kiren Pillay wrote:
Hi Sergey,
I am getting a NPE when I use the WebClient as a self-standing
application. We're using Maven and the
You would need to ask about this on the JBoss lists. They have their own
class loaders and integration things and such that can dictate some of the
behavior around this.
Dan
On Aug 11, 2014, at 3:18 PM, Aida ai.d...@gmail.com wrote:
Hi all,
I have been googling and reading threads
Hi,
I'm new in CXF and i've created a Web service (with Jax-WS) that i've
deployed in 2 different ways : in Tomcat and then in Karaf (making an OSGI).
Once my service working... which tool whould you advise me to administrate
my web service ?
I would like to have a kind of console (like T.A.C)
(... or maybe ServiceMix)
--
View this message in context:
http://cxf.547215.n5.nabble.com/General-question-about-CXF-and-monitoring-tp5747682p5747683.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi,
Some time before I have started a thread with jackson and form
parameters in cxf
http://mail-archives.apache.org/mod_mbox/cxf-users/201406.mbox/%3c53aac4cc.8010...@biovista.com%3E
Sergey suggested that I should use ParamConverterProvider.
I tried it today and it worked. Great.
Now I am
Hi
AFAIK ParamConverterProvider is expected to be called once per every
entity in the list.
Thanks, Sergey
On 12/08/14 16:12, Vassilis Virvilis wrote:
Hi,
Some time before I have started a thread with jackson and form
parameters in cxf
Aah,
So in order to make this work through CXF is to define an
EntitiesListWrapper class. Right? Then the ParamConverter will be called
with EntitiesListWrapper as argument and jackson will deserialize. Right?
Is there any other way to break the input of
final String
Sorry, do not understand what you are trying to do.
Why do you use a single parameter (query, header, or may be form) to
send a JSON array ? This is typically sent as a message body, in which
case JAX-RS MessageBodyReader takes care of it.
Imagine this case:
?a=1-2-3a=4-5-6
here we have 2
On 12/08/14 17:13, Sergey Beryozkin wrote:
Sorry, do not understand what you are trying to do.
Why do you use a single parameter (query, header, or may be form) to
send a JSON array ? This is typically sent as a message body, in which
case JAX-RS MessageBodyReader takes care of it.
Imagine
Hi Sergey,
First of all thanks for your prompt reply as always. Your help is
appreciated.
Secondly, I am sorry I didn't explain the situation more clearly. I am a
bit frustrated with this... as always when things don't work as we
expect them too. It is quite probable that I lack the
Hi,
On 12/08/14 19:44, v.virvi...@biovista.com wrote:
Hi Sergey,
First of all thanks for your prompt reply as always. Your help is
appreciated.
Secondly, I am sorry I didn't explain the situation more clearly. I am a
bit frustrated with this... as always when things don't work as we
expect
Hi,
On 12/08/14 19:44, v.virvi...@biovista.com wrote:
Hi Sergey,
First of all thanks for your prompt reply as always. Your help is
appreciated.
Secondly, I am sorry I didn't explain the situation more clearly. I am a
bit frustrated with this... as always when things don't work as we
expect
Hi Sergey,
I have managed to get the local transport working. It is working as
specified in the tests:)
I think the missing MessageObserver error is caused by a missing
target resource bean in my jaxrs:server config.
Regards
Kiren
On Mon, Aug 11, 2014 at 12:18 PM, Kiren Pillay
Hi Kiren
Sounds good, thanks for making it work
Cheers, Sergey
On 12/08/14 20:39, Kiren Pillay wrote:
Hi Sergey,
I have managed to get the local transport working. It is working as
specified in the tests:)
I think the missing MessageObserver error is caused by a missing
target resource
Thanks for your help Sergey!
Cheers.
On Tue, Aug 12, 2014 at 9:49 PM, Sergey Beryozkin sberyoz...@gmail.com wrote:
Hi Kiren
Sounds good, thanks for making it work
Cheers, Sergey
On 12/08/14 20:39, Kiren Pillay wrote:
Hi Sergey,
I have managed to get the local transport working. It is
I know on 3.0.x, this change was needed to support the new StAX based
WS-Security processing. We needed to know up front which type of crypto’s and
such we need to setup for the stax code to use. Not sure why this was needed
on 2.7.x. Colm is on vacation this week so I’ll have to wait
JBoss AS 5 has its own web services implementation (JBossWS Native)
installed by default. Unless you explicitly installed JBossWS-CXF in
your installation, then JBossWS Native is going to be used, which of
course won't recognize CXF annotations.
If you want, you could package CXF in your
Hi All,
Currently am using java first approach for xfire to cxf migration.
The WSDL generated by cxf is having the following:
xsd:import namespace=some_name_space_1/
xsd:import namespace=some_name_space_2/
Any chance I may put all these imports in the
18 matches
Mail list logo
