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
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 for
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 doin
On Behalf Of David Sierra
> > Fernandez
> > Sent: Friday, 16 June 2000 10:41
> > To: Orion-Interest
> > Subject: PORTABILITY PROBLEMS !!!
> >
> >
> >
> > I tried to deploy ATM example in Sun's J2EE implementation server, but it
> > d
---
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David Sierra
> Fernandez
> Sent: Friday, 16 June 2000 10:41
> To: Orion-Interest
> Subject: PORTABILITY PROBLEMS !!!
>
>
>
> I tried to deploy ATM example in Sun's J2EE implementation server, but
I tried to deploy ATM example in Sun's J2EE implementation server, but it
didn't recognize ear file. I tried to create the ear file mayself but when
I tried to include the war and jar files, this last was also not recognize
as a valid file.
Then I tried to create both files begining from the .cl
