Hi Philippe and Helene,
No I wasn't able to run your examples. This is the error message I have got
when running the client
D:\eqplite>java
-Djava.naming.factory.initial=com.sun.jndi.rmi.registry.Registry
ContextFactory eb.ClientAccount AccountImplHome
Getting a UserTransaction object from JNDI
Cannot lookup UserTransaction: javax.naming.NameNotFoundException:
javax.transaction.UserTransaction
I have sent you an email about it yesterday late afternoon
This is the output from Jonas with trace set to 3,31 running Jonas examples
JOnAS Server, version 2.0, running on rmi.
NamingManager: rebind TMFactory
NamingManager: rebind java:comp/UserTransaction
Mapping datasource jdbc:interbase://aqpone/e:/aqp/aqp/source/db/realaqp.gdb
on
qpjdbc
NamingManager.registerBean: OpHome
EJBHome:sb.JOnASOpBeanOpHome for Op available
NamingManager: setBeanEnvironment
NamingManager: setComponentContext: Op
NamingManager: Binding object prop1 -> prop1 value
CompNamingContext rebind prop1
NamingManager: setComponentContext: reset to null
NamingManager.registerBean: AccountExplHome
EJBHome:eb.JOnASAccountExplBeanAccountHome for AccountExpl available
NamingManager: setBeanEnvironment
NamingManager: setComponentContext: AccountExpl
NamingManager: Linking resource jdbc/AccountExplDs -> aqpjdbc
CompNamingContext rebind jdbc/AccountExplDs
CompNamingContext createSubcontext jdbc
CompNamingContext rebind AccountExplDs
NamingManager: setComponentContext: reset to null
NamingManager.registerBean: AccountImplHome
EJBHome:eb.JOnASAccountImplBeanAccountHome for AccountImpl available
NamingManager: setBeanEnvironment
NamingManager: setComponentContext: AccountImpl
NamingManager: setComponentContext: reset to null
NamingManager: rebind jonas_Adm
EJBServer is ready
As you can see, there is missing lines
javaURLContextFactory.getObjectInstance:null
javaURLContext rebind java:comp/UserTransaction
What does it mean???
Helene, my jndi.properties file look like this
###################### JNDI configuration
# Please refer to the JNDI documentation for further details.
# You must adapt <hostname> and maybe the port number (1099 by default)
# depending on your configuration.
# If you use Jeremie only
java.naming.factory.initial
org.objectweb.jeremie.libs.services.registry.jndi.JRMIInitialContextFactory
java.naming.provider.url jrmi://<hostname>:1099
# if you use rmi only
#java.naming.factory.initial
com.sun.jndi.rmi.registry.RegistryContextFactory
#java.naming.provider.url rmi://localhost:1099
# In both cases
java.naming.factory.url.pkgs org.objectweb.jonas.naming
BTW My first name is Miro/Miroslav 8-)))
Best Regards and thank you for your effort and help,
Miro
-----Original Message-----
From: Philippe Coq [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 16, 2000 2:20 AM
To: Halas, Miroslav
Cc: [EMAIL PROTECTED]
Subject: Re: Can't read bean environment properties
"Halas, Miroslav" wrote:
>
> Well, RMI din't work either so it is not probably problem of Jeremie.
> If I get trace from JOnas and debug the startup portion, I can see, that
the
> property is read from the XML file and bind.
>
> Deployment Descriptor of 'aqp.beans.busreq.BusinessRequirement' is read
>
> getDisplayName()=null
> getEjbName()=aqp.beans.busreq.BusinessRequirement
> getJndiName()=aqp.beans.busreq.BusinessRequirement
> getHomeClass()=interface aqp.beans.busreq.BusinessRequirementHome
> getRemoteClass()=interface aqp.beans.busreq.BusinessRequirement
> getEjbClass()=class aqp.beans.busreq.BusinessRequirementBean
> getEnvEntryDesc(0)=getName()=DOCUMENT_DB_TABLE getType()=class
> java.lang.String getValue()=T_BUSINESS_REQUIREMENT...
>
> ...
>
> JEntityHome constructor for aqp.beans.busreq.BusinessRequirement
>
JBeanMetaData.JBeanMetaData(ejbHome,aqp.beans.busreq.BusinessRequirementHome
> , aqp.beans.busreq.BusinessRequirement, aqp.beans.id.InTypeID, false,
false)
> JBeanHome.setEJBMetaData()
>
JOnASBusinessRequirementBeanBusinessRequirementHome(aqp.beans.busreq.Busines
> sRequirement)
>
EJBHome:aqp.beans.busreq.JOnASBusinessRequirementBeanBusinessRequirementHome
> for aqp.beans.busreq.BusinessRequirement available
> NamingManager: setBeanEnvironment
> NamingManager: setComponentContext: aqp.beans.busreq.BusinessRequirement
> NamingManager: Binding object DOCUMENT_DB_TABLE -> T_BUSINESS_REQUIREMENT
> CompNamingContext rebind DOCUMENT_DB_TABLE
> NamingManager: setComponentContext: reset to null
> createEJBContainer()
> ...
>
> do you haveany other clue, where could be the problem? The strange thing
is
> that the previous values are looked up correctly, it is just his
environment
> propery (and before the resource factory for DataSources) which is causing
> us this showstopper
>
> in setSessionContext
>
> this passes
> ctcContext = new InitialContext();
> m_dcDocControlHome =
(DocumentControllerHome)ctcContext.lookup(
>
> "aqp.beans.document.DocumentController");
> m_qrcQueryControlHome = (QueryControllerHome)ctcContext.lookup(
> "aqp.beans.query.QueryController");
>
> // Lookup data source for this bean
> m_dsDataSource = (DataSource)ctcContext.lookup("aqpjdbc");
>
> this fails
> objDocDBTable =
> ctcContext.lookup("java:comp/env/DOCUMENT_DB_TABLE");
>
> Best Regards,
>
> Miro
>
Excuse me Halas, but you didn't tell me if you have suceeded to
run the examples/src/eb examples in your environment.
It is very important to know that because we are sure that
this example runs, ans it can validate your environment.
Can you :
1. set up jonas.trace.level 3,31 in jonas.properties
2. run "registry "
3. under $(JONAS_ROOT)/examples/src/eb:
- make
- EJBServer
You must have the following traces:
JOnAS Server, version 2.0, running on RMI.
NamingManager: rebind TMFactory
NamingManager: rebind java:comp/UserTransaction
javaURLContextFactory.getObjectInstance:null
javaURLContext rebind java:comp/UserTransaction
Mapping datasource jdbc:oracle:thin:@malte:1521:OTS on jdbc_1
NamingManager.registerBean: AccountExplHome
EJBHome:eb.JOnASAccountExplBeanAccountHome for AccountExpl available
NamingManager: setBeanEnvironment
NamingManager: setComponentContext: AccountExpl
NamingManager: Linking resource jdbc/AccountExplDs -> jdbc_1
CompNamingContext rebind jdbc/AccountExplDs
CompNamingContext createSubcontext jdbc
CompNamingContext rebind AccountExplDs
NamingManager: setComponentContext: reset to null
NamingManager.registerBean: AccountImplHome
EJBHome:eb.JOnASAccountImplBeanAccountHome for AccountImpl available
NamingManager: setBeanEnvironment
NamingManager: setComponentContext: AccountImpl
NamingManager: setComponentContext: reset to null
NamingManager: rebind jonas_Adm
EJBServer is ready
Have you the same?
It is not a Jeremie problem for sure.
--
Philippe
Philippe Coq Groupe Bulll/BullSoft/OpenMaster Phone: (33) 04 76 29 78
49
Bull S.A - 1 rue de Provence - 38432 Echirolles Cedex France
[EMAIL PROTECTED] http://www-frec.bull.com
Download our EJBServer at http://www.bullsoft.com/ejb
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
