Hello again. Thanks for your responses. I have run the samples/ejb exercise, and the EJBs were deployed OK (on the face of it - they appear in the Axis list of services offered, and I can look at xxx?wsdl ok) and the SimpleBean said hello back to me no problem. I couldn't get my client to talk to the NiceThingsBean, though. I think this is due to either the JNDI name or the namespace given in the .wsdd for the NiceThingsBean, but I'm not that far with my learning yet that I can fix it...
Here is the response from Java2WSDL when I run it against the remote interface of the EJB I want to expose. Please forgive me if I'm being thick here. :-) Regards, Dan ------------------- response from Java2WSDL ---------------------- C:\work\ws>java org.apache.axis.wsdl.Java2WSDL -o sch.wsdl -l"http://localhost:8080/axis/services/sch"; -n "urn:sch" -p"sch" "urn:sch" sch.WEBSRVC_ORDER_IN_LMS_Remote 17:01:10,736 WARN - The class com.ca.gen65.vwrt.vdf.VDF does not contain a default constructor, which is a requirement for a bean class. The class cannot beconverted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file. 17:01:10,814 WARN - The class java.lang.Character is defined in a java or javax package and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file. 17:01:10,970 WARN - The class char is not a bean class and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file. 17:01:11,002 WARN - The class java.lang.StringBuffer is defined in a java or javax package and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file. 17:01:11,033 WARN - The class com.ca.gen65.vwrt.IExportView does not contain a default constructor, which is a requirement for a bean class. The class cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file. 17:01:11,033 WARN - The class javax.ejb.EJBHome is defined in a java or javaxpackage and cannot be converted into an xml schema type. An xml schema anyTypewill be used to define this class in the wsdl file. 17:01:11,033 WARN - The class javax.ejb.Handle is defined in a java or javax package and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file. 17:01:11,033 WARN - The class javax.ejb.EJBObject is defined in a java or javax package and cannot be converted into an xml schema type. An xml schema anyType will be used to define this class in the wsdl file. C:\work\ws> > -----Original Message----- > From: Venkat Reddy [mailto:[EMAIL PROTECTED] > Sent: 09 February 2005 12:07 > To: [EMAIL PROTECTED] > Subject: Re: Newbie with EJB/web service problem > > Just to ensure that the environment is alright, did you try building > and running the samples/ejb in axis? > > As you mentioned, the issue could be with code generation (java2wsdl, > wsdl2java). What errors did you get when you ran WSDL2Java? Need to > resolve issues with the EJB classes to run Java2WSDL and WSDL2Java > properly. > > In the worst case, you might need to handcraft the WSDL file and run > WSDL2Java. > > -- Venkat > > > > On Tue, 8 Feb 2005 17:10:53 -0000, Dan Hobbs > <[EMAIL PROTECTED]> wrote: > > Hello, I'm new to web services and I'm having real trouble exposing an > EJB > > as a web service. I'm not sure whether what I'm trying to do is > impossible > > though, or whether I am approaching this in entirely the wrong way... > > > > I am using Axis 1.2RC2 on Tomcat 4.1.31/Windows 2000 Professional. I am > > familiar enough with Tomcat, it's just web services where my head is > > spinning because there seem to be so many ways of doing things! > > > > I also have the option of putting Axis within JBoss (I have v4.0.0) (I > have > > removed the jboss-ws4ee.sar folder and got Axis working OK within > JBoss). > > > > All OK so far, but when I try to do something useful... > > > > My task is to expose an EJB (which has been generated by a 3rd party, > and I > > can't see the source of the runtime helper classes it uses). I > successfully > > ran Java2WSDL (on the EJB remote interface) to create the .wsdd but > received > > warnings about some of the objects used for I/O not having default > > constructors so not being mappable to XML. I cannot therefore run > WSDL2Java > > on the .wsdd to create the endpoint stub. > > > > I have considered writing a wrapper EJB whose call method has a similar > > signature, but has equivalent classes with default constructors, but I'm > not > > sure whether that is feasible because I don't know how the clients of > the > > EJB will be built. > > > > I have also thought about putting a service-endpoint into ejb-jar.xml, > but > > by now I am so confused I'm not sure which direction I should be > heading. > > > > If anyone has any advice on whether this is possible, and what I should > be > > doing, then it would be greatly appreciated. > > > > Regards, > > > > Dan > > > >
