Thanks, Carlin. Eddie
On 11/9/05, Carlin Rogers (JIRA) <[email protected]> wrote: > [ http://issues.apache.org/jira/browse/BEEHIVE-52?page=all ] > > Carlin Rogers closed BEEHIVE-52: > -------------------------------- > > Resolution: Cannot Reproduce > > Closing this issue. Chad stated in the bug that the original issue cannot be > reproduced. > > As Chad noted in the beehive dev list, this bug had a patch on it to update > the wsm-employee sample to use the Beehive JdbcControl rather than the old > controls-db sample. Eddie has made these changes to the wsm-employee sample. > See svn revision 330867 on 11/4/2005... > http://svn.apache.org/viewcvs?rev=330867&view=rev > > > 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) > > Reporter: daryoush mehrtash > > Assignee: Eddie O'Neil > > Priority: Minor > > 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 > >
