Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version: 3.2.0

Mapping documents:
<hibernate-mapping>
<class name="uk.gov.westsussex.ipls.IPLSTreeNode" table="WSCC_IPLS">
<id name="id" column="ID">
<generator class="native"/>
</id>
<property name="name" column="Name"/>
<property name="parentid" column="Parent" type="long"/>
<property name="leftVisit" column="left_Visit" type="integer"/>
<property name="rightVisit" column="right_visit" type="integer"/>
<property name="url" column="URL"/>
<property name="eventCode" column="eventCode" type="long"/>
<set name="children" order-by="name" lazy="false">
<key column="Parent"/>
<one-to-many class="uk.gov.westsussex.ipls.IPLSTreeNode"/>
</set>
</class>
</hibernate-mapping>

Code between sessionFactory.openSession() and session.close(): Doesn't get this far

Full stack trace of any exception that occurs: org.omg.CORBA.NO_PERMISSION: not authorized to perform
bind_new_corba_context operation.

Name and version of the database you are using: Oracle 9i

The generated SQL (show_sql=true): n/a

Debug level Hibernate log excerpt:n/a

I do not have any problems with hibernate when deployed to my local server (RAD WAS 5.1 Sever), but when I deploy to our Development environment I get the Permissions problem. This occurrs when Hibernate is trying to Bind the session Factory to the JNDI Tree (for now I am just not binding it, but I am deploying to a distributed environemt, so would like the session factory there) I understand why this is occurring, but I can't find a way round this, I have had comments about changing the cos naming Group access for All_Users to write, and delete, but Our Websphere Admin won't allow this, and quite right too. Any help on this matter would be really usefull, I did find this article: http://www-128.ibm.com/developerworks/w ... otzum.html, but it hasn't helped, it has just confussed me even more, it has a link to other IBM resources one which suggests creating a context first, then using a loginContext with user and password, then use the initial Contect again. It's driving me crazy...