Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of ning.jiang@iona.com designates
 12.170.54.180 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C83C03.852F06E5"
Subject: RE: configurability of published soap:address location on jaxws
 endpoints
Date: Tue, 11 Dec 2007 09:35:41 -0500
Message-ID: <9A4696F35B459043970EE4A85A31739002557A@amer-ems1.IONAGLOBAL.COM>
Thread-Topic: configurability of published soap:address location on jaxws
 endpoints
Thread-Index: Acg74gEQsOEIdqfHRhebaDl56np5SwAF+xF8AAJLWZQ=
References: 
 <90622e530712030204r4b5c0998i866d7fd5c856c11b@mail.gmail.com><4754F50B.4020505@iona.com><90622e530712032339o41d6f3ecxa0c0941cc6fe986c@mail.gmail.com><475523BB.5030300@iona.com><90622e530712040258s4bb847eftb6f45130ae5c63fc@mail.gmail.com><4755EA7F.2050205@iona.com>
 <47560DC2.4080500@iona.com><90622e530712100718wb079e4fu29a4405602cd83df@mail.gmail.com>
 <90622e530712110238s68a32eb4i8ef6f539edadf963@mail.gmail.com>
 <9A4696F35B459043970EE4A85A317390025579@amer-ems1.IONAGLOBAL.COM>
From: "Jiang, Ning \(Willem\)" <Ning.Jiang@iona.com>
To: <cxf-dev@incubator.apache.org>

------_=_NextPart_001_01C83C03.852F06E5
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi Christian,

I just checked the code , the real reason is jaxws front end module's =
pom.xml=20
does not include the http transport module.
I will move the SpringBeansTest.testPublishedEndpointUrl test code to=20
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
=20

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
=20
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.
>


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


------_=_NextPart_001_01C83C03.852F06E5--