Any idea when this will become reality for HEAD? The spaghetti
interceptor model is making the separation of EJB bits from the server
module very hairy if not impossible.
--jason
---
This SF.net email is sponsored by: Etnus, makers of
]
Subject: [JBoss-dev] Unified interceptors?
Any idea when this will become reality for HEAD? The spaghetti
interceptor model is making the separation of EJB bits from the server
module very hairy if not impossible.
--jason
] Behalf Of
Jason
Dillon
Sent: Thursday, March 06, 2003 2:04 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] Unified interceptors?
Any idea when this will become reality for HEAD? The spaghetti
interceptor model is making the separation of EJB bits from the server
module very hairy
Well it is still possible to separate the two w/o unified interceptors.
Not including the bits from org.jboss.cmp (this stuff is very
independent) there are about 150+ classes which are not directly
dependent on the bits from org.jboss.ejb (and related).
Some bits are forced to remain in
On Thursday, March 6, 2003, at 04:08 PM, Jason Dillon wrote:
What is left over is:
org.jboss.cmp (I am guessing this is some of the new cmp framework)
This is our new generic persistence code. Jason can you add a new
empty module 'persistence' for us and we'll move the stuff over.
