Document about configuring JBoss for J2EE compliance

[tobias]

Hi!
In this thread I'd like to collect all the tweaks that will come up to change the distrubution configuration to a J2EE compliant configuration.

Perhaps we can put this together in a document later on.

So if you see in another thread some hint how something needs to be configured for compliance, then copy'n'paste it to here please.

[tobias]

(moraelin:)
The Unified Classloader is also not particularly standard conform.

E.g, section "21.6.9 Runtime security enforcement" states that: "The EJB Container must isolate an enterprise bean instance from other instances and other application components running on the server. The EJB Container must ensure that other enterprise bean instances and other application components are allowed to access an enterprise bean only via the enterprise bean’s component and home interfaces."

(bill:)
Depends on the application. Sometimes the Unified Classloader is a pain, sometimes is godsend, which is why it is OPTIONAL!

classloading architecture/config I believe can be downloaded at http://sourceforge.net/projects/jboss/ under the downloads section.

===

So the Unified Classloader is OPTIONAL and should be turned off for compliance. (How do I do that for example in JBoss 3.2 ?)

[tobias]

Configure invocations on non-local interfaces (local or remote) to pass-by-value instead of pass-by-reference. (How do I do that in JBoss 3.2?)

[juhalindfors]

add org.jboss.invoker.ByValueInvokerInterceptor to your client interceptor stack in jboss.xml

[tobias]

Use the latest version of a branch (3.0.x / 3.2.x / 4.x.y) to get a version that has all the discovered inconsistencies with the spec removed.