changing conn parameters in -ds.xml file !!!urgent!!!

[sankul123]

I have tried to explain using these two cases -
ora-ds.xml -> oracle ds xml file.
CASE 1:
If I place the ora-ds.xml file under ${JBOSSHOME}/server/default i,e

${JBOSSHOME}/server/default
|
|------- myApp.ear
|
|-------ora-ds.xml
|

and I update the ora-ds.xml file manually with new connection params to the same JNDI name, I can see the following in log file -
[06/19/08 12:08:49,879 PM] [ConnectionFactoryBindingService] [INFO] [Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=OracleDS' from JNDI name 'java:OracleDS']
[06/19/08 12:08:49,957 PM] [ConnectionFactoryBindingService] [INFO] [Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=OracleDS' to JNDI name 'java:OracleDS']
This gives me confirmation that connection obj is according to changed conn parameters.

CASE 2:
I am trying to achieve the above thing through a program and just move the ora-ds.xml inside the ear[few of the customers are not interested giving our program any permissions[java security perm] outside our context].
So now I have placed the ora-ds.xml file inside ear and specify the path in jboss-app.xml file.

myApp.ear
|
|-----META-INF
| |
| |-jboss-app.xml [ <module><service>ora-ds.xml</service></module>]
| |
| |
|
|------- web1.war
|
|------- web2.war
|
|
|-------ora-ds.xml
|
|

And I am updating the ora-ds.xml file from my program. Even after updating I still get old conn object if I make a JNDI call.
I dont see any events as mentioned in case 1 , when I update the ora-ds.xml file in second case.

Bottom Line :

I want to update the connection parameters in ora-ds.xml and get new conn obj accordingly

Please answer whether what I am trying to do is either possible or NOT possible

Sandeep

[vickyk]

"sankul123" wrote:
Even after updating I still get old conn object if I make a JNDI call.
I dont see any events as mentioned in case 1 , when I update the ora-ds.xml file in second case.

You should be redeploying the EAR to see the changes in -ds.xml , modify the EAR/META-INF/app.xml after you make changes in the -ds.xml that will lead to the hot deployment of EAR .

[sankul123]

"vickyk" wrote:


You should be redeploying the EAR to see the changes in -ds.xml , modify the EAR/META-INF/app.xml after you make changes in the -ds.xml that will lead to the hot deployment of EAR .

Thank you Vicky , for the reply.
Just to add to my question, changing conn parameters is exposed as a feature. So for end user the operation should after performing the operation , he should either a success or failure I mean to say , he should not get either a 404 or any exception as appl is redeploying.

Is there any JBoss JCA API to achieve through code, we have a seperate a package for all container related operations , so I am free to use any JBoss API's there. Please let me know if there are any such Jboss API's to refresh the conn obj registered with JNDI name.

Sandeep

[vickyk]

"sankul123" wrote:

Is there any JBoss JCA API to achieve through code,

The JMX should do the trick for you .
Try to use the following JCA related MBean .

./twiddle.sh invoke "jboss.jca:name=DefaultDS,service=ManagedConnectionFactory" getManagedConnectionFactoryAttribute connectionURL

You should be able to set the properties through setManagedConnectionFactoryAttribute() and get it though the getManagedConnectionFactoryAttribute operation of the JCA Mbean.

[vickyk]

!!!urgent!!!
When you want these things to get addressed you MUST go for Jboss support .

[sankul123]

"vickyk" wrote:
!!!urgent!!!
When you want these things to get addressed you MUST go for Jboss support .

do they charge for developer support?

Let me try JMX , thank you for your help.

[vickyk]

"sankul123" wrote:
do they charge for developer support?

Yes , read this
https://www.redhat.com/security/updates/jboss_notes/