[EJB 3.0] - Re: Is this a JBoss bug?
by mrducnguyen
Well, as I said, instead of using transaction-type JTA, I'm using RESOURCE_LOCAL and a non-jta-data-source. I think it's something about the security, the transaction manager of hibernate (which is the persistence provider for JBoss) cannot join with the JTA, which is managed by JBoss, and the Database Server's own transaction manager.
Anyway, changing to RESOURCE_LOCAL and non-jta-data-source may help, but be sure to provide the right hibernate.dialect property in persistence.xml. In my case, I used SQL Server, so my properties elements in persistence.xml should look like this:
| <properties>
| <property name="hibernate.dialect"
| value="org.hibernate.dialect.SQLServerDialect" />
| <property name="hibernate.hbm2ddl.auto" value="update" />
| </properties>
|
For your right dialect, please have a look at hibernate project's website. About the property hibernate.hbm2ddl.auto, which value is update, it means that if there're any changes in the Entity Bean, update those changes to the database. It can have other values, once again, you should refer to the documents of hibernate.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141805#4141805
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141805
18 years
[Security & JAAS/JBoss] - Re: Single Sign On with LDAP Examples
by sohil.shah@jboss.com
Alejandro and Mauricio are correct.
The LDAPIdentityProvider is designed to use the InetOrgPerson schema which is standard LDAP schema.
However, I think the use of cn and sn in its current implementation is not correct.
I would prefer to use uid instead of cn, and still not sure how to represent the "activation" field.
using sn is confusing.
I initially used these, since the LDAP repo that I was connecting with had the data setup that way.
However, its time the out-of-the-box LDAP impl moves away from that semantics and uses uid and something else for representing "account activation"
Part of the reason I have not changed it, is also keeping backward compatibility with existing users who have setup their LDAP repo based on this impl.
I think the cleanest approach will be leave this LDAPIdentityProvider impl as is, and introduce a new one that maps the data in a more standard manner.
I apologize for the confusion that the hackish usage of 'sn' created ;)
If I were Hillary Clinton then I would say "I mis-coded" ;)
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141802#4141802
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141802
18 years