Using different names for SEI and Service solved the problem!
:-) Thank you very much, Jitendra!!!
In a way, this was a strange thing. Was there any chance for me to find
the reason by myself? I tried the "verify J2EE compliance tool", but
that gave me no hint. Should choosing the same name being avoided (maybe
by rejecting it in wscompile or so) or (as I said, it worked in
WebSphere) is this a thing which happened due to "reference
implementation" state of Sun J2EE?
Again, many thanx!
Merten
> -----Original Message-----
> From: Jitendra Kotamraju [mailto:Jitendra.Kotamraju_at_Sun.COM]
> Sent: Thursday, July 22, 2004 11:06 PM
> To: users_at_jax-rpc.dev.java.net
> Subject: Re: problem with JAX-RPC web service in J2EE 1.4 RI,
> internal server error (ClassCastException) from generated tie
>
> Merten Schumann wrote:
> > Hello,
> >
> > I'm using the J2EE 1.4 RI, update 1.
> > I created the HelloService sample according to the latest J2EE 1.4
> > tutorial.
> > With wscompile I created WSDL and mapping.xml; with
> deploytool I created
> > the .war and deployed it.
>
> Looks like you have SEI and service both have the same name
> "HelloService". May be you can change the service name in the config
> file while generating the mapping file.
>
> <?xml version="1.0" encoding="UTF-8"?>
> <configuration
> xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
> <service name="XXX"
> ...
>
> </service>
> </configuration>
>
> Let me know how it goes.
>
> Thanks,
> Jitu
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net