2:16 p.m.
Create https://issues.jboss.org/browse/AS7-5125 for 1)
On 07/05/2012 04:02 PM, Jaikiran Pai wrote:
There are 2 issues here:
1) The expression value validation isn't allowing empty values. So
internally it results in:
org.jboss.as.controller.OperationFailedException [ "JBAS014704: '' is
an invalid value for parameter default-distinct-name. Values must have
a minimum length of 1 characters" ]
2) This real exception isn't reported during server startup and I
don't know the reason why.
Please create separate JIRAs for this. I believe a fix for #1 would
involve overriding the String type attribute validator with an custom
validator which allows empty strings (since for default-distinct-name
a empty string is a valid value).
-Jaikiran
On Thursday 05 July 2012 11:46 AM, Wolf-Dieter Fink wrote:
> No,
> If I configure the EJB subsystem with a correct distinct-default
> everything works (see initial mail, "If I set property to XX...")
>
> My intention was to set the default-distinct name with an expression
> and use the default "",
> so it it possible to use the same profile for different server-groups
> and configure the distinct name with a property.
>
> This works as long as I have a default different from "" or overwrite
> with a property different from "".
> But if I don't want the distinct name and set "", no difference
> whether default or property, a execution with "no distinct name" will
> not work.
>
> I've looked into the source and play around with expressions and
> properties and it looks like that ${XY:} will set "" as I want and a
> property with value="" works either.
> So I don't understand at the moment why this don't work for distinct
> name !?
>
> - Wolf
>
> On 07/05/2012 07:34 AM, Jaikiran Pai wrote:
>> Sorry, I don't completely understand the issue. Are you saying that
>> whatever distinct name you specify in the EJB3 subsystem is not being
>> used by the deployed EJBs?
>>
>> -Jaikiran
>> On Wednesday 04 July 2012 07:59 PM, Wolf-Dieter Fink wrote:
>>> I want to set
>>> <default-distinct-name value="${server.distinct.name:}"/>
<!--
>>> default to "" empty -->
>>> for the ejb3 subsystem.
>>>
>>> If I look into the sources for ModelNode this should work, also do a
>>> simple mail-class test ;)
>>>
>>> Also if I set later in the server-group
>>> <system-properties><property name="server.distinct.name"
value=""/>
>>>
>>> The result is the same:
>>> EJBCLIENT000025: No EJB receiver available for handling
>>> [appName:apptwo,
>>> moduleName:ejb, distinctName:]
>>>
>>> If I set property to "XX" or default-distinct-name to
>>> "${server.distinct.name:XX}" (and don't set property)
>>> everything works fine.
>>>
>>> I suppose that there is something wrong with the setting for the
>>> receiver, but I don't see anything in TRACE level that give me an
>>> idea.
>>>
>>> Does anybody can help?
>>>
>>> - Wolf
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>