[ http://issues.apache.org/jira/browse/GERONIMO-856?page=all ]

Joe Bohn updated GERONIMO-856:
------------------------------

        Summary: Exception in JMS Connector Factory Portlet & Database 
Connections Portlet  (was: Exception in JMS Connector Factory Portlet)
    Description: 
A Portlet Exception was being caught and thrown because the 
JMSConnectionFactoryManagerPortlet assumes that the retrieval of an attribute 
"state" from the GBean will be successful and not throw an attribute not found 
exception (which is what it is doing).

It appears that the state of the GBean instead should be retrieved from the 
kernel for that GBean.

This same error exists in the AbstractConnectionFactoryManagerPortlet

  was:
A Portlet Exception was being caught and thrown because the 
JMSConnectionFactoryManagerPortlet assumes that the retrieval of an attribute 
"state" from the GBean will be successful and not throw an attribute not found 
exception (which is what it is doing).

It appears that the state of the GBean instead should be retrieved from the 
kernel for that GBean.


> Exception in JMS Connector Factory Portlet & Database Connections Portlet
> -------------------------------------------------------------------------
>
>          Key: GERONIMO-856
>          URL: http://issues.apache.org/jira/browse/GERONIMO-856
>      Project: Geronimo
>         Type: Bug
>   Components: management
>     Versions: 1.0-M4
>  Environment: Windows XP
>     Reporter: Joe Bohn
>  Attachments: jmsPortlet.patch
>
> A Portlet Exception was being caught and thrown because the 
> JMSConnectionFactoryManagerPortlet assumes that the retrieval of an attribute 
> "state" from the GBean will be successful and not throw an attribute not 
> found exception (which is what it is doing).
> It appears that the state of the GBean instead should be retrieved from the 
> kernel for that GBean.
> This same error exists in the AbstractConnectionFactoryManagerPortlet

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to