On Wed, Oct 10, 2012 at 7:51 PM, Marina Vatkina
<marina.vatkina_at_oracle.com>wrote:
> See http://docs.oracle.com/cd/**E26576_01/doc.312/e24930/jdbc.**htm#gavro<http://docs.oracle.com/cd/E26576_01/doc.312/e24930/jdbc.htm#gavro>and
> http://docs.oracle.com/cd/**E26576_01/doc.312/e24930/**
> transaction-service.htm#beamu<http://docs.oracle.com/cd/E26576_01/doc.312/e24930/transaction-service.htm#beamu>
>
> To support API based access those 2 options are created in the background
> automagically.
>
Oh, interesting. (And, have to say, weird.) So it would appear that by
default when you use the web console the allow-non-component-callers option
is set to true, whereas if you just do asadmin deploy this is set to false.
Is that by design?
Here's another odd curveball for you: if I told you that a mistake was made
:-) and a jdbc/cx resource was never created on the GlassFish in question,
but a jdbc/cx__pm etc. still showed up, what would that mean? How would
that come about?
Best,
Laird
--
http://about.me/lairdnelson