Jboss problems

[Il Solco Vinilico]

Hello to everybody,

I have a problem:
I have create a web server with jboss e jax-rpc.
the server web is ok, and when I put this address in the browser

http://localhost:8080/MioWebServer/WebService?WSDL

I can see the xml page.

After I created an application client, with the file WSDL
http://localhost:8080/MioWebServer/WebService?WSDL and I wrote
this simple class:

-------------------------------------------------------------------------------
package javaapplication24;

import clientService.*;
import javax.xml.rpc.Stub;
/**
*
* @author admin
*/
public class Main {

public static void main(String[] args) {
try{
Stub stub = creaProxy();
stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY,"http://localhost:8080/MioWebServer/WebService");
WebServiceSEI classe = (WebServiceSEI)stub;
String saluto = classe.saluta("Gino");
System.out.println(saluto);
}catch(Exception ex){
ex.printStackTrace();
}
}

private static Stub creaProxy(){
return (Stub)(new WebService_Impl().getWebServiceSEIPort());
}
}
------------------------------------------------------------------------------------

when I compiling that, is all ok, but if I esecute the program I have this
error:

**** errore ****

run-single:
java.rmi.ServerException: Endpoint cannot handle requests in state: CREATED
at
com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:510)
at
com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:307)
at
clientService.WebServiceSEI_Stub.saluta(WebServiceSEI_Stub.java:69)
at javaapplication24.Main.main(Main.java:26)
BUILD SUCCESSFUL (total time: 4 seconds)

***************

I'm working on that since two days, do you have soma idea for solving this
problem?
:-(

[Philipp Taprogge]

Hi!

Thus spake Il Solco Vinilico on 04/27/2007 10:57 AM:
> **** errore ****
>
> run-single:
<snip>
It would be more helpful to have a look at the jboss server log.
Your client just gives you the error it got from jboss. Why the
error occurred and the stacktrace can only be found in the server's
log. Maybe the service did not even deploy correctly...

Regards,

Phil