We have developed a pooling scheme that is a kind of hybrid between the
SharedLocalTransactionCM and the
XAConnectionManager ...
Without tx context (read usage), the pool dispenses for each separate
allocation request a different XA-enabled connection.
Within a single tx context (read&write u
-Ursprüngliche Nachricht-
>Von: marc fleury [mailto:[EMAIL PROTECTED]]
>Gesendet: Sonntag, 5. August 2001 18:55
>An: Jboss-Development@Lists. Sourceforge. Net
>Betreff: [JBoss-dev] Scoping CL
>Dr Juno
>imho "scoping" will be useful in security (visibility of classes can be
>scoped) but
User: dsundstrom
Date: 01/08/05 12:32:19
Modified:src/main/org/jboss/ejb/plugins
EntitySynchronizationInterceptor.java
Log:
Fixed remove problem.
* Moved tx entity map to application
* Moved synchronize entities in tx method to application
* Moved sync
User: dsundstrom
Date: 01/08/05 12:32:19
Modified:src/main/org/jboss/ejb Application.java EntityContainer.java
Log:
Fixed remove problem.
* Moved tx entity map to application
* Moved synchronize entities in tx method to application
* Moved sync call to entity container find an
Dr Juno
imho "scoping" will be useful in security (visibility of classes can be
scoped) but from an admin standpoint doesn't work.
stay tuned
marcf
_
Marc Fleury, Ph.D
[EMAIL PROTECTED]
_
___
Jboss-development mailin
> Hmmm. I'm not sure I agree entirely:
>
> 1. the value object is effectively part of the interface because it is
> what is returned by the getData methods etc. So the client has to have
> access to it and I don't see anything drastically wrong with having the
> data bean as an inner class of the
User: vharcq
Date: 01/08/05 07:43:58
Modified:src/docs advconfig.xml
Log:
resource-ref section : java.net.URL and resource-managers
Revision ChangesPath
1.17 +96 -16manual/src/docs/advconfig.xml
Index: advconfig.xml
=
User: vharcq
Date: 01/08/05 06:48:24
Modified:src/docs advconfig.xml
Log:
Section on resource-ref entry
Revision ChangesPath
1.16 +125 -0manual/src/docs/advconfig.xml
Index: advconfig.xml
=
