-
1. Re: Configuration storage
timfox Mar 22, 2010 6:50 PM (in response to clebert.suconic)The only requirements I know of are persisting JMS queues and topics, where did these other requirements come from?
Andy- I would like to see your input here, as these requirements come from the console work.
-
2. Re: Configuration storage
clebert.suconic Mar 22, 2010 6:53 PM (in response to timfox)As far as I know, we should be able to persist security settings, connection factories and address settings as well.
-
3. Re: Configuration storage
clebert.suconic Mar 22, 2010 6:54 PM (in response to timfox)> where did these other requirements come from?
The console admin is for instance managing connection factories. They should be persisted for example.
Anything done through the admin console should be persisted. We may decide to cut some of the persistence now.. but that means.. we will have to do it later.
-
4. Re: Configuration storage
timfox Mar 22, 2010 6:55 PM (in response to clebert.suconic)It's all very well saying that you think that we should persist X, Y and Z.
But without providing any reasoning as to why you think that, your statement is really rather pointless.
I may as well say "I like cheese". Well, thanks for that.
-
5. Re: Configuration storage
timfox Mar 22, 2010 6:57 PM (in response to clebert.suconic)Clebert Suconic wrote:
> where did these other requirements come from?
The console admin is for instance managing connection factories. They should be persisted for example.
Anything done through the admin console should be persisted. We may decide to cut some of the persistence now.. but that means.. we will have to do it later.
Well, that's not what I have been told on the latest updates.
If it's changed, it needs to be discussed. Right now I am working on the basis it's just JMS queues and topics.
-
6. Re: Configuration storage
clebert.suconic Mar 22, 2010 7:07 PM (in response to timfox)If you look at the attachments on Andy's message:
http://community.jboss.org/message/532433#532433
He's managing address settings & security settings.
I could just do it alltogether around Queue names, but I don't think that's the proper way of doing it.
I know for instance we need to persist Connection Factories. If I provide a generic way now, it could be easily reused later, while the development time would be the same here.
-
7. Re: Configuration storage
leosbitto Mar 22, 2010 7:09 PM (in response to timfox)As an aministrator, I would be significantly diappointed if I would lose anything which I would configure through the administration console! Every other JMS provider I have approached offers the possibility to persist the online configuration changes, which I consider to be an essential feature (still missing in HornetQ, sadly though).
-
8. Re: Configuration storage
timfox Mar 22, 2010 7:14 PM (in response to leosbitto)Can you be more specific about what is "missing" ?
-
9. Re: Configuration storage
leosbitto Mar 22, 2010 7:25 PM (in response to timfox)I miss the possibility to persist all the configuration changes made through any online configuration interfaces (like the JMX console in 2.0.0.GA for example) to get the consistent behaviour after the restart.
-
10. Re: Configuration storage
timfox Mar 23, 2010 3:38 AM (in response to leosbitto)I'm looking for a specific list of what is missing.
-
11. Re: Configuration storage
timfox Mar 23, 2010 3:50 AM (in response to clebert.suconic)Clebert Suconic wrote:
If you look at the attachments on Andy's message:
http://community.jboss.org/message/532433#532433
He's managing address settings & security settings.
I could just do it alltogether around Queue names, but I don't think that's the proper way of doing it.
I know for instance we need to persist Connection Factories. If I provide a generic way now, it could be easily reused later, while the development time would be the same here.
I expected it to be done by the end of yesterday. This should be a two hour copy and paste job. Maybe quicker for you since you are familiar with the journal.
Looks like all we got after one day is an email outlining how to do this
-
12. Re: Configuration storage
ataylor Mar 23, 2010 5:07 AM (in response to timfox)We need to persist the following:
JMS Queue
JMS Topic
JMS COnnection Factories
However since the user must be able to configure things on the destinations we need to persist Address Settings and Security Settings as well so on restart the queues are configured the same.
Have a look at the attached screen shot of configuring a new Queue Resource via the admin console and you will see.
-
13. Re: Configuration storage
timfox Mar 23, 2010 6:30 AM (in response to ataylor)Address settings and security settings go in core, not the jms server.
Also, I'd like to understand how this works together with xml config.
What takes precedence? Xml or store? Can they work together? If so, how?
-
14. Re: Configuration storage
ataylor Mar 23, 2010 7:32 AM (in response to timfox)This was discussed at the F2F and agreed on by every one, when the user creates a new destination they should be able to configure settings and security at the point the queue is created. Exactly like the screen shot shows.
Persistence ill take priority over xml config.
fyi, the admin console will only have JMS objects for this version.