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... a good approach to compatibility could be to write the
application as normal and then write a class which implements the security
API so if we want to move to another server, we don't have to rewirte the
beans and we only should rewrite the secutiy class with the implementation
of the security API of the new server.
Am I correct?
-------------------------------------------------------------
David Sierra Fern�ndez
E.T.S.I. Telecomunicaci�n
Universidad de Valladolid AULA CEDETEL
Campus Miguel Delibes E-Mail: [EMAIL PROTECTED]
47011 Valladolid (SPAIN)
--------------------------------------------------------------
-- Sierr@ --
On Fri, 16 Jun 2000, Mike Cannon-Brookes wrote:
> 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 structured once you work it out!) but it is non standard - all
> containers have their own API.
>
> If you want portability, roll your own user management API (but this is a
> pain as it won't hook nicely into app server functions).
>
> Such is life on the edge.
>
> Mike
>
> > -----Original Message-----
> > 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 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 .class files but It
> > does not work anyway. For last I tried to compile again the classes but I
> > got the following error:
> >
> > AccountOwnerManagerEJB.java:8: Package com.evermind.security not found in
> > import
> > .
> > import com.evermind.security.*;
> > ^
> > UserManagementSessionEJB.java:7: Package com.evermind.security not found
> > in impo
> > rt.
> > import com.evermind.security.*;
> >
> >
> >
> > If the standard file is the jar, Why Orion include especific files in the
> > code? Does this not break the comatibility?
> >
> > How I can deploy an Orion application in other servers to test
> > performance?
> >
> >
> > THANK YOU.
> >
> >
> > -------------------------------------------------------------
> > David Sierra Fern�ndez
> > E.T.S.I. Telecomunicaci�n
> > Universidad de Valladolid AULA CEDETEL
> > Campus Miguel Delibes E-Mail: [EMAIL PROTECTED]
> > 47011 Valladolid (SPAIN)
> > --------------------------------------------------------------
> >
> > -- Sierr@ --
> >
> >
>
>
