Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I had a scan through the instructions on that page, and it mostly follows the same steps that I have. The critical difference seems to be in the contents of his <code>jboss-app.xml</code> file:</p> <pre><code>&lt;jboss-app&gt; &lt;loader-repository&gt; org.myapp:loader=SomeClassloader &lt;loader-repository-config&gt; java2ParentDelegation=false &lt;/loader-repository-config&gt; &lt;/loader-repository&gt; &lt;/jboss-app&gt; </code></pre> <p>My system does not disable parent delegation, it only has the loader name:</p> <pre><code>&lt;jboss-app&gt; &lt;loader-repository&gt;org.myapp:loader=MyAppName&lt;/loader-repository&gt; &lt;/jboss-app&gt; </code></pre> <p>You may (or may not) also need to set the Isolated=true attribute in JBoss's <code>deploy/ear-deployer.xml</code> file:</p> <p>And that works nicely. By disabling parent delegation, you cripple your application's ability to interact with the container in any way, which is a bit extreme. If you leave out that option, though, a bit of <a href="http://en.wiktionary.org/wiki/yak_shaving" rel="nofollow noreferrer">yak shaving</a> is required</p> <p>By leaving out the <code>java2ParentDelegation=false</code> option, you get a situation where any classes in your EAR which have the same name as classes in JBoss will be loaded preferentially from the EAR (which is good). However, any classes not found in the EAR will fall through to JBoss's libs. In the case of <code>jboss-local-jdbc.rar</code>, this is good. However, it can have peculiar side effects.</p> <p>For example, when Hibernate creates a session factory, it looks for the Hibernate Search and Hibernate Validator libraries, and tries to start them up also. If these aren't present in your EAR, it will find them in JBoss's libs. The problem is that you often then get a linker error, because the versions of Search and Validator shipped with JBoss may not be compatible with the Hibernate packaged in your EAR. </p> <p>The solution to this is to either configure the Hibernate session factory to disable registration of Search and Validator listeners using config properties (<code>hibernate.validator.autoregister_listeners=false</code> and <code>hibernate.search.autoregister_listeners=false</code>), or to package compatible versions of Search and Validator in your EAR also.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload