"[EMAIL PROTECTED]" wrote : I think that would be OK for usage in the AS, 
but... does JBC have the ability to bind a Cache instance in JNDI?  AFAIK when 
we do that now we're relying on the AS's proxy factories.

Is this necessary?  Wouldn't a simple 


  | new InitialContext().bind(jndiName, cacheInstance);
  | 

do the trick, since we'd only be binding to local JNDI?


"[EMAIL PROTECTED]" wrote : The other one I can think of would be more 
app-specific mgmt consoles, e.g. show me the names all the sessions in the 
cache for webapp X, which would use a JMX call to getChildrenNames.  For a mgmt 
console people don't want to use JNDI as it leads to the need to have JBC 
classes available to the console.

I agree, but could this be construed as management info - and be made avbl in 
the CacheMBean?  E.g., a method like:


  |    /**
  |    * Returns a string representation of all children and the number of 
  |    * attributes in each child, as well as number of children on each child.
  |    * NB: Only works for String based Fqns.
  |    */
  |    String getChildrenNames(String fqn);
  | 


View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971235#3971235

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971235
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to