Okay, it looks like what was going on is that the build.xml uses a
single classpath for both client and server, so when I'm running
wsdeploy after creating the client code it sees a
SeismicService_SerializerRegistry class in the client code and assumes
it doesn't need to create one, even though that class is not included in
the war file. I'd think this should be considered a bug in wsdeploy - it
should make sure the necessary classes are actually in the war, not just
on its classpath.
- Dennis
Doug Kohlert wrote:
>Dennis,
>If there is no xxx_SerializerRegistry in your war file then something
>went wrong
>with wsdeploy. Try to run wsdeploy with the -verbose option to see if
>you get
>any warnings or errors?
>
>Dennis Sosnoski wrote:
>
>
>
>>Thanks, I found the exception in the launcher.server.log:
>>
>>java.lang.NoClassDefFoundError:
>>com/sosnoski/seismic/jaxrpc/SeismicService_SerializerRegistry
>> at com.sosnoski.seismic.jaxrpc.Seismic_Tie.<init>(Seismic_Tie.java:32)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>Method)
>> ...
>>
>>>From looking at the HelloWorld example I'm using as a base, I gather
>>the xxxx_SerializerRegistry class is added when the deployable WAR
>>file is created. In my case I'm getting a bunch of other classes added
>>(including the Seismic_Tie class, and a bunch of
>>yyyy_LiteralSerializer classes), but no xxxx_SerializerRegistry. The
>>build-war Ant task says it's successful, and as far as I can see I'm
>>using the same options as the HelloWorld example).
>>
>>Any idea what to look at next?
>>
>> - Dennis
>>
>>
---------------------------------------------------------------------
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