-
1. Re: JNDIView problem
adrian.brock Mar 22, 2002 6:55 AM (in response to johnprince)Hi,
This is a bug in jboss, I'm going to fix this and
some others this weekend.
You can fix this yourself by changing the
invoke() in JNDIView.list to use server.getAttribute()
the attribute name is "DeployedApplications"
Regards,
Adrian -
2. Re: JNDIView problem
squirest Mar 22, 2002 7:14 AM (in response to johnprince)Hey,
the version of JNDIView that you are using (1.12 I think) is trying to call a getter method for an attribute - something which is illegal.
Juha/Adrian, this problem is going to come up again and again until jboss/jbossmx releases are synch'd up WRT supported behaviour. Adrian, are you able to give advice as to which JBoss version works best?
To reiterate what I said yesterday, I think we should add a switch to relax "attribute methods are not operations". I take Adrian's point that jbossians don't like hacks but while we're trying to encourage early jbossmx adopters this sort of thing is just going to piss people off.
Trev -
3. Re: JNDIView problem
adrian.brock Mar 22, 2002 7:31 AM (in response to johnprince)Hi Trevor,
Yeh, somebody already fixed it. It is in latest HEAD from
REL_3_0_0_4. But that tag has the MBeanProxy problem.
I'm going to integrate this weekend unless I get a stop
from the dev-list.
I can then announce a release tag where JBoss uses
JBossMX and the java 1.4 problem goes away. :-)
Personally, I vote against the hack. I think the same
problem will arise with the jmxri.jar maintenance
release.
It is better developers spot this mistake early, rather
than get bitten by it in a live environment later.
But, you've got r/w if you want to provide
backwards compatiblity(TM)
Just make sure it is off by default.
Regards,
Adrian -
4. Re: JNDIView problem
squirest Mar 22, 2002 7:41 AM (in response to johnprince)Okay,
if you get a "stop" on the release tag I'll revisit the hack issue.
Trev