Re: jndi.properties and ApplicationClientInitialContextFactory

2002-02-26 Thread Brendan McKenna

Hi,

Does the requirement to install orion.jar with every instance of 
the client application mean that you have to (in a commercial environment) 
purchase an Orion license for each seperate instance of the client you 
want to run.  In other words, if I want to run 10 instances of my client,
plus 1 of the server itself, how many licenses do I need to buy, 1 or 11?



Brendan
-- 
Brendan McKenna   [EMAIL PROTECTED]
Senior Partner
Hallway Software Design Corp.






RE: jndi.properties and ApplicationClientInitialContextFactory

2002-02-26 Thread The elephantwalker

This question needs to be directed to Ironflare AB.

However, the pricing seems to say ...per server and not ...per client or
server.

regards,

the elephantwalker
www.elephantwalker.com


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Brendan
McKenna
Sent: Tuesday, February 26, 2002 1:06 AM
To: Orion-Interest
Subject: Re: jndi.properties and ApplicationClientInitialContextFactory


Hi,

Does the requirement to install orion.jar with every instance of
the client application mean that you have to (in a commercial environment)
purchase an Orion license for each seperate instance of the client you
want to run.  In other words, if I want to run 10 instances of my client,
plus 1 of the server itself, how many licenses do I need to buy, 1 or 11?



Brendan
--
Brendan McKenna   [EMAIL PROTECTED]
Senior Partner
Hallway Software Design Corp.







RE: jndi.properties and ApplicationClientInitialContextFactory

2002-02-26 Thread The elephantwalker



It was 
just pointed out to me that my link was bad...should be 

http://www.elephantwalker.com/rfa?id=178

regards,

the 
elephantwalker
www.elephantwalker.com


  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]]On Behalf Of The 
  elephantwalkerSent: Monday, February 25, 2002 1:05 PMTo: 
  Orion-InterestSubject: RE: jndi.properties and 
  ApplicationClientInitialContextFactory
  This 
  question is answered here:
  http://www.elephantwalker.com/searchresult?id=178.
  
  Basically, you must have the orion.jar, plus 
  the various j2ee helper libraries, to make your application client work with 
  orion.
  
  regards,
  
  the elephantwalker
  www.elephantwalker.com
  
  
  
-Original Message-From: 
[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]]On Behalf Of Randahl 
Fink IsaksenSent: Monday, February 25, 2002 7:55 AMTo: 
Orion-InterestSubject: jndi.properties and 
ApplicationClientInitialContextFactory

I noticed that when 
specifying the jndi properties in accordance with 
the orion documentation 
you include this line:

java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory

Does this mean that the 
application client needs to have the mentioned class in its class path? If 
so, how do you make this class available to the client  I think having the 
client application include all of the huge orion.jar (which contains this class) seems a bit 
awkward, and if you can use this class on its own I wonder why it is located 
in orion.jar.


Randahl


SV: jndi.properties and ApplicationClientInitialContextFactory

2002-02-26 Thread Magnus Rydin

Hi there,

You would pay for the 1 server and not for the 10 clients.

Hopefully we will find time to generate a small client.jar to use
instead of the larger jar files in the near future.

WR
Magnus Rydin
IronFlare

-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] För Brendan McKenna
Skickat: den 26 februari 2002 09:06
Till: Orion-Interest
Ämne: Re: jndi.properties and ApplicationClientInitialContextFactory 


Hi,

Does the requirement to install orion.jar with every instance of

the client application mean that you have to (in a commercial
environment) 
purchase an Orion license for each seperate instance of the client you 
want to run.  In other words, if I want to run 10 instances of my
client, plus 1 of the server itself, how many licenses do I need to buy,
1 or 11?



Brendan
-- 
Brendan McKenna   [EMAIL PROTECTED]
Senior Partner
Hallway Software Design Corp.






RE: jndi.properties and ApplicationClientInitialContextFactory

2002-02-26 Thread Geoff Soutter

That'd be cool.

Geoff

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED]] On Behalf Of 
 Magnus Rydin
 Sent: Wednesday, 27 February 2002 10:22 AM
 To: Orion-Interest
 Subject: SV: jndi.properties and 
 ApplicationClientInitialContextFactory 
 
 
 Hi there,
 
 You would pay for the 1 server and not for the 10 clients.
 
 Hopefully we will find time to generate a small client.jar to 
 use instead of the larger jar files in the near future.
 
 WR
 Magnus Rydin
 IronFlare
 
 -Ursprungligt meddelande-
 Från: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]] För Brendan McKenna
 Skickat: den 26 februari 2002 09:06
 Till: Orion-Interest
 Ämne: Re: jndi.properties and ApplicationClientInitialContextFactory 
 
 
 Hi,
 
   Does the requirement to install orion.jar with every instance of
 
 the client application mean that you have to (in a commercial
 environment) 
 purchase an Orion license for each seperate instance of the 
 client you 
 want to run.  In other words, if I want to run 10 instances 
 of my client, plus 1 of the server itself, how many licenses 
 do I need to buy, 1 or 11?
 
 
 
   Brendan
 -- 
 Brendan McKenna   [EMAIL PROTECTED]
 Senior Partner
 Hallway Software Design Corp.
 
 
 
 





jndi.properties and ApplicationClientInitialContextFactory

2002-02-25 Thread Randahl Fink Isaksen








I noticed that when specifying the jndi properties in accordance with the orion documentation you include this line:



java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory



Does this mean that the application client
needs to have the mentioned class in its class path? If so, how do you make
this class available to the client  I think having the client
application include all of the huge orion.jar (which
contains this class) seems a bit awkward, and if you can use this class on its
own I wonder why it is located in orion.jar.





Randahl








RE: jndi.properties and ApplicationClientInitialContextFactory

2002-02-25 Thread The elephantwalker



This 
question is answered here:
http://www.elephantwalker.com/searchresult?id=178.

Basically, you must have the orion.jar, plus the 
various j2ee helper libraries, to make your application client work with 
orion.

regards,

the elephantwalker
www.elephantwalker.com



  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink 
  IsaksenSent: Monday, February 25, 2002 7:55 AMTo: 
  Orion-InterestSubject: jndi.properties and 
  ApplicationClientInitialContextFactory
  
  I noticed that when 
  specifying the jndi properties in accordance with 
  the orion documentation you 
  include this line:
  
  java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory
  
  Does this mean that the 
  application client needs to have the mentioned class in its class path? If so, 
  how do you make this class available to the client  I think having the client 
  application include all of the huge orion.jar (which 
  contains this class) seems a bit awkward, and if you can use this class on its 
  own I wonder why it is located in orion.jar.
  
  
  Randahl


Re: jndi.properties and ApplicationClientInitialContextFactory

2002-02-25 Thread Warren Hedley

Hi Randahl,

Yip, if you want to use Orion's container to manage your application client, 
then your client will need to include a bunch of Orion's classes + the Crimson 
XML parser (which requires DOM and SAX classes in turn) + javax transaction and 
security classes. I've managed to get the size of the client helper JAR down 
to 2MB, and it could probably get lower if you have the patience to manually 
remove classes from the JAR.

This is unfortunately the price you pay for the advantages of using Enterprise 
Java like RMI to beans and authentication.

Regards,
Warren Hedley


Randahl Fink Isaksen wrote:
 I noticed that when specifying the jndi properties in accordance with 
 the orion documentation you include this line:

 
java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory

 Does this mean that the application client needs to have the mentioned 
 class in its class path? If so, how do you make this class available to 
 the client ? I think having the client application include all of the 
 huge orion.jar (which contains this class) seems a bit awkward, and if 
 you can use this class on its own I wonder why it is located in orion.jar.





jndi.properties

2001-12-18 Thread Namor Taror


I'm getting jndi exception when envoking ejb web service. I have defined 
jndi.properties file and put a reference to it into my system classpath as 
well as into the axis orion-application.xml and orion-web.xml files.

My jndi.properties file is:

java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory
java.naming.provider.url=ormi://localhost:23791/Schedule
java.naming.security.principal=admin
java.naming.security.credentials=123


and the exception is:

javax.naming.NamingException: Error instantiating web-app JNDI-context: No 
location specified and no suitable instance of the type 
'com.taror.schedule.ejb.session.scheduler.SchedulerManager' found for the 
ejb-ref SchedulerManager



_
Send and receive Hotmail on your mobile device: http://mobile.msn.com