Re: Web Service WSDL Location
Nevermind... I got it working. I could swear that I had the line
"properties.setProperty("openejb.embedded.remotable", "true");" there at
first, and it wasn't working. So then I came to these forums and I read
someone saying that line isn't needed for web services, so I took it out.
After adding it back, it starting working. I'm not 100% sure if that was the
only fix. After adding it I was still getting the same problem, but while I
was pasting the code for my test case it just started working. Thanks.
David Blevins wrote:
>
>
> On Jul 24, 2008, at 3:12 PM, endium wrote:
>
>>
>> I am doing some unit testing using web services. I tried following the
>> example web service project as a guide. I am getting:
>> Caused by: javax.wsdl.WSDLException: WSDLException:
>> faultCode=PARSER_ERROR:
>> Problem parsing 'http://localhost:4204/ZipCodeWidget?wsdl'.:
>> java.net.ConnectException: Connection refused: connect
>>
>> I think this is because I am specifying the wrong wsdl location. I
>> have no
>> idea really what to specify, from the example project it looks like
>> the
>> default is the name of the webservice implementation class. That's not
>> working for me though.
>
> Can you post your test case?
>
> Also, definitely make sure you keep the
> "properties.setProperty("openejb.embedded.remotable", "true");" line
> from the example.
>
> -David
>
>
>
>
--
View this message in context:
http://www.nabble.com/Web-Service-WSDL-Location-tp18641626p18658908.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Web Service WSDL Location
On Jul 24, 2008, at 3:12 PM, endium wrote:
I am doing some unit testing using web services. I tried following the
example web service project as a guide. I am getting:
Caused by: javax.wsdl.WSDLException: WSDLException:
faultCode=PARSER_ERROR:
Problem parsing 'http://localhost:4204/ZipCodeWidget?wsdl'.:
java.net.ConnectException: Connection refused: connect
I think this is because I am specifying the wrong wsdl location. I
have no
idea really what to specify, from the example project it looks like
the
default is the name of the webservice implementation class. That's not
working for me though.
Can you post your test case?
Also, definitely make sure you keep the
"properties.setProperty("openejb.embedded.remotable", "true");" line
from the example.
-David
Re: help with this error [Virus checked]
On Jul 23, 2008, at 2:01 AM, [EMAIL PROTECTED] wrote: Hi experts, I try to run a test case from eclipse, I get this error and have no idea what it's all about. Any help ? Apache OpenEJB 3.0build: 20080408-04:13 http://openejb.apache.org/ INFO - openejb.home = D:\Dokumente und Einstellungen\DE16297\workspace\oejb3-jpa INFO - openejb.base = D:\Dokumente und Einstellungen\DE16297\workspace\oejb3-jpa INFO - Configuring Service(id=Default Security Service, type=SecurityService, provider-id=Default Security Service) INFO - Configuring Service(id=Default Transaction Manager, type=TransactionManager, provider-id=Default Transaction Manager) INFO - Configuring Service(id=Default JDK 1.3 ProxyFactory, type=ProxyFactory, provider-id=Default JDK 1.3 ProxyFactory) INFO - Found EjbModule in classpath: D:\Dokumente und Einstellungen\DE16297\workspace\oejb3-jpa\target\classes INFO - Configuring app: D:\Dokumente und Einstellungen\DE16297\workspace\oejb3-jpa\target\classes FATAL - OpenEJB has encountered a fatal error and cannot be started: The Assembler encountered an unexpected error while attempting to build the container system. java.lang.NoClassDefFoundError: org/objectweb/asm/FieldVisitor at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) Seems like the asm-2.2.3.jar is not in your IDEs classpath. -David
