From: Juha-P L. <jpl...@cc...> - 2002-04-28 20:09:59
|
On Sun, 28 Apr 2002, marc fleury wrote: > > 2 solutions. > 1- I build a mapper that takes String and returns ObjectName > 2- you build a ObjectName implementation that caches the ObjectName and > returns the right Object if you pass me exactly the same String. > > Come to think of it we probably need the first one. Can you expose it at > the JMX level? I have an idea for it but (obviously) haven't looked at the details yet. Might be a deliverable. Right now I need to take a time out on this. Need to finish the inforIT, explain our interceptors to EG and then do that finetuning for training slides. -- Juha I believe the registry idea must be present at the JMX > level, then you would put the objectname mapped to the String name and that > is fast enough for me to use and STANDARDIZE on inside the server. > > Bar that, the spirit dies for a spec quirk > > |MBean's do you imagine having in your server, could you create the object > |names for them on the server side and lookup the same instances from a > |"cache" -- I know it sounds ass backwards but given then future plans on > |JMX it would be best to avoid too much reliance on the JMX classes > |themselves. > > correct that is what I understand we need that "cache". It is the Registry > idea with more generic mappings. It is a system level Registry juha. > > In a invoker I want to pass the String and use that to map to the ObjectName > on the server or maybe expose an invoke that doesn't work with ObjectNames? > something that makes sense. Keep exceptions out of the design. > > marcf > > ++++++++++++++++++++++++++++++++++++++++ > "I will not watch my people die while > you discuss this invasion in a commitee" > -- some silly queen in a SF movie-- > ++++++++++++++++++++++++++++++++++++++++ > > -- Juha Lindfors Author of "JMX: Managing J2EE with Java Management Extensions" Senior Developer, JBoss Group LLC |