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 <[EMAIL PROTECTED]> 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.
