"rauschuber" wrote : I agree with producing something useful yet with as few cool features as possible in the first go-round. Versioning will be very useful, but it doesn't have to be in the product for it to work.
Right. I think commit/rollback should be sufficient. Thinking more on where the "cached configuration" should live, may be it makes more sense to give the Admin Console its own persistent store. I think this would be invaluable when dealing with a multi-node setup. You don't want to have to go to each node in the cluster to retrieve cached configuration information. Much better to keep it close to the Admin Console and then push the changes out to each node on commit. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862937#3862937 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862937 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
