Claude Moore wrote:Hi, I don't remember seeing such a behaviour in WAS.... Did you try to open a PMR ? Moreover, did you try as workaround to split your EJB project in two or three EJB project, in order of reducing xml descriptor size and entries number ?
Bogdan Baraila wrote:As long as the children id's are also mapped to a identity column you don't have any reasons to worry. If you add a new children to a parent object and save the parent the children will be saved also, with the setting you have now.
Bogdan Baraila wrote:Hello.
If your OverrideID is an identity column (autonumber, sequence etc.) than it should work else it will not cause this is what is using the identity generator class.
Vishwanath Krishnamurthi wrote:Hi,
Sonx Nkuks wrote:Hi, i have the following form
Here, you have given the submit-button the same name you've given for your select box. You don't need a name for a submit button. Even if you provide, it'd be better to use a unique name.
HTH,
Vishwa
David O'Meara wrote:what do you see in the HTML source for the select?
Deepak Pant wrote:
1. If you are using EJB3 then you will need Remote interface file with annotation @Remote.
2. The bean class will need to implement the remote interface. It will have @Stateless annotation.
3. Under same JVM, the JNDI lookup code should be done using the full qualified remote interface class name.
4. Suggest you clear the websphere temp dir and see if anything changes.
Deepak Pant wrote:Is your EJB Client and the EJB running in same JVM or different JVM?