I'm not really worried about keeping the dependency isolated. I think the deployment descriptor mechanism is much nicer for getting a reference to services like CMS than JNDI ever will be. I will redo my descriptor to jboss-portlet.xml and remove my portlet-instances.xml file. In hindsight - jboss-portlet.xml makes more sense for this dependency injection as it is very unlikely that a dependency for a service would exist for a particular instance of a portlet but not universally for that portlet's class.
The interceptor sounds very cool! I like this aspect based stuff - it saves me from writing the same code in a hundred places to do something like you are describing (which I may actually need for some of the ideas I have for Portal). I guess that's why the smart guys came up with it. :) Thank you for a very cool set of tech in Portal and Seam - I think it has big potential. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3943191#3943191 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3943191 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
