[JBoss-dev] MBeanServer and EAR-Scoping

2002-09-06 Thread Michael Bartmann

Hi everybody,

I use JMX to manage an MBean inside an EAR-scope.
It has methods with arguments and return values
of a class which is only known inside the EAR-Scope
(and of course known to the client connecting to the MBeanServer).

If objects of those ear-private classes are a return value
(server - client) serialization works. This is no surprise,
each object knows where it came from.

If the client puts parameters of those ear-private in the method
(client - server) the server has to de-serialize and fails.
Even this is no surprise.

But: could you think about allowing the JMX-server to access the
ears repository?

Regards,
Michael Bartmann

PS.: tested under Branch_3_2.



---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] MBeanServer and EAR-Scoping

2002-09-06 Thread David Jencks

Just to be a little more definite, how are you communicating with the jmx
server?  I think that is the part doing the deserialization... (and on the
other end the serialization)

thanks
david jencks

On 2002.09.06 15:55:46 -0400 Michael Bartmann wrote:
 Hi everybody,
 
 I use JMX to manage an MBean inside an EAR-scope.
 It has methods with arguments and return values
 of a class which is only known inside the EAR-Scope
 (and of course known to the client connecting to the MBeanServer).
 
 If objects of those ear-private classes are a return value
 (server - client) serialization works. This is no surprise,
 each object knows where it came from.
 
 If the client puts parameters of those ear-private in the method
 (client - server) the server has to de-serialize and fails.
 Even this is no surprise.
 
 But: could you think about allowing the JMX-server to access the
 ears repository?
 
 Regards,
 Michael Bartmann
 
 PS.: tested under Branch_3_2.
 
 
 
 ---
 This sf.net email is sponsored by: OSDN - Tired of that same old
 cell phone?  Get a new here for FREE!
 https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] MBeanServer and EAR-Scoping

2002-09-06 Thread Michael Bartmann

Through RMIAdaptor.

Object obj = ctx.lookup(jmx:local:rmi);
RMIAdaptor adaptor = ((RMIAdaptor)obj);
RemoteMBeanServer connector = new RMIConnectorImpl(adaptor);
...
blabla.invoke(...);


When replacing the problematic parameter by byte[] and doing the
serialization by hand in the ear and on the client everything
works.

The strage thing is:
When the access fails, there is no log message on the server
console.




---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development