July 2007 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: JBossEjbParsingDeployer can't handle EJB3 jboss.xml

by wolfc

It's not really as such in EJB 3. We got instance level annotations. It took me a while to realize this. We instantiate a class container per ejb and add annotations to it. Then at the next stage we don't get the annotations from the class, but resolve the annotations from class container. This works as long as it only affects the ejb bean class. It doesn't work for interceptor classes. So either I've to abandon this model or add extra annotations for instance metadata related to other classes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059583#4059583 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059583

17 years, 8 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Tomcat Deployer is wrong in JBoss Head

by adrian＠jboss.org

The Tomcat Deployer in JBoss Head should not be starting Tomcat. The deployer should just be creating MBeans that have a dependency on Tomcat with Tomcat started from the deploy directory as a service. It needs splitting into two deployments, a WARDeployer and a Tomcat/JBossWEB service. This will also allow "on demand" where if there are no web deployments Tomcat doesn't need to start. I've just had to hack JCA to put the "Cached Connection Manager" in the jca deployers otherwise Tomcat (really the WARDeployer) won't start with the CachedConnectionManagerValve enabled. This is only a temporary solution! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059579#4059579 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059579

17 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - Re: UserTransactedStartedListener is not implemented in EJB3

by adrian＠jboss.org

NOTE: The embedded UserTransactions has the same problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059567#4059567 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059567

17 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - Re: UserTransactedStartedListener is not implemented in EJB3

by adrian＠jboss.org

I think the way this does is pretty bad. It requires each UserTransaction to implement a static method to inject the transaction started listener | //Registration for CachedConnectionManager so our UserTx can notify | //on tx started. | private static ServerVMClientUserTransaction.UserTransactionStartedListener tsl; | | /** | * The <code>setUserTransactionStartedListener</code> method is called by | * CachedConnectionManager on start and stop. The tsl is notified on | * UserTransaction.begin so it (the CachedConnectionManager) can enroll | * connections that are already checked out. | * | * @param newTsl a <code>ServerVMClientUserTransaction.UserTransactionStartedListener</code> value | */ | public static void setUserTransactionStartedListener(ServerVMClientUserTransaction.UserTransactionStartedListener newTsl) | { | tsl = newTsl; | } | Then the cached connection manager (CCM) needs to know about all listeners: | | protected void startService() | throws Exception | { | tm = (TransactionManager) getServer().getAttribute(transactionManagerServiceName, | "TransactionManager"); | TransactionSynchronizer.setTransactionManager(tm); | ServerVMClientUserTransaction.getSingleton().registerTxStartedListener(this); | EnterpriseContext.setUserTransactionStartedListener(this); | } | It would be much better if the CCM had a single place to register the listener and then each UserTransaction notified that single place of transaction start. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059563#4059563 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059563

17 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - UserTransactedStartedListener is not implemented in EJB3

by adrian＠jboss.org

This relates to JBCTS-599 but I can explain it without reference to that. There is a little known feature in JavaEE called lazy transaction enlistment. It basically works with the UserTransaction where you retrieve a connection before starting the transaction and then ut.begin() enlists the connection. | // BMT EJB(3) method | public void doSomething() | { | DataSource ds = ... | Connection c = ds.getConnection(); // Not enlisted in transaction, there isn't one | UserTransaction ut = ... | ut.begin(); // the connection is enlisted in the transaction | } | It even works across multiple transactions | public void doSomething() | { | DataSource ds = ... | Connection c = ds.getConnection(); // Not enlisted in transaction, there isn't one | UserTransaction ut = ... | ut.begin(); // the connection is enlisted in the transaction | ut.commit(); // connections is unenlisted | ut.begin(); connection is enlisted in the new/different transaction | } | The problem is that EJB3 is not firing the transaction started events from its user transaction. Compare EJB2/EJB3: org.jboss.ejb.EnterpriseContext/org.jboss.ejb3.tx.UserTransactionImpl | | public void begin() | throws NotSupportedException, SystemException | { | TransactionManager tm = con.getTransactionManager(); | | int oldTimeout = -1; | if (tm instanceof TransactionTimeoutConfiguration) | oldTimeout = ((TransactionTimeoutConfiguration) tm).getTransactionTimeout(); | | // Set the timeout value | tm.setTransactionTimeout(timeout); | | try | { | // Start the transaction | tm.begin(); | | // HERE!!!!!!!!!!!!! notify checked out connections | if (tsl != null) | tsl.userTransactionStarted(); | | Transaction tx = tm.getTransaction(); | if (trace) | log.trace("UserTx begin: " + tx); | In fact, if you compare the two classes you'll see that the EJB3 user transaction is incomplete in other ways (such as resetting the transaction timeout after the begin). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059560#4059560 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059560

17 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBossEjbParsingDeployer can't handle EJB3 jboss.xml

by adrian＠jboss.org

"wolfc" wrote : As for the order: at one point we must have a full set of meta data attached for use in the SecurityDeployer & WebServices. | Either we do parse & scan = complete or scan & parse = complete. Since xml overrides annotations my vote is for: scan then parse. Actually, xml overrides annotations because they are different things! :-) Class level metadata == annotations Instance level metadata == xml (or predetermined attachments) Instance (the Object level) overrides Class (shared across objects). The order of populating does not matter if you get this basic fact correct. See the hierarchical metadata stuff in the jboss-container project which is also available in aop. This is how we allow instance level annotation overrides in the microcontainer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059556#4059556 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059556

17 years, 8 months

1
0
0 / 0

[TODO - DEVELOPMENT] - News reader portlet

by manousopul

I' like to add functionality to news reader portlet developed by Roy Russo. At the existing version of the portlet, the logged user reads rss items of one single rss feed. The idea is to handle with more rss feeds that will be saved at user preferences. I try to contact Roy Russo but no success. Can anyone help me to contact with him?? Thank you, Chris View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059518#4059518 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059518

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-1006 - Throwing exception when failover fail

by clebert.suconic＠jboss.com

This should be pretty easy to try. I will try it out on monday. The problem was failover was interrupting failover and keepting the session half way. I have fixed the order where the client is set already (before failover). I will try closing the session when this happens. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059451#4059451 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059451

17 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Usage of the new jboss50 new deployer architecture

by thomas.diesler＠jboss.com

1) Fix the build so it is reproducable yes, this is an outstanding issue which is caused by dependencies of our integration layers on projects that have no tagged release. It definitely needs to be done. 2) Don't reinvent the deployers framework We are taking the concepts of the deployer architecture and make them available accross AS50, AS42, AS40 3) Fix the error handling Please be more specific 4) Reuse the already developed code instead of re-inventing it and introducing alternate bugs. If it is doesn't quite do do what you want then add some new callbacks like the accepts() I added to the parsing deployers so EJB3 can do its hacks. :-) No comment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059437#4059437 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059437

17 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums July 2007