This week's giveaway is in the EJB and other Java EE Technologies forum.
We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line!
See this thread for details.
The moose likes JBoss/WildFly and the fly likes DataSource managed by JBoss VS DataSource Managed By spring Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "DataSource managed by JBoss VS DataSource Managed By spring" Watch "DataSource managed by JBoss VS DataSource Managed By spring" New topic
Author

DataSource managed by JBoss VS DataSource Managed By spring

Rohit Rai
Ranch Hand

Joined: Aug 04, 2008
Posts: 53
Hi!

currently in my application i have a datasource configured in my applicationContext.xml.

what would be the advantage if i moved this to a xxx-ds.xml and retrived the DataSource using JNDI for future use.

any significant advantages / drawbacks.

Please do share your ideas .

Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 9317
    
109

As far as i know, the applicationContext.xml is a Spring specific file. So it's Spring which is responsible for creating and managing the datasource. But if you want JBoss to create the datasource and manage it, then *-ds.xml files are the only option.

Haven't used Spring, so I don't know what advantages you might see when using Spring datasources instead of JBoss'


[My Blog] [JavaRanch Journal]
Rohit Rai
Ranch Hand

Joined: Aug 04, 2008
Posts: 53
Yes you are right i am using spring in my application and spring uses the datasource configured in applicationContext.xml
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: DataSource managed by JBoss VS DataSource Managed By spring
 
Similar Threads
Isolation Level
WLS 7 Experience?
javax.naming.NameNotFoundException: XAConnectionFactory not bound
Datasource JNDI Lookup in WSAD from standalone app
resource ref needs to be setup