[ https://jira.jboss.org/jira/browse/JBIDE-6078?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-6078: --------------------------------------- Affects Version/s: LATER Hi Tom, Thanks for your input! Sorry for my ignorance about blacktie but are you simply asking for a structured editor for the xml files ? About the generation - how do we know what to generate ? Got any existing tools (or even documentation?) we can utilize ? Note, putting this on LATER since we don't currently have expertise on this project - contributors very welcome :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-6078?page=com.atlassian.jira.plu... ] Tom Jenkinson commented on JBIDE-6078: -------------------------------------- Hi Max, Thanks for getting back to me! And the LATER setting isn't a problem! Hopefully we could try to contribute something back as well. NOTE: Blacktie clients and services are typically written in C In terms of the XML, what I was thinking is basically we have several actors in an application: Domain -> Machines -> Servers -> Machines-Refs -> Services -> Clients I was thinking a GUI could show the entities (file -> new domain, right click on the domain, add server type thing, right click on the server, add service), then some of the output would be XML, i.e. the user would not need to edit XML but would receive XML as an output. When a user creates a new server in the gui, they should be able to specify whether the services for that server are coded in C or Java or both (this value is then of assistance when creating template services below). Also, only one Java server is allowed to be defined per domain. When a user creates a new service in the gui they can either ask us to output a simple template or they can specify the path to the source to use.. We do currently have tools for the generation of C actors (parameterized ant script), it was about putting them in the gui to make it easier for users to "not go wrong". The output from the tool would be a domain on disk (not compiled) and would consist of: domainName/ serverName/ build.xml (simple build file to build the server as configured) btconfig.xml (contains machine config - determined from gui) log4cxx.properties (always the same) TemplateServiceFOO.c (optional if the user asked us to create a template service.c file for them) [more TemplateServiceX.c) [more serverName] client/ btconfig.xml Thanks for any input/guidance you can offer even if it is to say this doesn't sound like a good fit for JBIDE! Tom -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6078?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-6078: --------------------------------------- Labels: integration (was: blacktie) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira