Title: RE: PORTABILITY PROBLEMS !!!
David,
Im sorry to say that due to a slip of my butterfingers, there is a import-statement in the AccountOwnerManagerEJB that should not be there.
All the Orion-specific user-management code should be in the UserManagementSessionEJB,which is so described
The ATM example uses the Orion User Authentication API which is container
specific as the spec is currently very 'grey' in this area.
In my experience this is the biggest problem when trying to develop portable
applications. The Orion UA API is great (excellent, easy to use and very
well
Thank you.
I agree with you in the power of that API, and now I understand the
concept of this API. With it we can create users and groups dinamically
from the inside of the applications without the need to edit the
deployment descriptor or using an administrive server console.
In that way...
Hello David,
Unfortunately there are still a few things that are not standardized in J2EE
1.2, especially in the field of security and user management (like dynamically
adding users to the server).
For such things, the application server vendor unfortunately has to provide
their own ways of
Hi David and Karl,
I talked to the J2EE group at Java One about this exact subject and
just sent a message to the [EMAIL PROTECTED] group. I also cross
posted the previous post in this thread as support.
I think other people need to let the J2EE team know about these issues
and the importance
