Reading xbean.xml Property Values from JDNI Resource

[terrancecrow]

Let's say I'm deploying an endpoint based on servicemix-mail, and I want to store the receiver's e-mail address in a table accessible through a JNDI resource. Let's further say that I'm running FUSE ESB 3.4.0.2 embedded under Tomcat 5.5.x under Linux.

How do I get the xbean.xml file to read the value from a specific table with a specific query?

I'm afraid this is a stupid question, but I'm at the juncture of too many things I don't know.

I think I understand conceptually how to help FUSE ESB talk JNDI, but I can't figure out where to go from here. My problem is that I'm a POJO developer who deploys a lot of servlets under Tomcat. My experience with frameworks in general is pretty weak. I'm thinking Spring gives me the tools I need, I'm just not finding instructions or examples on how to put it together.

I've searched this forum and Google, but I didn't see anything that made sense to me.

Might anyone be able to point me in the right direction? Nothing elaborate -- helping me understand the right topics to search would be very helpful at this point.

Thanks in advance!

[stlewis]

It sounds like what you want to do here (retrieve e-mails and store the incoming e-mail addresses in a DB) might be better suited to a camel route using camel-mail and then maybe camel-ibatis to write the data into the DB.  You could deploy this then as an SA in servicemix.

[terrancecrow]

Thank you very much for your reply.

I apologize, because it looks like I didn't state my question clearly.

What I need to do is retrieve an xbean.xml property value from an JNDI data source.

To use a specific example: Let's say I need to connect to an FTP server. Consider this segment from an FTP endpoint's xbean.xml file:

<ftp:sender service="replaceMe:withYourService"

              endpoint="endpoint"

              targetService="replaceMe:receiver"

              uri="ftp://servicemix:rocks@localhost/smx/test" />

I'd like to store the rocks@localhost (along with its password, which doesn't really show up in the example) in a JNDI data resource. That way, if the ID/passwords changes, I can give non technical staff a UI to simply change the value in the table, and the FTP service unit will continue to operate.

Does that make sense? Am I even looking at the problem in the right way?

Thank you again for your response.

[stlewis]

Hmmm, the closest thing I can see to your use case is to use a PropertyPlaceholderConfigurer:

This will let you at least specify these values without having to modify the xbean.xml.  At the moment though even if you change the properties file pointed to by "location" the changes won't get picked up until the SA is re-deployed, as the xbean.xml file is only consulted at deployment time.  Hope that gets you going in the right direction at least!

[stlewis]

Look at that, looks like you can use this to specify a .properties file in JNDI if it helps:  http://forum.springsource.org/showthread.php?t=14361

[terrancecrow]

Thanks for the tip on properties files -- that might be what I need. I'll try that this weekend.

Thanks again!

[terrancecrow]

I'm afraid I didn't get a chance to test this over the weekend, but I'll give it a shot as soon as I can. In the meantime, I'm going to mark the question closed, because I think the solution will work.

Thanks again for your help!