Scott Stark [http://community.jboss.org/people/starksm64] created the discussion "Re: Best practices for openshift express and tools" To view the discussion, visit: http://community.jboss.org/message/628395#628395 -------------------------------------------------------------- Where do I setup the server adapter? I see the jboss tools runtime detection, but don't really find the as7 server adapter or settings your talking about. There are a number of issues that I'm facing that we should try to make easier. 1. I can easily run all 5 wars in the same local runtime each with unique localhost based urls using the context-root resulting from the war deployment name. These are mapped to 5 different express applications and need to have an updated jboss-web.xml that specified a / context-root since each application already has a unique dns name, for example, http://localhost:8080/idp http://localhost:8080/idp deployes to http://idp-sstark.dev.rhcloud.com/ http://idp-sstark.dev.rhcloud.com/ Now I can certainly just use the same default context root of idp so that the url for the express app is http://idp-sstark.dev.rhcloud.com/idp/ http://idp-sstark.dev.rhcloud.com/idp/, but I'm looking into things users would want to do with a local vs paas deployment of their application. Currently I achieve this by exporting the war to the express app deployments directory, and then run an ant fixup script that overwrites the ipd.war/WEB-INF/jboss-web.xml with another that overrides the context-root. I know I mentioned the need to have an exported context-root differ from what is deployed locally in another thread. If in the M4 there could be a setting that allowed one to specifiy an alternate jboss-web.xml (like the jboss-web-express.xml I use), that would overwrite the current WEB-INF/jboss-web.xml whent the war is exported, that would be helpful. 2. The application I'm working on have references to each other, and as such, have pages/configuration that reference either a property or a default localhost based url. For example: <PicketLinkSP xmlns="urn:picketlink:identity-federation:config:1.0" ServerEnvironment="tomcat"> <IdentityURL>${idp.url:: http://localhost:8080/idp/ http://localhost:8080/idp/}</IdentityURL> <ServiceURL>${employee.url:: http://localhost:8080/employee/ http://localhost:8080/employee/}</ServiceURL> </PicketLinkSP> Now I set the idp.url and employee.url settings in the express app .openshift/conf/standalone.xml server configuration file. It would be nice if there was a dual notion for the jboss as7 server runtime that allowed you to edit a local vs paas view. Right now there is an XML Configuration section under the server with just a Ports section. If there were Local and PaaS sections where two standalone.xml configuration could be managed that would be helpful. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/628395#628395] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Scott Stark [http://community.jboss.org/people/starksm64] created the discussion "Re: Best practices for openshift express and tools" To view the discussion, visit: http://community.jboss.org/message/628640#628640 -------------------------------------------------------------- Yes, I do think we have to change what gets exposed to the user to a series of admin commands that get played against the server to setup the the deployment and other PaaS vs local settings. The admin configuration file is not really the best thing. I'll start looking into this more seriously after JavaOne. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/628640#628640] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] created the discussion "Re: Best practices for openshift express and tools" To view the discussion, visit: http://community.jboss.org/message/628734#628734 -------------------------------------------------------------- btw. in the current state of things the best thing would be if when the pom.xml is being used on openshift side that could be detected somehow and used as a way to enable the proper profile in which you can do the proper "deployment dependent" switches. This doesn't solve the problem of direct binary deployment from eclipse tooling, but its the best scalable approach I can forsee right now. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/628734#628734] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] created the discussion "Re: Best practices for openshift express and tools" To view the discussion, visit: http://community.jboss.org/message/629248#629248 -------------------------------------------------------------- Scott, could you open a feature/bug on this in https://jira.jboss.org/jira/browse/JBIDE https://jira.jboss.org/jira/browse/JBIDE p.s. the xml configuration elements aren't really solid stuff anymore - was considering removing it for AS7 stuff... -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/629248#629248] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Scott Stark [http://community.jboss.org/people/starksm64] created the discussion "Re: Best practices for openshift express and tools" To view the discussion, visit: http://community.jboss.org/message/629375#629375 -------------------------------------------------------------- The xml configuration does not appear to be working even with the workaround, and it really is not what we want to expose going forward anyway. I'll create a feature request to support a "CLI Batch" file that contains a collection of admin commands that will be run through the cli interface. There will need to be a remote/local notion to support the openshift case of having this file be in the application git repo and applied when pushed vs applied to a local server by invoking the cli tool. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/629375#629375] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] created the discussion "Re: Best practices for openshift express and tools" To view the discussion, visit: http://community.jboss.org/message/629386#629386 -------------------------------------------------------------- okey! sounds good. p.s. jbosstools-dev mailing list is where more dev people are listening. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/629386#629386] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]