-
1. Re: Address Setting issue on deployement packages
ataylor Feb 2, 2010 12:06 PM (in response to clebert.suconic)I think the altrenative, that you suggested, was to associate address settings with a queue, similar to how JBM 1.4 is used. I think this is wrong, firstly we should only have a different way to deploy stuff in the AS than in Standalone. secondly, these settings are on an address not a queue. adding it to queue will only confuse users more.
I think most users will just use default settings anyway.
-
2. Re: Address Setting issue on deployement packages
clebert.suconic Feb 2, 2010 12:07 PM (in response to clebert.suconic)To avoid this, I wouldn't let users to deploy queues.xml on the MDB jar.
And I would add an queue-seeting and security setting on the JMS element, such as:
<queue name="exampleQueue"> <entry name="/queue/exampleQueue"/> <security> ...blablablabla... </security> <settings> <page-max-size/> <whatever-else-is-needed-here/> </settings> </queue>
This way the user would be locked with his settings and his queues.
At the implementation those settings would be applied towards the address of the JMS queue (or topic)
-
3. Re: Address Setting issue on deployement packages
clebert.suconic Feb 2, 2010 12:09 PM (in response to ataylor)My concern is, the user has the power to do something hard to catch.
Murphy says it will eventually happen.
I'm just raising my concern. If everybody thinks this is not an issue (as long as you guys understand what I'm raising here), I will just accept it.
-
4. Re: Address Setting issue on deployement packages
ataylor Feb 2, 2010 12:12 PM (in response to clebert.suconic)My main issue are
1.) it implies that the settings are associated with queues which will only confuse users.
2.) it is different to how we deploy standalone.
-
5. Re: Address Setting issue on deployement packages
clebert.suconic Feb 2, 2010 12:17 PM (in response to ataylor)1) We would do it only to JMS Users. If users want to deploy a generic config they should do it on the main config file, not individually on JARs messing with other applications.
2) we would also let standalone users to deploy JMS destinations this way if we get into an agreement.
-
6. Re: Address Setting issue on deployement packages
timfox Feb 2, 2010 4:19 PM (in response to clebert.suconic)We shouldn't have any different config in JBoss AS compared to standalone.
Let's keep this simple, address settings is fine
-
7. Re: Address Setting issue on deployement packages
clebert.suconic Feb 2, 2010 4:41 PM (in response to timfox)I don't want to create a different way for JBAS. I would change the jms-queue on both standalone and application server.
I'm raising an issue with multiple applications messing up with address-settings, and I don't think the user should be able to mess with that.
If you don't think that's an issue, fine... I don't like it but I will accept it.