You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "david mcilroy (JIRA)" <xm...@xml.apache.org> on 2005/04/05 16:09:19 UTC
[jira] Created: (XMLBEANS-142) XmlBeans - Web service - BindingException
XmlBeans - Web service - BindingException
-----------------------------------------
Key: XMLBEANS-142
URL: http://issues.apache.org/jira/browse/XMLBEANS-142
Project: XMLBeans
Type: Bug
Components: XmlObject
Versions: Version 2 Beta 1
Environment: Win Xp SP2 - deploying to Weblogic Server 8.1
Reporter: david mcilroy
Priority: Blocker
Hi,
I am working with XmlBeans in Jbuilder and have created a project that contains a couple of EJBs that use XmlBeans to compile and manipulate a couple of XSD Schema files. The application works fine when deployed to Weblogic as an EJB, however when I configure the project as a Web Service and rebuild I get the following error:
[servicegen] weblogic.xml.schema.binding.BindingException: Invalid class received: interface com.bt.sas.SasSendDocument loaded from file:/D:/CLASSPATH/XmlBeanProject/xmlTypesSasSend.jar!/com/bt/sas/SasSendDocument.class. All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor
As I hinted above I am instantiating the interface "SasSendDocument.class" in my JBuilder project and can deploy and run the application but when I try and create a web service from the project it starts complaining about the fact that I am using an interface. XmlBeans "scomp" also generated a SasSendDocumentImpl.class that I have tried to use to overcome this problem (althoughin WLWorkshop I have always used the XmlBeanDocument object), but I then get the following error:
[servicegen] weblogic.xml.schema.binding.BindingException: No default constructor was found for class com.bt.sas.xml.impl.SasResultDocumentImpl loaded from file:/D:/Classpath/SasReturnSrc.jar!/com/bt/sas/xml/impl/SasResultDocumentImpl.class.All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor - with nested
Here it seems to be complaining that the class has no default constructor. However, these classes are auto-generated by XmlBeans for me and I don't believe I should have to tinker with the source and recompile. Anyway, even if I do change the class I cannot update the .xsb files which were produced by the XmlBeans compiler.
Any ideas greatfully received :)
Regards
Davy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Resolved: (XMLBEANS-142) XmlBeans - Web service - BindingException
Posted by "Radu Preotiuc-Pietro (JIRA)" <xm...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XMLBEANS-142?page=all ]
Radu Preotiuc-Pietro resolved XMLBEANS-142:
-------------------------------------------
Resolution: Fixed
Assuming that the problem reported went away. I have opened XMLBEANS-174 to track the issue of default constructors in particular.
> XmlBeans - Web service - BindingException
> -----------------------------------------
>
> Key: XMLBEANS-142
> URL: http://issues.apache.org/jira/browse/XMLBEANS-142
> Project: XMLBeans
> Type: New Feature
> Components: XmlObject
> Versions: Version 2 Beta 1
> Environment: Win Xp SP2 - deploying to Weblogic Server 8.1
> Reporter: david mcilroy
> Assignee: Radu Preotiuc-Pietro
> Priority: Blocker
> Fix For: TBD
>
> Hi,
> I am working with XmlBeans in Jbuilder and have created a project that contains a couple of EJBs that use XmlBeans to compile and manipulate a couple of XSD Schema files. The application works fine when deployed to Weblogic as an EJB, however when I configure the project as a Web Service and rebuild I get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: Invalid class received: interface com.bt.sas.SasSendDocument loaded from file:/D:/CLASSPATH/XmlBeanProject/xmlTypesSasSend.jar!/com/bt/sas/SasSendDocument.class. All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor
> As I hinted above I am instantiating the interface "SasSendDocument.class" in my JBuilder project and can deploy and run the application but when I try and create a web service from the project it starts complaining about the fact that I am using an interface. XmlBeans "scomp" also generated a SasSendDocumentImpl.class that I have tried to use to overcome this problem (althoughin WLWorkshop I have always used the XmlBeanDocument object), but I then get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: No default constructor was found for class com.bt.sas.xml.impl.SasResultDocumentImpl loaded from file:/D:/Classpath/SasReturnSrc.jar!/com/bt/sas/xml/impl/SasResultDocumentImpl.class.All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor - with nested
> Here it seems to be complaining that the class has no default constructor. However, these classes are auto-generated by XmlBeans for me and I don't believe I should have to tinker with the source and recompile. Anyway, even if I do change the class I cannot update the .xsb files which were produced by the XmlBeans compiler.
> Any ideas greatfully received :)
> Regards
> Davy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Assigned: (XMLBEANS-142) XmlBeans - Web service - BindingException
Posted by "Lawrence Jones (JIRA)" <xm...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XMLBEANS-142?page=all ]
Lawrence Jones reassigned XMLBEANS-142:
---------------------------------------
Assign To: Radu Preotiuc-Pietro
> XmlBeans - Web service - BindingException
> -----------------------------------------
>
> Key: XMLBEANS-142
> URL: http://issues.apache.org/jira/browse/XMLBEANS-142
> Project: XMLBeans
> Type: New Feature
> Components: XmlObject
> Versions: Version 2 Beta 1
> Environment: Win Xp SP2 - deploying to Weblogic Server 8.1
> Reporter: david mcilroy
> Assignee: Radu Preotiuc-Pietro
> Priority: Blocker
> Fix For: TBD
>
> Hi,
> I am working with XmlBeans in Jbuilder and have created a project that contains a couple of EJBs that use XmlBeans to compile and manipulate a couple of XSD Schema files. The application works fine when deployed to Weblogic as an EJB, however when I configure the project as a Web Service and rebuild I get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: Invalid class received: interface com.bt.sas.SasSendDocument loaded from file:/D:/CLASSPATH/XmlBeanProject/xmlTypesSasSend.jar!/com/bt/sas/SasSendDocument.class. All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor
> As I hinted above I am instantiating the interface "SasSendDocument.class" in my JBuilder project and can deploy and run the application but when I try and create a web service from the project it starts complaining about the fact that I am using an interface. XmlBeans "scomp" also generated a SasSendDocumentImpl.class that I have tried to use to overcome this problem (althoughin WLWorkshop I have always used the XmlBeanDocument object), but I then get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: No default constructor was found for class com.bt.sas.xml.impl.SasResultDocumentImpl loaded from file:/D:/Classpath/SasReturnSrc.jar!/com/bt/sas/xml/impl/SasResultDocumentImpl.class.All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor - with nested
> Here it seems to be complaining that the class has no default constructor. However, these classes are auto-generated by XmlBeans for me and I don't believe I should have to tinker with the source and recompile. Anyway, even if I do change the class I cannot update the .xsb files which were produced by the XmlBeans compiler.
> Any ideas greatfully received :)
> Regards
> Davy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-142) XmlBeans - Web service - BindingException
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XMLBEANS-142?page=history ]
Jacob Danner updated XMLBEANS-142:
----------------------------------
Fix Version: TBD
Maybe something we should consider in later releases?
> XmlBeans - Web service - BindingException
> -----------------------------------------
>
> Key: XMLBEANS-142
> URL: http://issues.apache.org/jira/browse/XMLBEANS-142
> Project: XMLBeans
> Type: New Feature
> Components: XmlObject
> Versions: Version 2 Beta 1
> Environment: Win Xp SP2 - deploying to Weblogic Server 8.1
> Reporter: david mcilroy
> Priority: Blocker
> Fix For: TBD
>
> Hi,
> I am working with XmlBeans in Jbuilder and have created a project that contains a couple of EJBs that use XmlBeans to compile and manipulate a couple of XSD Schema files. The application works fine when deployed to Weblogic as an EJB, however when I configure the project as a Web Service and rebuild I get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: Invalid class received: interface com.bt.sas.SasSendDocument loaded from file:/D:/CLASSPATH/XmlBeanProject/xmlTypesSasSend.jar!/com/bt/sas/SasSendDocument.class. All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor
> As I hinted above I am instantiating the interface "SasSendDocument.class" in my JBuilder project and can deploy and run the application but when I try and create a web service from the project it starts complaining about the fact that I am using an interface. XmlBeans "scomp" also generated a SasSendDocumentImpl.class that I have tried to use to overcome this problem (althoughin WLWorkshop I have always used the XmlBeanDocument object), but I then get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: No default constructor was found for class com.bt.sas.xml.impl.SasResultDocumentImpl loaded from file:/D:/Classpath/SasReturnSrc.jar!/com/bt/sas/xml/impl/SasResultDocumentImpl.class.All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor - with nested
> Here it seems to be complaining that the class has no default constructor. However, these classes are auto-generated by XmlBeans for me and I don't believe I should have to tinker with the source and recompile. Anyway, even if I do change the class I cannot update the .xsb files which were produced by the XmlBeans compiler.
> Any ideas greatfully received :)
> Regards
> Davy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-142) XmlBeans - Web service - BindingException
Posted by "Radu Preotiuc-Pietro (JIRA)" <xm...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XMLBEANS-142?page=comments#action_62600 ]
Radu Preotiuc-Pietro commented on XMLBEANS-142:
-----------------------------------------------
David,
this probably is some unfortunate interaction between JBuilder and XmlBeans. The way we designed our Java binding, it binds Schema types to interfaces backed by implementation classes without an empty constructor. As you can imagine, it would be a pretty big deal to change this 180degrees to classes with empty constructor. Not to say that it's never going to happen, but you should not look for it in the near future. So this can't be filed as a "bug".
On the other hand, a lot of people are successfully using XmlBeans with WebLogic 8.1. I know this for a fact and there are threads on user@xmlbeans.apache.org discussing this; so you should refer to these threads and to the WebLogic documentation, because it can be done.
> XmlBeans - Web service - BindingException
> -----------------------------------------
>
> Key: XMLBEANS-142
> URL: http://issues.apache.org/jira/browse/XMLBEANS-142
> Project: XMLBeans
> Type: Bug
> Components: XmlObject
> Versions: Version 2 Beta 1
> Environment: Win Xp SP2 - deploying to Weblogic Server 8.1
> Reporter: david mcilroy
> Priority: Blocker
>
> Hi,
> I am working with XmlBeans in Jbuilder and have created a project that contains a couple of EJBs that use XmlBeans to compile and manipulate a couple of XSD Schema files. The application works fine when deployed to Weblogic as an EJB, however when I configure the project as a Web Service and rebuild I get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: Invalid class received: interface com.bt.sas.SasSendDocument loaded from file:/D:/CLASSPATH/XmlBeanProject/xmlTypesSasSend.jar!/com/bt/sas/SasSendDocument.class. All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor
> As I hinted above I am instantiating the interface "SasSendDocument.class" in my JBuilder project and can deploy and run the application but when I try and create a web service from the project it starts complaining about the fact that I am using an interface. XmlBeans "scomp" also generated a SasSendDocumentImpl.class that I have tried to use to overcome this problem (althoughin WLWorkshop I have always used the XmlBeanDocument object), but I then get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: No default constructor was found for class com.bt.sas.xml.impl.SasResultDocumentImpl loaded from file:/D:/Classpath/SasReturnSrc.jar!/com/bt/sas/xml/impl/SasResultDocumentImpl.class.All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor - with nested
> Here it seems to be complaining that the class has no default constructor. However, these classes are auto-generated by XmlBeans for me and I don't believe I should have to tinker with the source and recompile. Anyway, even if I do change the class I cannot update the .xsb files which were produced by the XmlBeans compiler.
> Any ideas greatfully received :)
> Regards
> Davy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-142) XmlBeans - Web service - BindingException
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XMLBEANS-142?page=history ]
Jacob Danner updated XMLBEANS-142:
----------------------------------
type: New Feature (was: Bug)
Making this a feature request
> XmlBeans - Web service - BindingException
> -----------------------------------------
>
> Key: XMLBEANS-142
> URL: http://issues.apache.org/jira/browse/XMLBEANS-142
> Project: XMLBeans
> Type: New Feature
> Components: XmlObject
> Versions: Version 2 Beta 1
> Environment: Win Xp SP2 - deploying to Weblogic Server 8.1
> Reporter: david mcilroy
> Priority: Blocker
> Fix For: TBD
>
> Hi,
> I am working with XmlBeans in Jbuilder and have created a project that contains a couple of EJBs that use XmlBeans to compile and manipulate a couple of XSD Schema files. The application works fine when deployed to Weblogic as an EJB, however when I configure the project as a Web Service and rebuild I get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: Invalid class received: interface com.bt.sas.SasSendDocument loaded from file:/D:/CLASSPATH/XmlBeanProject/xmlTypesSasSend.jar!/com/bt/sas/SasSendDocument.class. All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor
> As I hinted above I am instantiating the interface "SasSendDocument.class" in my JBuilder project and can deploy and run the application but when I try and create a web service from the project it starts complaining about the fact that I am using an interface. XmlBeans "scomp" also generated a SasSendDocumentImpl.class that I have tried to use to overcome this problem (althoughin WLWorkshop I have always used the XmlBeanDocument object), but I then get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: No default constructor was found for class com.bt.sas.xml.impl.SasResultDocumentImpl loaded from file:/D:/Classpath/SasReturnSrc.jar!/com/bt/sas/xml/impl/SasResultDocumentImpl.class.All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor - with nested
> Here it seems to be complaining that the class has no default constructor. However, these classes are auto-generated by XmlBeans for me and I don't believe I should have to tinker with the source and recompile. Anyway, even if I do change the class I cannot update the .xsb files which were produced by the XmlBeans compiler.
> Any ideas greatfully received :)
> Regards
> Davy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Closed: (XMLBEANS-142) XmlBeans - Web service -
BindingException
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacob Danner closed XMLBEANS-142.
---------------------------------
Assignee: (was: Radu Preotiuc-Pietro)
Per comments, this issue should be closed.
> XmlBeans - Web service - BindingException
> -----------------------------------------
>
> Key: XMLBEANS-142
> URL: https://issues.apache.org/jira/browse/XMLBEANS-142
> Project: XMLBeans
> Issue Type: New Feature
> Components: XmlObject
> Affects Versions: Version 2 Beta 1
> Environment: Win Xp SP2 - deploying to Weblogic Server 8.1
> Reporter: david mcilroy
> Priority: Blocker
> Fix For: TBD
>
>
> Hi,
> I am working with XmlBeans in Jbuilder and have created a project that contains a couple of EJBs that use XmlBeans to compile and manipulate a couple of XSD Schema files. The application works fine when deployed to Weblogic as an EJB, however when I configure the project as a Web Service and rebuild I get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: Invalid class received: interface com.bt.sas.SasSendDocument loaded from file:/D:/CLASSPATH/XmlBeanProject/xmlTypesSasSend.jar!/com/bt/sas/SasSendDocument.class. All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor
> As I hinted above I am instantiating the interface "SasSendDocument.class" in my JBuilder project and can deploy and run the application but when I try and create a web service from the project it starts complaining about the fact that I am using an interface. XmlBeans "scomp" also generated a SasSendDocumentImpl.class that I have tried to use to overcome this problem (althoughin WLWorkshop I have always used the XmlBeanDocument object), but I then get the following error:
> [servicegen] weblogic.xml.schema.binding.BindingException: No default constructor was found for class com.bt.sas.xml.impl.SasResultDocumentImpl loaded from file:/D:/Classpath/SasReturnSrc.jar!/com/bt/sas/xml/impl/SasResultDocumentImpl.class.All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor - with nested
> Here it seems to be complaining that the class has no default constructor. However, these classes are auto-generated by XmlBeans for me and I don't believe I should have to tinker with the source and recompile. Anyway, even if I do change the class I cannot update the .xsb files which were produced by the XmlBeans compiler.
> Any ideas greatfully received :)
> Regards
> Davy
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org