On 15/07/2004 3:10 AM, Dain Sundstrom wrote:
On Jul 14, 2004, at 4:47 AM, Gianny Damour wrote:
Sorry; indeed, this is perhaps not the right approach. However, I was
pretty confident that this new behavior was more correct:
As far as I understand, the JMX GBeanInvokers are used only when the
On 14/07/2004 6:44 AM, [EMAIL PROTECTED] wrote:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-267
Here is an overview of the issue:
On 14/07/2004 9:17 AM, Gianny Damour wrote:
org.apache.geronimo.gbean.jmx.NoSuchOperationError: No implementation
method:
objectName=geronimo.server:J2EEApplication=skeleton/app,J2EEModule=skeleton-ejb.jar,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=StatelessSession,
method=public
On 14/07/2004 12:09 PM, Dain Sundstrom wrote:
On 14/07/2004 9:17 AM, Gianny Damour wrote:
I have just updated the way GBean attribute names are derived:
When GBeans are proxied via RawGBeanInvokers, attribute names may
start with an upper-case letter. For instance, if a GBean has a
method
On Wed, Jul 14, 2004 at 11:01:18AM +1000, Gianny Damour wrote:
This was the behavior before my updates and I have restored it.
Thanks for the speedy fix Gianny, it seems to work: the exception's no
longer being thrown.
Regards,
Toby
On Jul 14, 2004, at 4:47 AM, Gianny Damour wrote:
On 14/07/2004 12:09 PM, Dain Sundstrom wrote:
On 14/07/2004 9:17 AM, Gianny Damour wrote:
I have just updated the way GBean attribute names are derived:
When GBeans are proxied via RawGBeanInvokers, attribute names may
start with an upper-case
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-267
Here is an overview of the issue:
-
