It's a bug. It should actually look like:
"timeout-unit" => {
"description" => "The instance acquisition timeout
unit",
"type" => STRING,
"required" => false,
"default" => "MINUTES",
"allowed" => [
"HOURS",
"MINUTES",
"SECONDS",
"MILLISECONDS"
],
"access-type" => "read-only",
"storage" => "configuration"
}
I'll send a pull request with the fix.
-Jaikiran
On Wednesday 21 September 2011 04:02 PM, Jaikiran Pai wrote:
The model for EJB3 does allow more than one timeout unit type
(SECONDS,
MINUTES and MILLISECONDS etc...). So that output doesn't look right. Let
me take a look why.
-Jaikiran
On Wednesday 21 September 2011 03:53 PM, David Bosschaert wrote:
> Hi all,
>
> I'm looking at the EJB3 pools timeout-unit description, which is the
> following:
> "timeout-unit" => {
> "description" => "The instance acquisition timeout
unit",
> "type" => STRING,
> "required" => false,
> "default" => "MINUTES",
> "allowed" => "MILLISECONDS",
> "access-type" => "read-only",
> "storage" => "configuration"
> }
>
> Is there an example of an attribute somewhere where 'allowed' has more
> than 1 value? I'd like to test a console gui piece against it.
>
> Thanks,
>
> David
> _______________________________________________
> 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