Bug #205 (closed)
Passivation throws an exception in JBoss
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | trivial | Cc: | sfrank, jburel, cxallan |
Sprint: | n.a. | ||
Total Remaining Time: | n.a. |
Change History (2)
comment:1 Changed 18 years ago by jmoore
- Cc jburel callan added
- Keywords changed from jboss, configuration to jboss, configuration, iteration2
- Milestone changed from Unscheduled to 3.0-M3
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 18 years ago by jmoore
Forgot to mention -- that was done in r825.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Not sure anymore if the exception was harmless, but it's fixed. JBoss4's EJB3 configuration still ignores some configuration files in its pre-productization stage. Moved from configuring NoPassiviationCache in jboss.xml to doing so in the bean itself. Similarly, moved the configuration for @ApplicationException from ejb-jar.xml to the ome.conditions package. This latter change may break unit tests that are expecting EJBExceptions but exception handling should now finally be accurate.