A while back I suggested that create=true be the default for @In. Gavin didn't think that would be very safe -- after further use I'd have to agree. create=false makes sense as the @In default.
However, I can't get around the fact that in my use there are several component beans that are just "made to exist". It doesn't make sense that they don't exist. So I'm always having to specify create=true when they are injected which seems odd. I'd like to suggest making a new optional parameter to @Name that allows the component itself to specify its *default* injection creation behavior. So if "create" is not specified in the @In value, Seam will default to whatever is specified in this optional @Name parameter. Seems like the best of both worlds to me.. :) Ryan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910452#3910452 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910452 ------------------------------------------------------- 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-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
