XFireFault exception: "No write method for property"

Have the same problem. Dan could you comment it.

Not sure if this has been taken care of in 1.2.2, but I believe I just ran into the same issue. I concur with Christian Nuesa's observation that the problem is somehow related to ArrayList.

In my situation, the error occured when processing GeometrySection$SegmentIDs which has an ArrayList.

I am jaxb2 binding. See detailed log below:

org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireF
ault: No write method for property

segmentIDsElement in class com.gcmtravel.webser
vice.data.GeometrySection$SegmentIDs
org.codehaus.xfire.fault.XFireFault: No write method for property

segmentIDsElemen
t in class com.gcmtravel.webservice.data.GeometrySection$SegmentIDs
at org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(Soap11FaultSerializer.java:31)

OK - CYW said this seems to be a problem when you have an ArrayList as opposed to a List. Will check into this.

Hello all,
Is there a workaround for this bug without having to change the initial schema?
Currently I manually insert a set-Method into the concerned classes to get it work.
Is there a way to let xfire do this per command ot something else?

Thanks for help in advance!

Is there an ETA on a fix or work-around?
Thanks,
Chris

Christian, CYW, others: I'm looking into this issue and it looks like you're trying to use the Aegis binding to serializer jaxb beans.

For instance on this line in the original description:

Service serviceModel = new ObjectServiceFactory().create(SOAPport.class) ;

that should be:

Service serviceModel = new JaxbServiceFactory().create(SOAPport.class) ;

Same goes for others who commented and mentioned they were using JAXB. If you aren't using JAXB, make sure you have both a getter and a setter. If you think you're still having issues, please email the mailing list with your complete configuration. Thanks

Reopening at the request of users...

A sample wsdl, a sample ant file that will build a stub from the wsdl, and the source code generated.

I've left out the contents of the "lib" dir, it just contained the jars from the 1.2.2 distro

Scheduling for 1.2.4

OK, I still can't reproduce this issue - even with the attached wsdl. Here is my client code:

XfireContractFirstClient service = new XfireContractFirstClient();

XfireContractFirst client = service.getXfireContractFirstSOAP("http://localhost:8081/XfireContractFirst");

InputMessageUnbounded unbounded = new InputMessageUnbounded();
unbounded.getItem().add("foo");
assertEquals("foo", client.doSomethingBroken(unbounded));

And my server code:

JaxbServiceFactory asf = new JaxbServiceFactory();
service = asf.create(CustomXfireContractFirstImpl.class, null,
new File("src/wsdl/xfire-509.wsdl").toURL(), null);

getServiceRegistry().register(service);

XFireHttpServer server = new XFireHttpServer();
server.start();

Everything invokes fine.

Looking at your webservices.xml though I think I see the issue. IIRC (and I'm not sure that I do), the Jsr181HandlerMapping isn't going to work out of the box with JAXB. It just loops through your beans, sees if it has a @WebService annotation, then exposes it using the AnnotationServiceFactory.

Instead of doing:

<property name="typeMappingRegistry">
<ref bean="xfire.typeMappingRegistry" />
</property>

You might want to try:

<property name="typeMappingRegistry">
<bean class="org.codehaus.xfire.jaxb2.JaxbTypeRegistry"/>
</property>

Let me know if that helps.

Not so much luck I'm afraid. Now the wsdl generated at run time doesn't include the full schema, here's the complete schema generated:

<wsdl:types>
<xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://www.industria.com/services/troubleticketing/mailer">
<xsd:element name="MailAnyStringRequest" type="tns:MailAnyStringRequest" />
<xsd:element name="MailAnyStringResponse" type="tns:MailAnyStringResponse" />
<xsd:element name="MailAnyStringFault" type="tns:MailAnyStringFault" />
</xsd:schema>
</wsdl:types>

Without the types, no clients can connect to it. On the bright side, it hasn't made up any of it's own namespaces.

Are you using XFire 1.2.3? There was a bug in 1.2.2 which did this.

I was using 1.2.2, I've just dropped in the 1.2.3-all jar, deleting the old 1.2.2 jar, and rebuilt, but it's the same thing. Should there be any other steps in upgrading?

I've also tried regenerating the server stub with the 1.2.3-all jar instead of the 1.2.2 jar, but that doesn't make any difference. (And a diff in both folders doesn't show any real differences in the generated source (Just a couple of differences in the order of methods in the files)

Is there any workaround for this at all if I want to sent a list of objects?

Ashley - can you paste your configuration? I still haven't seen any situations where this isn't a configuration problem of some sort.

We junked our configs and started from scratch again, and got it working, but only by going back to the plain single services.xml.

Some more examples of the config setup would be nice

We fixed this by adding the JaxbServiceFactory into services.xml like so: -

<beans>
<service xmlns="http://xfire.codehaus.org/config/1.0">
<name>Test</name>
<namespace>http://localhost:8080/bam/services/TestDemo</namespace>
<serviceClass>com.blah.MyServiceClass</serviceClass>
<serviceFactory>org.codehaus.xfire.jaxb2.JaxbServiceFactory </serviceFactory>
</service>
</beans>

I hope this helps somebody!

For me, this was happening on Aegis binding when I had a read-only property (no setter method).
I added a no-op setter method and it works now...

Hi All,

I am facing the same kind of problem (org.codehaus.xfire.fault.XFireFault: No write method for property ).

I am using the XFire 1.2.1 and was using the ObjectServiceFactory. After going through comments above, i changed it to JaxbServiceFactory. Then it started asking for the annotations(since my service class does not have any annotations). I added web services annotations to my service class. But unfortunately, this also did not solve my issue. The service class which i am using is a interface; and when i am trying to access the service with the above implemenation; it gives the following error:

org.codehaus.xfire.annotations.AnnotationException: Service class cannot be abstract: com.pinkroccade.jfoundation.calculation.releases.ReleaseManager
at org.codehaus.xfire.annotations.AnnotationServiceFactory.assertValidImplementationClass(AnnotationServiceFactory.java:278)
at org.codehaus.xfire.annotations.AnnotationServiceFactory.create(AnnotationServiceFactory.java:172)

If i make my implementation class as service class it might work(i tried that also; but there is some other problem). But as of now i dont want to do it that way. Is there any ways by which i can fix this problem ????

By using xfire-1.2.3, will it solve the issue ?????

And whats this "no-op setter method". May i hav esome more information on this.