[EMAIL PROTECTED] wrote:
Having the dependency information will make things work a lot more
smoothly for us, we will still not be able to use service beans
without at least deploytime dependency injection. We will have to
continue to kludge around these holes in the near future but one day
5.0 will fix all of our problems (and hopefully brew a find cup of
java)...
Again, service beans should support XML injection of <ejb-ref>
<env-entry>, etc... from XML in jboss.xml
I guess that could work....its extremely undesireable, but technically
feasible. It would be rather unpleasent to look up ever independent
attribute as a seperate JNDI lookup and forcibly inject it. For the
moment dealing with the drawbacks of XMBeans and the integration issues
is less unpleasant.
EJB 3.0 spec supports injection through XML via the <injection-target>
element. Service beans *should* support this, if not I'm going to
bitchslap BillD.
Bill
-------------------------------------------------------
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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
