I can confirm there is definitely a bug in the JAXB WSDL generation...
Could you maybe try this build?
http://snapshots.repository.codehaus.org/org/codehaus/xfire/xfire-all/1.2-SNAPSHOT/xfire-all-1.2-20061016.171227-27.jar
We're working on getting 1.2.3 out soon! :-)
- Dan
Ruth, Brice D wrote:
Dan -
We're using JSR-181 annotations, so here's the annotation on the
service class:
@WebService(
serviceName = "EwsTaskService",
endpointInterface =
"com.example.workflow.ewsng.controller.ITaskController")
Here's our Spring app context, we're using vanilla spring instead of
XBean -
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
"http://www.springframework.org/dtd/spring-beans.dtd";>
<!-- START SNIPPET: services -->
<beans>
<!-- Import XFire beans -->
<import resource="classpath:org/codehaus/xfire/spring/xfire.xml"/>
<bean id="ewsng.TaskController.service"
class="org.codehaus.xfire.spring.ServiceBean">
<property name="serviceBean" ref="ewsng.taskController" />
<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>
</beans>
-----Original Message-----
*From:* Brice Ruth [mailto:[EMAIL PROTECTED]
*Sent:* Saturday, October 14, 2006 10:31 PM
*To:* [email protected]
*Subject:* Re: [xfire-user] wsdl: doesn't describe pojos in xsd
Not at all - I'll paste the relevant config parts on Monday.
Brice
On 10/14/06, *Dan Diephouse* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
There might be a bug with our JAXBWSDLBuilder that someone pointed
out
to me the other day. Its on my list to fix monday. Although it
might be
a configuration issue - you mind pasting your config?
- Dan
Ruth, Brice D wrote:
> XFire team -
>
> Rolling back to xfire-1.0 JARs appears to fix the problem,
though I am
> still no closer to understanding why the newer versions are "broken"
> for me. We are using JAXB2 bindings on the service side - is JAXB2
> responsible for generating the schema parts in the wsdl, or is
wsdl4j?
>
> Respects,
> Brice Ruth
>
> -----Original Message-----
> *From:* Ruth, Brice D
> *Sent:* Wednesday, October 11, 2006 3:46 PM
> *To:* [email protected] <mailto:[email protected]>
> *Subject:* [xfire-user] wsdl: doesn't describe pojos in xsd
>
> Good afternoon -
>
> I am seeing a problem in xfire-1.2.2 and xfire-1.1.2, coming from
> xfire-1.0 with respect to generating the wsdl correctly. Somehow,
> XFire is generating the wsdl without explicitly defining the objects
> used by the web service operations. For example, an operation
> "startTasks" has an UpdateTaskInput and a ManageTaskResult (in0 and
> out, respectively). However, those objects are not enumerated
anywhere
> else in the wsdl. Obviously, this causes problems when generating
> client stubs.
>
> I have compiled xfire-1.2.2 from src and replaced all dependent
JARs
> with the ones downloaded by the build process. I have also
grabbed the
> nightly for JAXB2 (10/11) for jaxb-api, jaxb-impl, and jaxb-xjc.
>
> Here's what I would get (excerpts) from xfire-1.0:
>
>
> <xsd:element name="retrieveTasks">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element
name="in0" type="ns2:RetrieveTasksInput" nillable="true"
minOccurs="1" maxOccurs="1" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
>
>...
>
> <xsd:complexType name="RetrieveTasksInput">
> <xsd:sequence>
> <xsd:element
name="criteria" type="ns1:TaskSearchDto" minOccurs="0"
nillable="true" />
> </xsd:sequence>
> </xsd:complexType>
>...
>
> <xsd:complexType name="TaskSearchDto">
> <xsd:sequence>
> <xsd:element
name="actorIds" type="tns:ArrayOfString" minOccurs="0"
nillable="true" />
> <xsd:element name="dates"
type="ns1:ArrayOfDateRange" minOccurs="0" nillable="true" />
> <xsd:element
name="descriptions" type="tns:ArrayOfString" minOccurs="0"
nillable="true" />
> <xsd:element name="ids"
type="tns:ArrayOfLong" minOccurs="0" nillable="true" />
> <xsd:element name="names"
type="tns:ArrayOfString" minOccurs="0" nillable="true" />
> <xsd:element
name="pageNumber" type="xsd:int" minOccurs="0" />
> <xsd:element
name="pageSize" type="xsd:int" minOccurs="0" />
> <xsd:element name="sorts"
type="ns1:ArrayOfSortImpl" minOccurs="0" nillable="true" />
> <xsd:element
name="statuses" type="ns1:ArrayOfETaskStatus" minOccurs="0"
nillable="true" />
> <xsd:element name="types"
type="tns:ArrayOfString" minOccurs="0" nillable="true" />
> <xsd:element
name="variables" type="ns1:ArrayOfVariableImpl" minOccurs="0"
nillable="true" />
> </xsd:sequence>
> </xsd:complexType>
>... (etc., defining each of the objects referenced as elements)
>
>
>
> In the wsdl I get with xfire-1.1.2 and xfire-1.2.2, all I see is
this:
> (No further definitions of the custom type is available.)
>
>
>
><xsd:element name="retrieveTasks">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element maxOccurs="1" minOccurs="1" name="in0"
nillable="true" type="ns1:RetrieveTasksInput"/>
> </xsd:sequence>
> </xsd:complexType>
></xsd:element>
>
> What's going on here? I've looked through the JIRA issues fixed for
> each release since 1.0 and I've searched the archives and I
can't come
> up with anything that might be causing this.
>
> Cheers,
> Brice Ruth
--
Dan Diephouse
(616) 971-2053
Envoi Solutions LLC
http://netzooid.com <http://netzooid.com>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
<http://xircles.codehaus.org/manage_email>
--
Brice Ruth
Software Engineer, Madison WI
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
