Dear David,
I really appreciate you sincere effort and yours persistence guidance,helfulness and caring attitude that you have shown and set as an example over in this forum on helping peolple epecially towards the newbies .
For the benefit of others and on open source sharing principle , I would seek your understanding and permission to allow me to reproduce your explanation towards the issue at this forum
---------------------------------------------------------------------------------
Had a quick look at the code. I cannot run it etc as such but I had a
look anyway. I hope the examples are not formatted oddly by the email
client.
Here are my comments.
I was glad to see your not (no longer) trying to access the system from
the GUI via JNDI (It will never work).
So here is what I would try:
1) I assume you have confirmed you do get into the SLSB from the swing
client (make sure you can).
2) Break some of the code into small utility functions so it can be much
cleaner (it is a bit of a mess at the moment).
For example here an example of the JNDI lookup.
public class HibernateUtil {
public static SessionFactory getHibernateSessionFactory() throws
NamingException
{
InitialContext initialContext = new InitialContext();
try {
SessionFactory factory = (SessionFactory)
initialContext.lookup("java:/HibernateFactory");
return factory;
}
finally {
initialContext.close();
}
}
}
3) Use CMT for the SLSB which simplifies the transaction management, eg,
don't need to do any. For example.
public boolean isUserValid(String UserName, String Password) {
Session sess = null;
boolean result = false;
try {
sess = HibernateUtil.openSession(this.factory);
result = authDAO.isUserValid(UserName, Password);
sess.flush();
}
catch (Exception e) {
ctx.setRollbackOnly();
throw ExceptionAdapterUtil.createExceptionAdapter(e);
}
finally {
HibernateUtil.closeSession(sess);
}
return result;
}
Where ctx is the SLSB context attribute, the factory is returned set when
the SLSB is created by the utility function above. The utility functions for
the session creates it and places the session into a Thread local for access
by the DAO layer. You may not need this so the DAO becomes you operations
and you open and close the session as normal from the session factory.
You can see there is not start transaction or commit. Not needed let the
container do the work for you. If you really want this then you will need to
define the user transaction JNDI entry in your SAR service description. This
is the JNDI lookup the is failing. Use CMT only and it is likely it will
work.
Finally you service description should not leave any spaces in the
definition, eg, don't have the <attribute> tags on there own lines. I have
found that sometime problems occur if you do this (depends on the Hibernate
version how tolerant it is).
<server>
<mbean code="net.sf.hibernate.jmx.HibernateService"
name="jboss.jca:service=HibernateFactory, name=HibernateFactory">
<depends>jboss.jca:service=RARDeployer</depends>
<!-- Make it deploy ONLY after DataSource had been started -->
<depends>jboss.jca:service=LocalTxCM,name=PostgresDS</depends>
<attribute name="MapResources">src/grp.hbm.xml,
src/codemaster.hbm.xml</attribute>
<attribute name="JndiName">java:/HibernateFactory</attribute>
<attribute name="Datasource">java:/PostgresDS</attribute>
<attribute
name="Dialect">net.sf.hibernate.dialect.PostgreSQLDialect</attribute>
<attribute
name="TransactionStrategy">net.sf.hibernate.transaction.JTATransactionFactor
y</attribute>
<attribute
name="TransactionManagerLookupStrategy">net.sf.hibernate.transaction.JBossTr
ansactionManagerLookup</attribute>
<attribute name="UseOuterJoin">false</attribute>
<attribute name="ShowSql">true</attribute>
</mbean>
</server>
Good luck,
Cheers David,
--------------------------------------------------------------------------------------
Just side track a bit , supposing a seperate jar files or class files have been employed using the SAR , how would one make use of the existing class packaged in the SAR through JMX ? what on my mind right now is , if I could successfully look up the factory , would it be a better approach to adopt where having some CMP or BMP transactions embedded within the session bean such as casting of hiebernate class involving get method
Thanks
ERIC
Login
FAQ
Search
