Re: [JBoss-user] problem with JNDI lookup...

2001-05-07 Thread David L Solomon

I got this to work by copying my ejb's jar file to JBOSS_HOME\lib\ext

I'm not sure why this is needed since this file is already in the deploy
directory.

Also, Can someone point me to a good resource to explain what .war and .ear
files are supposed to contain and what threir purposes are?


Thanks,
dave
- Original Message -
From: David L Solomon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, April 16, 2001 2:16 PM
Subject: [JBoss-user] problem with JNDI lookup...


 I am running JBOSS 2.2 with embedded tomcat 3.2.1 on NT 4.0 sp6

 I have a test program which tests my ejb using the following code:


 // Get a naming context

 InitialContext jndiContext = new InitialContext();

 System.out.println(Got context);

 // This is in the case you use the jboss.xml to override the JNDI name

 Object ref = jndiContext.lookup(ValidateUser);

 System.out.println(Got reference);

 // Get a reference from this to the Bean's Home interface

 ValidateUserHome home = (ValidateUserHome) PortableRemoteObject.narrow
(ref,
 ValidateUserHome.class);

 // Create an Interest object from the Home interface

 ValidateUser l_ValidateUser = home.create();

 .// call beans methods here





 This works just fine.  However, when i call this exact same code from a
 servlet, I get the following exception ( thrown from the call to
 jndiContext.lookup(ValidateUser);) )



 Got context javax.naming.CommunicationException [Root exception is
 java.lang.ClassNotFoundException: database.ValidateUserHome]





 Finally, this works just fine from a servlet when i run (older versions
Pre
 2.1 ) jboss and and tomcat 3.2.1 in separate JVMs.

 Thanks in advance for any help on this.



 dave





 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



[JBoss-user] problem deploying ear file

2001-04-22 Thread David L Solomon

I am running jboss 2.2.1, with embedded tomcat 3.2.1 on windows nt 4.0, sp6.

when I try to deploy an ear file containing my ejb ( ValidateUser in
'database' package ), I get the following error:
What is the verifier trying to tell me.  Thanks.




[Auto deploy] Auto deploy of
file:/D:/JBoss-2.2.1_Tomcat-3.2.1/jboss/deploy/four
plebs.ear
[J2EE Deployer Default] Deploy J2EE application:
file:/D:/JBoss-2.2.1_Tomcat-3.2
.1/jboss/deploy/fourplebs.ear
[J2EE Deployer Default] Create application fourplebs.ear
[J2EE Deployer Default] install module fourplebs.ear
[Container factory]
Deploying:file:/D:/JBoss-2.2.1_Tomcat-3.2.1/jboss/tmp/deploy
/Default/fourplebs.ear
[Verifier] Verifying
file:/D:/JBoss-2.2.1_Tomcat-3.2.1/jboss/tmp/deploy/Default/
fourplebs.ear/ejb1001.jar
[Verifier]
Bean   : ValidateUser
Section: 16.2
Warning: The Bean Provider must specify the fully-qualified name of the Java
cla
ss that implements the enterprise bean's business methods.

[Verifier]
Bean   : ValidateUser
Section: 16.2
Warning: The Bean Provider must specify the fully-qualified name of the
enterpri
se bean's home interface in the home element.

[Verifier]
Bean   : ValidateUser
Section: 16.2
Warning: The Bean Provider must specify the fully-qualified name of the
enterpri
se bean's remote interface in the remote element.

[Container factory] Deploying ValidateUser
[Container factory] java.lang.ClassNotFoundException:
database.ValidateUserHome
[Container factory] at
java.net.URLClassLoader$1.run(URLClassLoader.java:200
)
[Container factory] at
java.security.AccessController.doPrivileged(Native Me
thod)
[Container factory] at
java.net.URLClassLoader.findClass(URLClassLoader.java
:188)
[Container factory] at
java.lang.ClassLoader.loadClass(ClassLoader.java:297)

[Container factory] at
java.lang.ClassLoader.loadClass(ClassLoader.java:253)

[Container factory] at
org.jboss.ejb.StatelessSessionContainer.init(Stateles
sSessionContainer.java:137)
[Container factory] at
org.jboss.ejb.Application.init(Application.java:183)
[Container factory] at
org.jboss.ejb.ContainerFactory.deploy(ContainerFactor
y.java:337)
[Container factory] at
org.jboss.ejb.ContainerFactory.deploy(ContainerFactor
y.java:275)
[Container factory] at java.lang.reflect.Method.invoke(Native Method)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
rverImpl.java:1628)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
rverImpl.java:1523)
[Container factory] at
org.jboss.deployment.J2eeDeployer.startApplication(J2
eeDeployer.java:435)
[Container factory] at
org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer
.java:178)
[Container factory] at java.lang.reflect.Method.invoke(Native Method)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
rverImpl.java:1628)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
rverImpl.java:1523)
[Container factory] at
org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:3
58)
[Container factory] at
org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:221)

[Container factory] at
org.jboss.ejb.AutoDeployer.startService(AutoDeployer.
java:332)
[Container factory] at
org.jboss.util.ServiceMBeanSupport.start(ServiceMBean
Support.java:93)
[Container factory] at java.lang.reflect.Method.invoke(Native Method)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
rverImpl.java:1628)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
rverImpl.java:1523)
[Container factory] at
org.jboss.util.ServiceControl.start(ServiceControl.ja
va:97)
[Container factory] at java.lang.reflect.Method.invoke(Native Method)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
rverImpl.java:1628)
[Container factory] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
rverImpl.java:1523)
[Container factory] at org.jboss.Main.init(Main.java:203)
[Container factory] at org.jboss.Main$1.run(Main.java:107)
[Container factory] at
java.security.AccessController.doPrivileged(Native Me
thod)
[Container factory] at org.jboss.Main.main(Main.java:103)
[J2EE Deployer Default] Starting fourplebs.ear failed!
[J2EE Deployer Default] Module fourplebs.ear is not running
[J2EE Deployer Default] Destroying application fourplebs.ear
[Auto deploy] Deployment
failed:file:/D:/JBoss-2.2.1_Tomcat-3.2.1/jboss/deploy/f
ourplebs.ear
[Auto deploy] org.jboss.deployment.J2eeDeploymentException: Error while
starting
 fourplebs.ear: Could not deploy
file:/D:/JBoss-2.2.1_Tomcat-3.2.1/jboss/tmp/dep
loy/Default/fourplebs.ear
[Auto deploy]   at
org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeploy
er.java:441)
[Auto deploy]   at
org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:17
8)
[Auto deploy]   at java.lang.reflect.Method.invoke(Native Method)
[Auto deploy]   at

Re: [JBoss-user] mod_jk.conf-auto file not being rewritten

2001-04-19 Thread David L Solomon

i ran into this problem also.  I ran tomcat.bat first which generated the
mod_jk.conf-auto, then killed off tomcat, and ran jboss with embedded tomcat
after.

hope this helps,

dave


- Original Message -
From: "Ryan Partridge" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, April 19, 2001 4:32 PM
Subject: [JBoss-user] mod_jk.conf-auto file not being rewritten


I am running JBoss w/ Embedded Tomcat + Apache (all the latest versions) on
a RedHat 7.0 box.  I have followed on the instructions on jakarta.apache.org
to configure Apache and Tomcat.  However, this setup depends on Tomcat
rewriting the mod_jk.conf-auto file each time it starts.  For whatever
reason, when JBoss starts Tomcat, the mod_jk.conf-auto file does not get
rewritten, so Apache cannot correctly forward requests to Tomcat.  Is there
something I'm missing?

Ryan Partridge


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



[JBoss-user] problem with JNDI lookup...

2001-04-16 Thread David L Solomon

I am running JBOSS 2.2 with embedded tomcat 3.2.1 on NT 4.0 sp6

I have a test program which tests my ejb using the following code:


// Get a naming context

InitialContext jndiContext = new InitialContext();

System.out.println("Got context");

// This is in the case you use the jboss.xml to override the JNDI name

Object ref = jndiContext.lookup("ValidateUser");

System.out.println("Got reference");

// Get a reference from this to the Bean's Home interface

ValidateUserHome home = (ValidateUserHome) PortableRemoteObject.narrow (ref,
ValidateUserHome.class);

// Create an Interest object from the Home interface

ValidateUser l_ValidateUser = home.create();

.// call beans methods here





This works just fine.  However, when i call this exact same code from a
servlet, I get the following exception ( thrown from the call to
jndiContext.lookup("ValidateUser");) )



Got context javax.naming.CommunicationException [Root exception is
java.lang.ClassNotFoundException: database.ValidateUserHome]





Finally, this works just fine from a servlet when i run (older versions Pre
2.1 ) jboss and and tomcat 3.2.1 in separate JVMs.

Thanks in advance for any help on this.



dave





___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user