Article:
  JBoss Optimizations 101
Subject:   How to utilize this with a session facade
Date:   2003-06-09 19:27:33
From:   anonymous2
Response to: How to utilize this with a session facade

The read-only tag in jboss.xml (and not the one in jbosscmp-jdbc.xml) is about enrollement in the current transaction and locking. Consequently, it has no sense in the case of a session bean (but only in the case of an entity bean. In your case, you may simply want to deploy the same EJB twice: one with RO, and one witout RO.


Cheers,



sacha

Main Topics Oldest First

Showing messages 1 through 2 of 2.

  • How to utilize this with a session facade
    2003-06-10 01:19:49  anonymous2 [View]

    Just a little follow-up-question:

    Do I have to make new RO relations as well?

    Suppose I have a PersonEJB with a CMR (recursive, if that matters) collection Children.

    So I make another deployment of PersonEJB, called PersonEJBRW, with <read-only>false</read-only> markup for the getChildren method, in ejb-jar.xml. I just copy the <entity>-section for PersonEJB and changed <entity-name> and <display-name>. In addition new <containser-transaction> specs for all methods are added (or could I "inherit" those somehow from PersonEJB?)

    I update jbosscmp-jdbc.xml so that both beans uses the same table, and I have a special entry for PersonEJBRW in jboss.xml specifying that all getters _except_ getChildren is <read-only>true</read-only>

    I suppose I must make new CMR-relations as well in ejb-jar.xml?

    So, basically, my question is; what have I forgotten here? I can't believe I've figured it out on the first try, that'd be very much unlike me :-)

    --
    Jon Martin Solaas
    jonmartin.solaas@mail.link.no
  • How to utilize this with a session facade
    2003-06-09 23:56:55  anonymous2 [View]

    Uh, why didn't I think of that myself ... :-)

    Thanks!

    --
    jon martin solaas