Two Laptop Bag*
The moose likes EJB and other Java EE Technologies and the fly likes Configuring Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Configuring "provider-url" in message driven bean descriptor" Watch "Configuring "provider-url" in message driven bean descriptor" New topic
Author

Configuring "provider-url" in message driven bean descriptor

mohamed zafer
Ranch Hand

Joined: Nov 03, 2000
Posts: 62
Hi There,
I have a Message driven bean deployed in the Weblogic 7.0 which subscribes to a topic from another Welbogic server. My deployment descriptor looks like this
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>MetricsFeedbackListener</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>jms.SampleTopic</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<provider-url>t3://172.0.34.02:7001</provider-url>
<connection-factory-jndi-name>javax.jms.TopicConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
IS there a way to have the <provider-url> configurable, I mean passing as a system property etc., instead of hardcoding here. The reason being I have to manually change each time , I move the build from DEV to SIT ,PROD environements.
Zafer
Maulin Vasavada
Ranch Hand

Joined: Nov 04, 2001
Posts: 1871
Hi
I guess if you use Service Locator pattern you would have only one place to change when you deploy on other environment..
See if you can use that..
Regards
Maulin
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Configuring "provider-url" in message driven bean descriptor
 
Similar Threads
Message Driven Bean security problems
Problem integrating Weblogic 8.1 with Sonic MQ 6.1
Issue with MDB and weblogic 9.2
mdb deploy problem
JMS subscription problem