On Jan 8, 2008, at 8:26 PM, Andreas Fischer wrote: > 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.
I've just added a bug report for this. The <authenticator> isn't webbeans-aware at the moment. By the way, the unit could be in resin/lib (or resin/ext), not ext- webapps. The only purpose of ext-webapps is to support those libraries that aren't classloader-aware, i.e. that can only work in a single web-app at one time. -- Scott > > 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. > > > _______________________________________________ > resin-interest mailing list > [email protected] > http://maillist.caucho.com/mailman/listinfo/resin-interest _______________________________________________ resin-interest mailing list [email protected] http://maillist.caucho.com/mailman/listinfo/resin-interest
