From: Bill B. <bi...@jb...> - 2005-11-23 22:40:34
|
I think I see where you are going Scott, but I'm not sure yet this can work generically. You want a component that can generically setup the ENC for a servlet, EJB, etc... The problem is that population of the ENC is a conglomeration of XML metadata and annotations. Another wrench is that Interceptors are a different class, yet they belong to the same ENC as the EJB and also have their own XML metadata. Personally, I'd rather have us iterate EJB and then WEB and then find the patterns of reuse. This would allow us to get working prototypes of EJB3 and WEB for Java EE 5 without writing some generic service that may/may not be used. Scott M Stark wrote: > I mean its an aspect that is triggered as part of the create phase of > the lifecycle to configure the enc component based on the bean metadata. > Today all containers are explicitly handing this task even though its > exactly the same. If it were properly factored out this should be > pluggable into each container type with the only difference being the > target of the ENC injection. > >>>- The ENC "pattern" bean associated with the container components. As we >>>have talked about, this varies depending on the container. What varies >>>is the association to the container components. EJB style containers >>>have an ENC per bean, WAR style containers have an ENC per deployment. >>>This would seem to be a lifecycle visitor aspect that associates the ENC >>> >>> >> >>Don't understand this comment? >>What does it mean to visit a lifecycle? :-) >> >> > > ------------------------------------------------------- This SF.net > email is sponsored by: Splunk Inc. Do you grep through log files for > problems? Stop! Download the new AJAX search engine that makes searching > your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ JBoss-Development > mailing list JBo...@li... > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Inc. |