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 in the deployment description.
Im sorry for any problems the import statement has caused.
Magnus Rydin
> -----Original Message-----
> From: David Sierra Fernandez [mailto:[EMAIL PROTECTED]]
> Sent: den 16 juni 2000 14: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@ --
>
>
