Since there is not an official build of Muse, you should
always do a "maven clean dist" when updating Muse.
You should also regenerate off of your wsdls to get the new
methods.
The methods you describe are implemented when you generate
to a new directory with all the updated jars...Again the best way to achieve
this is to do a "maven clean dist" in the Muse project.
We are aggressively adding new functionality to the codegen
to simplify things...That being said, bleeding edge folks, like yourselves, may
feel some pain during this process....
-Sal
From: Joseph Kueser [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 10, 2005 9:55 AM
To: [email protected]
Subject: RE: Muse build error
Just
as a FYI, I'm passing this along from my team:
1) Latest build does
not eliminate VM_global_library.vm errors and warnings.
2) Latest 5-9 build breaks another class with new abstract classes not extended anywhere. Within the Apollo .jar file, org.apache.ws.resource.impl.AbstractResourceHome defines several new abstract classes. I believe the XXXXXXXXSoapPortHome.java class now gets compile errors because the new abstract methods aren’t defined. I check the drop from 5-6 and these are new abstract methods were just added on 5-9. So I have dropped back to the 5-6 drop for now.
-----Original Message-----
From: Joseph Kueser
Sent: Monday, May 09, 2005 3:00 PM
To: [email protected]
Subject: Muse build errorSome of the guys here are getting the following error when building.Concrete class within auto-generated XXXXXXXXSoapPortService.java does not extend the abstract method getManageabilityReferences(org.oasisOpen.docs.wsdm.x2004.x12.mows.wsdmMows.GetManageabilityReferencesDocument) defined in auto-generated AbstractXXXXXXXXSoapPortService.java.
We don’t know what this method is suppose to do so we have implemented a dummy method that returns null, just to get past the compile stage.
Any ideas?
Thanks!
Joe
