I'm not sure how the cxf-rt-frontend-jaxrs dependency should be handled.
The work I've done so far [1] will tie the DSW software to the JAX-RS
implementation. Since cxf-rt-frontend-jaxrs isn't an osgi bundle, I'd have
to embed the jar within DSW to satisfy the dependency. This doesn't seem
like a
test failures are because the test 'fails to fail' in the default
profile which lacks the necessary wstx version. I will deal when I get
home from 5th grade concert.
On Wed June 10 2009 12:57:52 pm Naresh Tallapelli wrote:
> Thanks Daniel.I am not using any of the external parsers for web services.
> Could you please let me know any configuration in cxf change the parser
> from woodstox to sun. And iam using cxf for last one year. I did not face
> this problem
Excellent work.It would probably be a good idea to start getting some of
this integrated into CXF itself. Now that a fixes branch for 2.2 has been
created and trunk is targeting 2.3, we definitely should start committing some
patches for this.
Dan
On Wed June 10 2009 4:04:22 am liucon
Thanks Daniel.I am not using any of the external parsers for web services.
Could you please let me know any configuration in cxf change the parser
from woodstox to sun. And iam using cxf for last one year. I did not face
this problem earlier. I am seeing this error from last one week. Could you
pl
Ah, a task at which I am uniquely qualified.
On Wed, Jun 10, 2009 at 11:21 AM, Daniel Kulp wrote:
> On Wed June 10 2009 11:12:58 am Benson Margulies wrote:
>> Is it OK if I check into trunk with changes that depend on new wstx+ msv?
>
> Yep. All's a go. Go ahead and destabilize trunk. :-)
>
On Wed June 10 2009 10:25:32 am Sergey Beryozkin wrote:
> Hi
>
> I need to generate schema instances from java types, these types may or may
> not be JAXB annotated. What options are available in CXF ?
>
> thanks, Sergey
JAXB can handle beans without annotations. You just need the annotations if
On Wed June 10 2009 11:12:58 am Benson Margulies wrote:
> Is it OK if I check into trunk with changes that depend on new wstx+ msv?
Yep. All's a go. Go ahead and destabilize trunk.:-)
--
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog
Is it OK if I check into trunk with changes that depend on new wstx+ msv?
Jaxb or Aegis. I don't think xmlbeans, but I may be out of date.
On Wed, Jun 10, 2009 at 10:25 AM, Sergey Beryozkin wrote:
> Hi
>
> I need to generate schema instances from java types, these types may or may
> not be JAXB annotated.
> What options are available in CXF ?
>
> thanks, Sergey
Hi
I need to generate schema instances from java types, these types may or may not
be JAXB annotated.
What options are available in CXF ?
thanks, Sergey
On Wed June 10 2009 4:38:37 am liucong wrote:
> So, the JMS transport just copy JMS message properties to somewhere(For
> example, Message.PROTOCOL_HEADERS map). Then the SOAP binding add some
> extra interceptors (How to add these interceptors?) to deal with these
> properties (check the propertie
> I've just updated a cxf-minimal bundle to include a jaxrs frontend and I
> updated the cxf.version in dosgi/parent to 2.3.0-SNAPHOT
>
> (David, Eoghan - we can downgrade it easily to 2.2.2 fixes tag if DOSGi will
> need to be released sooner than 2.3 does which is in about 3 months or so I
> beli
Hi Josh
What do you think about this idea. The factory which returns handlers
can check first if a given service intents include "HTTP" but no "SOAP"
and a frontend.jaxrs property is set, and if yes then it returns
JaxRSPojoConfigurationTypeHandler which will do what
PojoConfigurationTypeHandle
So, the JMS transport just copy JMS message properties to somewhere(For
example, Message.PROTOCOL_HEADERS map). Then the SOAP binding add some
extra interceptors (How to add these interceptors?) to deal with these
properties (check the properties, throw some SOAP Faults, and so on).
Does it wo
Hi all,
Project Description:
SOAP over JMS specification (http://www.w3.org/TR/soapjms/) is aimed at
a set of standards for the transport of SOAP messages over JMS (Java
Message Service). The main purpose is to ensure interoperability between
the implementations of different Web services vendors.
16 matches
Mail list logo