|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2304 | minor | always | 01-09-08 08:52 | 01-10-08 14:01 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.1.4 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.5 | ||
|
|
|||||
| Summary: | 0002304: Authenticator needs to be webbeans-aware | ||||
| Description: |
(rep by Andreas Fischer) I try to write an Authenticator that uses a persistence unit that stores users identities. The unit is stored in ext-webapps so multiple applications can use it. If I try to use annotations only null is passed as the persistence manager. If I try to look either the persistence context up in the authenticator over JNDI I get a name not found. Even if I try to delay the actual lookup until loginImpl is called the Unit / Context can still not be found. Looking up the same context in an example servlet works over annotations. It shouldn't be such an uncommon case for an authenticator to access infomration from a persistence context? I mean it is easy to work arround the problem by using SQL queries but using the persistence unit approach would make things easier. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||