JBossDeveloper

What about a multi-session embedded mode. The Mappings attribute would be an HibernateMapping[] array object (something you may need to create) that is umarshalled from the xml based on the jbossxb schema mappings applied in the hibernate-mapping-3.0.xsd:

 <mbean code="org.jboss.hibernate.har.HARDeployer" name="jboss.har:service=HARDeployer">
 <attribute name="Mappings" serialDataType="jbxb">
 <hbm:mappings
 xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:hbm="urn:jboss:hibernate-mapping"
 xs:schemaLocation="urn:jboss:hibernate-mapping hibernate-mapping-3.0.xsd"
 >
 <hibernate-mapping package="org.jboss.test.hibernate.model">

 <!-- there is no "Edit Role" function, so map Role as an immutable class -->
 <class name="Role" table="t_role" mutable="false">

 <!-- there are few roles, and they are not updated so cache them -->
 <cache usage="read-only"/>

 <id name="id" type="long" unsaved-value="null">
 <generator class="increment"/>
 </id>

 <property name="name" unique="true" not-null="true" update="false" length="25"/>
 <property name="description" length="150"/>
 <property name="timeOfCreation" update="false" not-null="true"/>

 <!--
 this is the "inverse" association of the User.userRoles collection. This
 mapping demonstrates that an "inverse" end of a many-to-many does not need
 to be the same type of collection mapping as the other end!
 -->
 <bag name="users" lazy="true" table="t_user_role" inverse="true" order-by="timeOfCreation asc">
 <!-- the foreign key of the Role -->
 <key column="role_id"/>
 <!-- the foreign key of the User -->
 <many-to-many column="user_id" class="User" outer-join="true"/>
 <!-- Since Users are not cached, make sure we use an outer join! -->
 </bag>

 </class>



 <!-- A named HQL query. This uses a subquery, so it won't
 work on MySQL! -->

 <query name="unassignedRolesByUser.HQL">
 <![CDATA[
 from Role role
 where not :user in ( select u.id from role.users u )
 order by role.name desc
 ]]>
 </query>


 <!-- For MySQL 4.0, which has no support for subselects, we
 need to use an ON-clause condition which is not provided
 by HQL. So we will use a named SQL query instead. -->

 <sql-query name="unassignedRolesByUser.MySQL">
 <![CDATA[
 select {rol.*}
 from t_role rol
 left join t_user_role ur
 on ur.role = rol.id and ur.user = :user
 where ur.id is null
 order by rol.name desc
 ]]>
 <return alias="rol" class="Role"/>
 <synchronize table="t_user_role"/>
 </sql-query>


 </hibernate-mapping>
 <hibernate-mapping package="org.jboss.test.hibernate.model">

 <class name="User" table="t_user">

 <id name="id" type="long" unsaved-value="null">
 <generator class="increment"/>
 </id>

 <!-- Use a timestamp for optimistic locking -->
 <version name="timeOfLastUpdate" type="calendar"/>

 <!-- We don't change the handle, so map it with update="false". -->
 <property name="handle" unique="true" not-null="true" update="false"/>

 <!-- password is a keyword in some databases, so quote it -->
 <property name="password" column="`password`" not-null="true"/>

 <property name="email"/>

 <!-- We can't change the creation time, so map it with update="false". -->
 <property name="timeOfCreation" update="false" not-null="true"/>

 <!-- Mapping for the component class Name -->
 <component name="name">
 <property name="firstName"/>
 <!-- initial is a keyword in some databases, so quote it -->
 <property name="initial" column="`initial`"/>
 <property name="lastName"/>
 </component>

 <!--
 A many-to-many association modelled using a composite-element mapping
 (this lets us keep track of the time of creation for the link. We use an
 <idbag>, since that gives us a nice surrogate key.
 -->
 <idbag name="userRoles" lazy="true" table="t_user_role" order-by="timeOfCreation asc" cascade="save-update">
 <!-- the surrogate primary key -->
 <collection-id column="id" type="long">
 <generator class="increment"/>
 </collection-id>
 <!-- the foreign key of the User -->
 <key column="user"/>
 <!--
 a composite-element holding the associated Role and User, and the
 creation time of the link
 -->
 <composite-element class="UserRole">
 <!-- for convenience, a backpointer to the User -->
 <parent name="user"/>
 <!-- an "extra" column -->
 <property name="timeOfCreation"/>
 <!-- the foreign key of the Role -->
 <many-to-one name="role" cascade="save-update" outer-join="false"/>
 <!-- since Roles are cached, disable outerjoining! -->
 </composite-element>
 </idbag>

 <!--
 Usually, when we access the user's roles, we don't care about the creation
 time of the link, etc. - we just want the roles themselves. So we map
 another collection to the same table. This demonstrates how inverse="true"
 can be used for purposes other than modelling a bi-directional association!
 -->
 <bag name="roles" lazy="true" table="t_user_role" inverse="true" order-by="timeOfCreation asc" cascade="save-update" batch-size="9">
 <!-- we access this collection often, so cache it. -->
 <cache usage="transactional"/>
 <!-- the foreign key of the User -->
 <key column="user_id"/>
 <!-- the foreign key of the Role -->
 <many-to-many column="role_id" class="Role" outer-join="false"/>
 <!-- since Roles are cached, disable outerjoining! -->
 </bag>

 <!--
 A simple collection of values. This collection table has a composite
 primary key consisting of the user and password columns.
 -->
 <set name="previousPasswords" table="t_old_passwords" lazy="true">
 <!-- the foreign key of the User-->
 <key column="user_id"/>
 <!-- the element (of value type) -->
 <element type="string" column="pswd"/>
 </set>

 </class>

 </hibernate-mapping>
 </hbm:mappings>
 </attribute>
 </mbean>

XML to Object back to XML is pointless. If there is not a usable object based metamodel then its not going to work. It seems like this is something to think about going forward as this is where everything else is going.

It should be done by editing the org.jboss.deployment.SARDeployer-xmbean.xml Suffixes attribute, but the SARDeployer.accepts method is still using hard-coded values. This needs to be replaced with a traversal through the suffixes, and moved to the SubDeployerSupport base class where the suffixes attribute actually lives.

All of the deployers using simple suffix matching need to be updated to delegate to the SubDeployerSupport.accepts method for at least that part of the testing.

Yes, the service classes need to be in the server lib directory.

To this point the suffix has had no correlation to the watch url. It was either the url in the case of a packed deployment/file, or the same deployer specific descriptor under META-INF for unpacked deployments. I'm inclined to keep it that way instead of introducing a suffix specific descriptor for now.

Steve,
Could you post a summary of what you did then to remove the HarDeployer and the changes needed to the SARDeployer to handle HARs? (including registering the .har extension). I ask this because I was following what you did with the HARDeployer before for integrating a product with JBoss and I know that others have also followed that pattern. With our integration we are also using a deployer to just pass the archive URL to the actual service which did seem like a lot of code for such little amount of work.

Thanks,
Brian Sam-Bodden

Talking about multiple sessionfactories, I am facing this issue now and hope you guys can give me some directions.
I am using jboss 4.0.2 and hibernate3. We have a central database and a bunch of administration databases. I wish I could define multiple har mbeans in one har's hibernate-service.xml. However, the jboss wiki page http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHibernate3 mentions that "Only one org.jboss.hibernate.jmx.Hibernate MBean may be defined within a given hibernate-service.xml descriptor". Does this means that if I want to have another sessionfactory, I need to create another har file? If so, can I have the same set of .hmb files in these hars?
The situation is made worse by the fact that we cannot have an exploded har inside an exploded ear. In production, we always deploy exploded ear so that support can modify some configurations. The same thing for har. We would like to modify har's config in the middle of our production.

Is it a good idea to clone one har mbean at runtime (using MBeanServer API) and modify its datasource attribute and then use the new instance of mbean for the second database? This is what I did before but not sure it is a good idea. What about those hbm mappings? If I just clone the har mbean, does the new sessionfactory can see those mappings defined in another sessionfactory?

Thanks and I am looking forward to some advices.

Richard