They are not broken out in terms of jar currently (all in one jar).
However, the org.jboss.remoting.serialization package can be broken out,
but will need to include
org.jboss.remoting.loading.ObjectInputStreamWithClassLoader as well.
Scott M Stark wrote:
It does not make sense to add the full remoting jar as there is no
dependency on this other than the serialization classes. This comes back
to the fact that org/jboss/invocation needs to be refactored into a
separate legacy remoting jar, and org.jboss.remoting.serialization
included in it or broken out. For now the minimal jar should just
include the org.jboss.remoting.serialization package classes. These are
self container aren't they?
-----Original Message-----
From: Tom Elrod
Sent: Friday, April 28, 2006 8:47 AM
To: Dimitris Andreadis
Cc: QA; jboss-development@lists.sourceforge.net; Clebert
Suconic; Tom Elrod
Subject: Re: Problem with minimal config in Branch_4_0
The problem stems from NamingService using
MarshalledInvocation, which now requires
org.jboss.remoting.serialization.IMarshalledValue and
org.jboss.remoting.serialization.SerializationStreamFactory
(which is found within jboss-remoting.jar).
However, jboss-remoting.jar is not included within
server/minimal/lib nor within jboss-minimal.jar. Easiest
thing to do would be to include jboss-remoting.jar in the
minimal/lib directory (which is 586K). This what you think
should be done Dimitris?
Dimitris Andreadis wrote:
Did something change recently in serialization/remoting?
run -c minimal
...
15:15:32,609 INFO [NamingService] JNDI bootstrap
JNP=/0.0.0.0:1099,
RMI=/0.0.0.0:1098, backlog=50, no client SocketFactory, Server
SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
15:15:32,629 WARN [ServiceController] Problem starting service
jboss:service=Naming
java.lang.NoClassDefFoundError:
org/jboss/remoting/serialization/impl/java/JavaSerializationManager
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123
)
...
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss:service=Naming
State: FAILED
Reason: java.lang.NoClassDefFoundError:
org/jboss/remoting/serialization/impl/
java/JavaSerializationManager
I Depend On:
jboss.system:service=ThreadPool
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development