-
1. Re: Browser-based configuration editor
kurtstam Mar 2, 2007 2:53 PM (in response to derek.adams)Thanks looks very nice Derek :). I think it makes a great addition. Please open a jira and it'd be great if you could attach the code there.
Thank very much :).
--Kurt -
2. Re: Browser-based configuration editor
dmarchant Mar 2, 2007 3:23 PM (in response to derek.adams)I second that.
That would be nice to have. -
3. Re: Browser-based configuration editor
derek.adams Mar 2, 2007 3:33 PM (in response to derek.adams)Ok. I posted a JIRA issue for it. Installing it should be as easy as dropping the war in your deploy directory and the action-templates.xml in your conf directory. When the server starts, navigate to http://localhost:8080/esbconfig/ESBConfigEditor.swf and your current config should appear in the editor. I uploaded a PDF user guide as well.
Here is the JIRA link http://jira.jboss.com/jira/browse/JBESB-449 that has the files.
Let me know what you think!
Derek -
4. Re: Browser-based configuration editor
kurtstam Mar 2, 2007 3:43 PM (in response to derek.adams)Just looked at the guide and the code. Very nice. Sorry for my ignorance wrt flash, but what tool do I use to edit the swf file. I'm assuming that's where most of the GUI 'code' lives?
Thanks,
--Kurt -
5. Re: Browser-based configuration editor
derek.adams Mar 2, 2007 3:54 PM (in response to derek.adams)I will add an attachment to the JIRA issue with the Flex2 source code for the editor. The tool I used for development was Flex Builder 2 (free-trial, based on Eclipse), but you can download the Flex2 SDK (command-line compiler) for free via a link off this page... http://www.adobe.com/products/flex/.
Hope that helps,
Derek -
6. Re: Browser-based configuration editor
daniel.brum Mar 2, 2007 4:38 PM (in response to derek.adams)I just tested the tool, deployed several QuickStarts. Very nice work.
is the Adobe toolkit capable of running say in a linux based browser? -
7. Re: Browser-based configuration editor
kurtstam Mar 2, 2007 4:43 PM (in response to derek.adams)Yep that sure helps Derek. Thanks again, this is a very nice addition!
--Kurt -
8. Re: Browser-based configuration editor
derek.adams Mar 2, 2007 4:55 PM (in response to derek.adams)"daniel.brum@jboss.com" wrote:
is the Adobe toolkit capable of running say in a linux based browser?
Yep. We have people in the office running Flex2 apps on Windows/IE, Linux/Firefox, and even.. dare I say it.. a Mac ;) ... all you need is the latest Flash plugin for your platform. -
9. Re: Browser-based configuration editor
marklittle Mar 2, 2007 6:15 PM (in response to derek.adams)Hi Derek. Thanks for the tools and please give us input on anything else you'd like to see added. BTW, don't be shy about the Mac: all of the best s/w is developed on it ;-)
-
10. Re: Browser-based configuration editor
marklittle Mar 6, 2007 8:49 AM (in response to derek.adams)Derek, we'll ship this in the next release of JBossESB, which is due in a few weeks. Thanks again for the donation!
-
11. Re: Browser-based configuration editor
marklittle Mar 14, 2007 9:28 AM (in response to derek.adams)Derek, could you take a look at updating the configuration editor in the next few days http://jira.jboss.com/jira/browse/JBESB-464?
-
12. Re: Browser-based configuration editor
derek.adams Mar 14, 2007 11:07 AM (in response to derek.adams)Making the JNDI URL optional on the JMS provider should be a quick change. Is that all we need for this release?
-
13. Re: Browser-based configuration editor
kurtstam Mar 14, 2007 11:14 AM (in response to derek.adams)Hi Derek,
If we go by this list:
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310150&fixfor=12311102
Then I think that is all.
Thx,
--Kurt -
14. Re: Browser-based configuration editor
kurtstam Mar 14, 2007 11:17 AM (in response to derek.adams)Oh before i forget. We are moving the jbossesb.xml out of the conf directory and into a '.esb' archive, packaged up with any custom code that goes with that config file.
You will be able to deploy multiple of these archives siultanously. This will have an impact on the editor too I think?