[JBoss AOP] - Hotswapping an interceptor to an EJB
by Giordacchio++
Hi !
I have a strange erroer when I try use hotswapping. I want to attach dinamically an interceptor to a method of an EJB.
I have prepared the class that I want to intercept with this tag in my jboss-aop.xml:
| <prepare expr="all(it.webscience.atlasweb.controller.SessionManagerAction)"/>
But when I try to deploy my app I get this strange exception exactly on the EJB that I want to intercept!
Someone knows why the exception says that my EJB has two destroy method when actually it has only one ??
Thx ;-)
15:15:13,083 ERROR [[/atlasweb]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
| java.lang.IllegalStateException: component has two @Destroy methods: sessionManager
| at org.jboss.seam.Component.initMembers(Component.java:406)
| at org.jboss.seam.Component.<init>(Component.java:250)
| at org.jboss.seam.Component.<init>(Component.java:203)
| at org.jboss.seam.init.Initialization.addComponent(Initialization.java:724)
| at org.jboss.seam.init.Initialization.addComponents(Initialization.java:650)
| at org.jboss.seam.init.Initialization.init(Initialization.java:407)
| at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
| at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
| at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
| at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
| at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
| at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
| at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
| at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
| at org.jboss.web.WebModule.startModule(WebModule.java:83)
| at org.jboss.web.WebModule.startService(WebModule.java:61)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor146.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy38.start(Unknown Source)
| at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990031#3990031
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990031
19Â years
[JBoss Portal] - Permissions Portal Pages and Portlets
by engela
I'm using Jboss portal 2.4.0 and Jboss AS 4.0.4 GA.
Portal Page Permissions
----------------------------
When I create a new page the security setting for the page for Unchecked is set to viewrecursive, but I would like to restrict the access to the page to certain admininstrators only. How can I achieve this?
Portlet Permissions
----------------------
Within a portal page I have a Portlet A and a Portlet B. I would like to restrict the access of Portlet A to Administrators. I went to the security settings page for the portal page and set the security setting from viewrecursive to view for all users. Then I went to the security settings for Portlet A and set the security settings only an Administrator to View. Despite this Portlet A can be viewed by whoever can access the page.
How can change the settings to achieve my goal i.e. that only administrators can view Portlet A?
Thanks...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990026#3990026
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990026
19Â years
[JBoss Seam] - Bugs? Weird transaction problems
by toni
Hi,
I have a JSP file, which contains a table that displays a list of clients. Each of the clients can have many addresses attached to it.
If you click on one of the clients you end up on a second page, which again displays a table that lists all the addresses of the selected client.
There exists a corresponding Statefull Session Bean (SSB) for each JSP. Both SSBs called ClientAction and AddressAction contain a funtion, which returns the DataModel containing the clients and addresses respectively.
The first SSB also has a function, which returns the selected Client from the DataModel, so that the second SSB can get the currently selected client to display his addresses:
public Client getSelection()
{
return (Client) dataModel.getRowData();
}
The second SSB calls the above function to get the currently selected Client and to retrieve the client's addresses to initialize it's own DataModel that it needs for it's JSP page.
If this function is called from the AddressAction SSB and we do NOT use an EXTENDED persistent context inside the ClientAction SB (see NOTE A), then we get the first exception (this is only the beginning):
"Caused by: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: de.pilati.calc.model.Client.proposals, no session or session was closed"
After I change the persistent context of the ClientAction SSB to an extended one, I get rid of the exception, but noticed something else, which seems very strange to me: It's a matter of live or death for my application, from which method inside the AddressAction the getSelection() method gets called.
In particular I it's very unhealty to call it from within the "getAddresses()" method of the AddressAction SSB, which is used to initalize the DataModel for use in the JSP file that displays the addresses. If I place the getSelection() method into the function which returns(!) the DataModel, the I get the following exception:
"Caused by: org.hibernate.TransactionException: Could not register synchronization
at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:159)
at org.hibernate.ejb.EntityManagerImpl.close(EntityManagerImpl.java:59)
at org.jboss.ejb3.stateful.StatefulBeanContext.closeExtendedPCs(StatefulBeanContext.java:284)
at org.jboss.ejb3.stateful.StatefulBeanContext.remove(StatefulBeanContext.java:268)
... 169 more
Caused by: javax.transaction.RollbackException: Already marked for rollback TransactionImpl"
If I instead move the "getAddresses()" out of the function, which returns the DataModel to the JSP page that displays the addresses into the the "list()" function, which gets called when the user clients onto the link that selects a client, then everything works fine. This is good, but it seems that something is very wrong here!?
To sum it all up I have two questions:
1.Why do I need a extended persitent context? After the ?getClients()? returns all the Entities should be detached from the persitent manger, shouldn't they? So why would a call to return the client (not the addresses inside) cause a LazyInitializationException, when I had retrieved the client object already before?! After all the getSelection only returns a client, which has already been fetched.
2.Why do I get a TransactionException, when I call the ?getSelection()? method in the function, which returns the DataModel to the JSP page(which needs it to render itself) but NOT when I place it into the method, which gets called to navigate to the JSP page???
Here are the important code snippets:
Client SSB
------------
public class ClientAction implements BasicClientAction
{
// NOTE A: This throws the first exception so I remove it
//@PersistenceContext
@PersistenceContext(type=PersistenceContextType.EXTENDED)
EntityManager entityManager;
// Stores all the clients
DataModel dataModel;
@Begin(join = true)
public DataModel getClients()
{
if (dataModel == null)
dataModel = new ListDataModel();
dataModel.setWrappedData(entityManager.createQuery("from Client").getResultList());
return dataModel;
}
public Client getSelection()
{
return (Client) dataModel.getRowData();
}
...
}
Address SSB
---------------
@Name("addressAction")
@Stateful
public class AddressAction implements BasicAdressAction
{
// Makes not difference if I set the context to extended or not
@PersistenceContext
EntityManager entityManager;
@In(create = true) @Out @Valid
Address address;
// Stores all the addresses of a SELECTED client
DataModel dataModel;
// This is needed to retrieve the currently selected client
@In(required = false)
BasicClientAction clientAction;
Client selectedClient;
public String list()
{
// NOTE B: Calling the getSelection() from here DOES NOT cause an excepiton
//selectedClient = clientAction.getSelection();
return "addresses";
}
@Begin(join = true)
public DataModel getAddresses()
{
if (dataModel == null)
dataModel = new ListDataModel();
// NOTE B: If the JSP page calls this fuction to initalize itself, the
// we get an exception
selectedClient = clientAction.getSelection();
dataModel.setWrappedData(selectedClient.getAddresses());
return dataModel;
}
...
}
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990025#3990025
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990025
19Â years