|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2648 | minor | always | 05-05-08 06:50 | 05-08-08 11:31 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.7 | ||
|
|
|||||
| Summary: | 0002648: hibernate/webbeans init order | ||||
| Description: |
(rep by wesley) I've set logging to "finer" and found datasource being initialized after AmberContainer parsing persistence.xml. After some tracing, I think the issue is also an order problem. After resin server initialized, it began to init the webapp, at the order below: 1. Look at persistence.xml and try to init an AmberContainer. 2. Parse resin-web.xml to init DataSource, JCA connectors, EJBs and Singletons. Note, at the first step method getJtaDataSource() of com.caucho.amber.cfg.PersistenceUnitConfig will be called. It tried to find a DataSource in JNDI and failed, because a DataSource will be available in JNDI until the 2nd step finished. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||