Hi!
Jon Finanger wrote:
> This issue have bothered me a while (in fact it held me away from using ejb
> for a while).
> Since my projects always involves some hardware communication i would have
> been glad if it was possible to nicely interface these beasts in the EJB
> app.server (not only the database). As i understand it, and whats stated in
> a FAQ entry, (http://www.jguru.com/jguru/faq/view.jsp?EID=2990), i may get
> trouble doing this.
>
> Any additional comments or experience on this issue?
Create an accessor object and bind it in the global JNDI namespace. Best
solution AFAIK.
Basically:
1. Create your Java objects for accessing the HW
2. Create some object that can be used to access your code
3. Create an MBean to administer this in the server
4. Let the MBean register your accessor object in JNDI
5. Let your beans lookup and use your stuff from JNDI:
MyHW hwAccessor = (MyHW)new InitalContext().lookup("myHwAccessor");
Should work well and be pretty portable.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
