Hi there,
cxf includes the jaxp-ri as a dependency when needed in a couple of
places (only when running with the ibm jdk), but I notice that in
the parent/pom.xml, jaxp-api is specifically excluded:
com.sun.xml.parsers
jaxp-ri
1.4.2
> My collegue followed the instructions there and was rewarded with a
> nonfunctioning environment. I confess that I've had bad experience
> with the output of WTP in the past, so I'm not inclined to push him to
> try harder. Call me irresponsible ...
Push him to report the issues :)
--oh
My collegue followed the instructions there and was rewarded with a
nonfunctioning environment. I confess that I've had bad experience
with the output of WTP in the past, so I'm not inclined to push him to
try harder. Call me irresponsible ...
On Wed, Jul 15, 2009 at 10:51 AM, Oisin Hurley wrote:
> In my experience, trying to use 'incubator' materials out of Eclipse
> is a recipe for incipient self-defenestration.
'Incubation' at Eclipse means that the project
hasn't reached a 1.0 yet in terms of APIs
and has not been through an official release
review.
Just like at Apache, the term incub
> No. We DID have an eclipse plugin, but it didn't do anything gui related. It
> literaly was just CXF and all the third party deps packaged into an eclipse
> plugin bundle thing so that could be put in the eclipse/plugins dir so that
> the STP tools could depend on it.
Yeah, I admit my weak mem
That explains that.
In my experience, trying to use 'incubator' materials out of Eclipse
is a recipe for incipient self-defenestration. So if that's the best
there is, we're stuck. I do wonder about whether the JBoss gang has
something useful.
On Wed, Jul 15, 2009 at 10:10 AM, Daniel Kulp wrote
On Tue July 14 2009 12:26:43 pm Oisin Hurley wrote:
> > I strongly remember that there was an entire eclipse plugin in our
> > tree back when I first showed up. I could be confabulating.
>
> I think you might be confabulating about that :)
No. We DID have an eclipse plugin, but it didn't do anyth
On Tue July 14 2009 6:24:39 pm Benson Margulies wrote:
> So, I modified the aegis sample to demonstrate a service with a
> Document as a return type. The client receives the
> org.w3c.dom.Document for the 'return' wrapper element, not the actual
> element corresponding to the server's return value,
