[jboss-as7-dev] Configuration conundrum with Express

[Max Rydahl Andersen]

>> 
>> Since just exposing this doesn't really help since users would then have to remember to invoke these operations always from whatever tool they use, wether that is command line, forge, eclipse, netbeans, maven etc.
>> 
>> I hope its done with something that doesn't requires N implementations - but something like the suggested feature of being able to deploy management changes.
> 
> AS7 doesn't allow this generally, right? So why would it be different on express?

I don't want Express to be different, I want both AS7 locally, on remote hosts and on express to be easy to configure/setup without relying on a running server or that your tool has access to do the right management calls at the right times.

i.e. before we could copy a .war and a -ds.xml and it would work/deploy from any tech.

Now we need to have forge, cli, jboss tools, netbeans, eclipse, intellij, my eclipse etc. be aware of AS7 management model and not only be able to tell the server to set something up, but also be able to handle the possible error conditions (i.e. datasource is already there, operation not permitted etc.) to do an outofbox deployment without too much fuzz.

/max

> 
>> 
>> /max
>> 
>>> 
>>> On 28 Sep 2011, at 09:14, Benjamin Browning wrote:
>>> 
>>>> 
>>>> On Sep 28, 2011, at 12:13 PM, David M. Lloyd wrote:
>>>> 
>>>>> On 09/28/2011 10:43 AM, Pete Muir wrote:
>>>>>> Warning, I may be repeating an existing query, so tell me politely where to go if that is the case ;-)
>>>>>> 
>>>>>> I've been adding Express support to Forge, in the run up to doing demos at JavaOne. I've hit the point where I want to add an entry (an Infinispan cache) to the standalone.xml (or domain.xml), and I want to do it without having to write a parser. If the node is available via the mgmt interface this is easy - I can use the REST interface etc. However, my node isn't, and the recommended way to configure it is to edit .openshift/configuration/standalone.xml.
>>>>>> 
>>>>>> Any thoughts on how I can make use of the management capabilities of AS to define this (in a machine controllable way without me reinventing the wheel) for OpenShift Express?
>>>>> 
>>>>> If there is something that is in standalone.xml that can't be affected 
>>>>> with management operations, I'd say we have a bug.  You should be able 
>>>>> to get at any configuration item at runtime.
>>>> 
>>>> I believe the issue is no management interfaces are enabled in Express. Your only interface is standalone.xml.
>>>> 
>>>> Ben
>>>> 
>>>> 
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>> 
>>> 
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> 
>> 
> 

/max
http://about.me/maxandersen