cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jiang, Ning \(Willem\)" <Ning.Ji...@iona.com>
Subject RE: configurability of published soap:address location on jaxws endpoints
Date Tue, 11 Dec 2007 14:35:41 GMT

Hi Christian,

I just checked the code , the real reason is jaxws front end module's pom.xml 
does not include the http transport module.
I will move the SpringBeansTest.testPublishedEndpointUrl test code to 
the systest module.

Willem.

-----Original Message-----
From: Jiang, Ning (Willem) [mailto:Ning.Jiang@iona.com]
Sent: Tue 12/11/2007 21:29
To: cxf-dev@incubator.apache.org; cxf-dev@incubator.apache.org
Subject: RE: configurability of published soap:address location on jaxws endpoints
 

Hi Christian,

I will take care it :)
It likes like you do not set the right bus for the JaxWsServerFactoryBean.

Willem.

-----Original Message-----
From: Christian Vest Hansen [mailto:karmazilla@gmail.com]
Sent: Tue 12/11/2007 18:38
To: cxf-dev@incubator.apache.org
Subject: Re: configurability of published soap:address location on jaxws endpoints
 
I've slept on it and ...

> Even though the test seems to (sometimes) work with the
> JaxWsServerFactoryBean, I've been unable to prove to myself that a
> spring-configured jaxws:endpoint works aswell due to #2, so I presume
> that part dosn't work.

... is no longer an issue. Turns out the little test project I created
was borked and included two versions of CXF - no wonder it didn't
work. Plus, the patch seems to work as expected in this test project
now that it's dependencies and deployment is fixed.

So this is a good thing, however mvn test still fails with a "Could
not find destination factory for transport
http://schemas.xmlsoap.org/soap/http" message, while eclipse lets the
test pass. I wonder what the difference is.


PS.
> I've created a JIRA
... but forgot the link. Here it is:
https://issues.apache.org/jira/browse/CXF-1279


On 12/10/07, Christian Vest Hansen <karmazilla@gmail.com> wrote:
> I've created a JIRA for this feature and attached a preliminary patch
> to it that I'de like someone to look at and comment on (I'm sure there
> are numerous things to point out).
>
> The patch has a number of issues that I'm currently stuck on:
>  #1. The SpringBeansTest.testPublishedEndpointUrl runs fine in Eclipse
> but breaks in mvn test (this also breaks the build).
>  #2. The changes to jaxws.xsd dosn't seem to have any effect outside
> the confines of JUnit (this breaks war-file deployment).
>  #3.  I've had to add the publishedEndpointUrl property to not only
> EndpointImpl, but also AbstractEndpointFactory, and I wonder if it
> needs to be added elsewhere.
>
> Even though the test seems to (sometimes) work with the
> JaxWsServerFactoryBean, I've been unable to prove to myself that a
> spring-configured jaxws:endpoint works aswell due to #2, so I presume
> that part dosn't work.
>
> On 12/5/07, Willem Jiang <ning.jiang@iona.com> wrote:
> > Jim Ma wrote:
> > >
> > >> Is there a specific reason for using jaxws:properties as oppose to a
> > >> first class attribute? Because I already implemented the attribute...
> > >> :p
> > >>
> > > That's cool .  There is no specific reason for that , I just  think
> > > it's the simple way to
> > > do that .. :)
> > >
> > I think in this case , you do not need to change the jaxws.xsd[1] and the
> > EndpointDefinitionParser[2] to consume a new attribute.
> >
> >
> > [1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/jaxws/src/main/resources/schemas/jaxws.xsd
> > [2]https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/spring/EndpointDefinitionParser.java
> >
> >
> > Willem.
> >
>
>
> --
> Venlig hilsen / Kind regards,
> Christian Vest Hansen.
>


-- 
Venlig hilsen / Kind regards,
Christian Vest Hansen.



Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message