You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beehive.apache.org by "Chad Schoettger (JIRA)" <be...@incubator.apache.org> on 2005/08/22 17:41:08 UTC

[jira] Updated: (BEEHIVE-52) Type errors are not informatiove

     [ http://issues.apache.org/jira/browse/BEEHIVE-52?page=all ]

Chad Schoettger updated BEEHIVE-52:
-----------------------------------

    Attachment: BEEHIVE-52.diff

The reported bug could not be reproduced.  I did cleanup this sample so it will build and so it uses the JDBC-Control instead of the old sample database control.  Patch attached.

> Type errors are not informatiove
> --------------------------------
>
>          Key: BEEHIVE-52
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-52
>      Project: Beehive
>         Type: Improvement
>   Components: Web Services (181)
>     Versions: TBD
>     Reporter: daryoush mehrtash
>     Assignee: Chad Schoettger
>     Priority: Minor
>      Fix For: TBD
>  Attachments: BEEHIVE-52.diff
>
> When your data types are not valid (not serializable, is a file,...)  The following error message is returned:
> Caused by: org.apache.beehive.wsm.axis.InvalidTypeMappingException: failed to re
> gister org.apache.beehive.wsmSample.dbControlExtension.WSEmployee as a valid web
>  service datatype, consider using a custom type mapping
>         at org.apache.beehive.wsm.axis.AxisHook.configureTypeMapping(AxisHook.ja
> va:367)
>         at org.apache.beehive.wsm.axis.AxisHook.createServiceDesc(AxisHook.java:
> 139)
>         at org.apache.beehive.wsm.axis.AnnotatedWebServiceDeploymentHandler.crea
> teSOAPServiceUsingAnnotations(AnnotatedWebServiceDeploymentHandler.java:199)
>         at org.apache.beehive.wsm.axis.AnnotatedWebServiceDeploymentHandler.crea
> teSOAPServiceFromAnnotatedClass(AnnotatedWebServiceDeploymentHandler.java:164)
>         at org.apache.beehive.wsm.axis.AnnotatedWebServiceDeploymentHandler.invo
> ke(AnnotatedWebServiceDeploymentHandler.java:110)
>         ... 42 more
> This is not informative enough,  each type of error should have its own error message.

-- 
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