Here's what I have ...
<bean id="ewsng.PurgeController.service"
class="org.codehaus.xfire.spring.ServiceBean">
<property name="serviceBean" ref="ewsng.purgeController" />
<property name="serviceFactory" ref="jaxbServiceFactory" />
<property name="faultHandlers">
<list>
<ref bean="ewsng.faultHandler"/>
</list>
</property>
</bean>
<!-- Initialize JAXB2 service factory -->
<bean name="jaxbServiceFactory"
class="org.codehaus.xfire.jaxb2.JaxbServiceFactory">
<constructor-arg ref="xfire.transportManager" />
</bean>
The only difference I see is that I only have one constructor-arg for
the JaxbServiceFactory ... I don't specify the aegis binding provider.
Now, truth be told, I haven't actually grabbed 1.2.3 or 1.2.4 and tested
it, after reading messages on the mail-list. Its a non-trivial effort to
re-do the project libs from xfire-1.0 to xfire-1.2.x ... we used
xfire-all previously, but the organization has now adopted a more
granular approach, i.e. - more tedious for me :|
-Brice
-----Original Message-----
From: Dan Diephouse [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 23, 2007 3:01 PM
To: [email protected]
Subject: Re: [xfire-user] Any Workarounds for XFIRE-739: wsdl: doesn't
describe pojos in xsd ?
Hi,
Your configuration is not right. Try this:
<bean
class="org.springframework.web
.servlet.handler.SimpleUrlHandlerMapping">
<property name="urlMap">
<map>
<entry key="/EchoService">
<ref bean="echo" />
</entry>
</map>
</property>
</bean>
<bean id="xfire.myjaxbServiceFactory"
class="org.codehaus.xfire.service
.binding.JaxbServiceFactory"
singleton="true">
<constructor-arg index="0">
<ref bean="xfire.transportManager" />
</constructor-arg>
<constructor-arg index="1">
<ref bean="xfire.aegisBindingProvider" />
</constructor-arg>
</bean>
<!-- Declare a parent bean with all properties common to both
services -->
<bean id="echo" class="org.codehaus.xfire.spring
.remoting.XFireExporter">
<property name="serviceFactory">
<ref bean="xfire.myjaxbServiceFactory" />
</property>
<property name="xfire">
<ref bean="xfire" />
</property>
<property name="serviceBean">
<ref bean="echoBean" />
</property>
<property name="serviceClass">
<value>org.codehaus.xfire.spring.example.Echo</value>
</property>
<property name="namespace">
<value>http://www.abc.com/myproject </value>
</property>
</bean>
Notice:
1. I'm using JaxbServiceFactory
2. you don't need to specify a wsdlbuilderfactory
Cheers,
- Dan
On 1/22/07, SWAMIG <[EMAIL PROTECTED]> wrote:
Hi Dan,
I am facing the same problem too.
The interface definition is
public interface Echo {
// Array of strings
String[] echo7();
}
The configuration file is
<?xml version=" 1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
"http://www.springframework.org/dtd/spring-beans.dtd ">
<beans>
<!-- START SNIPPET: xfire -->
<bean
class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
<property name="urlMap">
<map>
<entry key="/EchoService">
<ref bean="echo" />
</entry>
</map>
</property>
</bean>
<bean id="xfire.wsdlBuilderFactory"
class="org.codehaus.xfire.jaxb2.JaxbWSDLBuilderFactory " />
<bean name="xfire.jaxbServiceFactory"
class="org.codehaus.xfire.jaxb2.JaxbServiceFactory">
<constructor-arg ref="xfire.transportManager" />
</bean>
<bean id="xfire.jaxb2MappingRegistry"
class="org.codehaus.xfire.jaxb2.JaxbTypeRegistry"
init-method="createDefaultMappings" singleton="true">
</bean>
<bean id="xfire.aegisBindingProvider"
class="org.codehaus.xfire.aegis.AegisBindingProvider"
singleton="true">
<constructor-arg index="0">
<ref bean="xfire.jaxb2MappingRegistry"
/>
</constructor-arg>
</bean>
<!-- bean id="xfire.commonsAnnotations"
class="org.codehaus.xfire.annotations.jsr181.Jsr181WebAnnotations" -->
<bean id="xfire.myjaxbServiceFactory"
class="org.codehaus.xfire.service.binding.ObjectServiceFactory "
singleton="true">
<constructor-arg index="0">
<ref bean="xfire.transportManager" />
</constructor-arg>
<constructor-arg index="1">
<ref bean="xfire.aegisBindingProvider"
/>
</constructor-arg>
<property name="wsdlBuilderFactory" ref="
xfire.wsdlBuilderFactory" />
</bean>
<!-- Declare a parent bean with all properties common to
both services -->
<bean id="echo"
class="org.codehaus.xfire.spring.remoting.XFireExporter ">
<property name="serviceFactory">
<ref bean="xfire.myjaxbServiceFactory"
/>
</property>
<property name="xfire">
<ref bean="xfire" />
</property>
<property name="serviceBean">
<ref bean="echoBean" />
</property>
<property name="serviceClass">
<value>org.codehaus.xfire.spring.example.Echo</value>
</property>
<property name="namespace">
<value>http://www.abc.com/myproject</value>
</property>
</bean>
<!-- END SNIPPET: xfire -->
</beans>
Dan Diephouse wrote:
>
> Can you paste your configuration? I'm having a hard time
reproducing this
> and wondering if it might be a configuration. If you can't
post it to the
> list feel free to send the relevant files to me privately.
Thanks,
>
> - Dan
>
> On 1/22/07, Henri Gomez < [EMAIL PROTECTED]> wrote:
>>
>> Did the snapshot is available ?
>>
>> This problem is very serious for us...
>>
>>
>> >2007/1/20, Henri Gomez <[EMAIL PROTECTED]>:
>> > The fix will be available in 1.2.5 so ?
>> >
>> > Did there is a snapshot available ?
>> >
>> > Regards.
>> >
>> > 2007/1/19, Brice Ruth <[EMAIL PROTECTED]>:
>> > > Thanks for your persistence and perseverance on this, Dan
- it is
>> much
>> > > appreciated.
>> > >
>> > > Brice
>> > >
>> > >
>> > > On 1/19/07, Dan Diephouse < [EMAIL PROTECTED]>
wrote:
>> > > > *sigh* - I did think I fixed that issue, but I'll take
a peek over
>> the
>> > > weekend and publish a SNAPSHOT out with a fix. I'm way
behind on
>> XFire
>> this
>> > > week, but will try to catch up this weekend... Thanks for
your
>> patience,
>> > > >
>> > > > - Dan
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On 1/11/07, Ruth, Brice D < [EMAIL PROTECTED]> wrote:
>> > > > >
>> > > > >
>> > > > > That's not good ... we're still on xfire-1.0 because
of this ...
>> > > > >
>> > > > >
>> > > > > -----Original Message-----
>> > > > > From: Sebastien Cesbron [mailto:[EMAIL PROTECTED]
>> > > > > Sent: Thursday, January 11, 2007 2:36 AM
>> > > > > To: [email protected]
>> > > > >
>> > > > > Subject: Re: [xfire-user] Any Workarounds for
XFIRE-739: wsdl:
>> doesn't
>> > > describe pojos in xsd ?
>> > > > >
>> > > > >
>> > > > > Sorry but it seems this is not fix in the last
release (1.2.4) so
>> we
>> > > cannot use JAXB2.0 annotations with xfire 1.2.4
>> > > > >
>> > > > > Seb
>> > > > >
>> > > > >
>> > > > > On 12/18/06, Christopher Moesel <
[EMAIL PROTECTED]>
>> wrote:
>> > > > > > Thanks Tom-- it's very much appreciated!
>> > > > > >
>> > > > > > -Chris
>> > > > > >
>> > > > > > -----Original Message-----
>> > > > > > From: Tomek Sztelak [mailto: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ]
>> > > > > > Sent: Monday, December 18, 2006 12:34 PM
>> > > > > > To: [email protected]
>> > > > > > Subject: Re: [xfire-user] Any Workarounds for
XFIRE-739: wsdl:
>> doesn't
>> > > > > > describe pojos in xsd ?
>> > > > > >
>> > > > > > Hi
>> > > > > > Hard to tell any particular date. I didn't look at
this bug
>> yet,
>> Dan
>> > > > > > is out of country, but we will try to fix this
before next
>> release,
>> > > > > > which should be some time soon.
>> > > > > >
>> > > > > > On 12/18/06, Ruth, Brice D <[EMAIL PROTECTED]> wrote:
>> > > > > > >
>> > > > > > >
>> > > > > > > Ugh, looks like you might be right. Dan, Tom -
any ETA on
>> this?
>> > > > > > >
>> > > > > > >
>> > > > > > > -----Original Message-----
>> > > > > > > From: Christopher Moesel
[mailto:[EMAIL PROTECTED]
>> ]
>> > > > > > > Sent: Monday, December 18, 2006 10:44 AM
>> > > > > > > To: [email protected]
>> > > > > > > Subject: RE: [xfire-user] Any Workarounds for
XFIRE-739:
>> wsdl:
>> > > doesn't
>> > > > > > > describe pojos in xsd ?
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > The release notes for 1.2.3 list:
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > - JAXB WSDL generation fix
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Looking through the resolved bugs for that
release, I think
>> that the
>> > > > > > release
>> > > > > > > notes may have been referring to XFIRE-568: "JAXB
2.0 with
>> > > Annotations
>> > > > > > > generates invalid schema imports".
Unfortunately, that is a
>> > > > > > completely
>> > > > > > > different problem than XFIRE-739, which is still
marked
>> unresolved
>> > > in
>> > > > > > the
>> > > > > > > bug tracker.
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > -Chris
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > -----Original Message-----
>> > > > > > > From: Ruth, Brice D [mailto: [EMAIL PROTECTED]
>> > > > > > > Sent: Monday, December 18, 2006 11:02 AM
>> > > > > > > To: [email protected]
>> > > > > > > Subject: RE: [xfire-user] Any Workarounds for
XFIRE-739:
>> wsdl:
>> > > doesn't
>> > > > > > > describe pojos in xsd ?
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > That's disturbing news. Dan or Tom - can you shed
any light
>> on
>> this?
>> > > I
>> > > > > > > remember from the 1.2.3 release notes that this
was supposed
>> to have
>> > > > > > been
>> > > > > > > fixed.
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > -Brice
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > -----Original Message-----
>> > > > > > > From: Christopher Moesel
[mailto:[EMAIL PROTECTED] ]
>> > > > > > > Sent: Monday, December 18, 2006 8:53 AM
>> > > > > > > To: [email protected]
>> > > > > > > Subject: RE: [xfire-user] Any Workarounds for
XFIRE-739:
>> wsdl:
>> > > doesn't
>> > > > > > > describe pojos in xsd ?
>> > > > > > >
>> > > > > > > I am using the 1.2.3 release (details below). I
suspect it
>> didn't
>> > > > > > make it
>> > > > > > > into the release since the bug has not been
closed out in the
>> > > tracker
>> > > > > > (and
>> > > > > > > since I'm still having problems!).
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > I am using:
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Xfire-all-1.2.3
>> > > > > > >
>> > > > > > > Xfire-jsr181-api-1.0-M1
>> > > > > > >
>> > > > > > > Jaxb-api-2.0
>> > > > > > >
>> > > > > > > Jaxb-impl-2.0.1
>> > > > > > >
>> > > > > > > Jaxb-xjc-2.0.1
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Thanks,
>> > > > > > >
>> > > > > > > Chris
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > -----Original Message-----
>> > > > > > > From: Ruth, Brice D [mailto: [EMAIL PROTECTED]
>> > > > > > > Sent: Monday, December 18, 2006 9:37 AM
>> > > > > > > To: [email protected]
>> > > > > > > Subject: RE: [xfire-user] Any Workarounds for
XFIRE-739:
>> wsdl:
>> > > doesn't
>> > > > > > > describe pojos in xsd ?
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Are you using 1.2.3? This was supposed to have
been fixed in
>> the
>> > > > > > latest
>> > > > > > > release. I, too, have this problem, but hadn't
yet been able
>> to test
>> > > > > > the
>> > > > > > > latest release.
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > -Brice
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > -----Original Message-----
>> > > > > > > From: Christopher Moesel [mailto:
[EMAIL PROTECTED]
>> > > > > > > Sent: Monday, December 18, 2006 7:41 AM
>> > > > > > > To: [email protected]
>> > > > > > > Subject: [xfire-user] Any Workarounds for
XFIRE-739: wsdl:
>> doesn't
>> > > > > > describe
>> > > > > > > pojos in xsd ?
>> > > > > > >
>> > > > > > > I've recently attempted to change from Aegis to
JAXB 2.0 for
>> my XML
>> > > > > > binding.
>> > > > > > > I am using a JSR181 code-first deployment. It
appears,
>> however,
>> > > that
>> > > > > > the
>> > > > > > > generated WSDL does not contain schema
definitions for any of
>> my
>> > > POJOs
>> > > > > > (nor
>> > > > > > > ArrayOfString). It looks like this is a known bug
and has
>> been
>> > > > > > discussed on
>> > > > > > > the list previously.
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > http://jira.codehaus.org/browse/XFIRE-739
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Are there any known workarounds, or do I need to
go back to
>> Aegis?
>> > > Is
>> > > > > > there
>> > > > > > > an expected release that the bugfix will be a
part of?
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Thanks, as always, for a great product! We
certainly
>> appreciate all
>> > > > > > of the
>> > > > > > > hard work you put into this!
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > -Chris
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > -----
>> > > > > > When one of our products stops working, we'll blame
another
>> vendor
>> > > > > > within 24 hours.
>> > > > > >
>> > > > > >
>> > >
---------------------------------------------------------------------
>> > > > > > To unsubscribe from this list please visit:
>> > > > > >
>> > > > > > http://xircles.codehaus.org/manage_email
>> > > > > >
>> > > > > >
>> > > > > >
>> > >
---------------------------------------------------------------------
>> > > > > > To unsubscribe from this list please visit:
>> > > > > >
>> > > > > > http://xircles.codehaus.org/manage_email
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Dan Diephouse
>> > > > Envoi Solutions
>> > > > http://envoisolutions.com | http://netzooid.com/blog
>> > >
>> > >
>> > >
>> > > --
>> > > Brice Ruth
>> > > Software Engineer, Madison WI
>> >
>>
>>
---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>
>
> --
> Dan Diephouse
> Envoi Solutions
> http://envoisolutions.com | http://netzooid.com/blog
>
>
--
View this message in context:
http://www.nabble.com/Any-Workarounds-for-XFIRE-739%3A-wsdl%3A-doesn%27t
-describe-pojos-in-xsd---tf2839974.html#a8513979
Sent from the XFire - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog
