Hey Faisal,
Try doing the JNDI list with the given jndiView.jar and see whether your
bean is properly deployed when you use the embedded tomcat. Also check
whether you are logging to console or file and if you want set the logging
level to be DEBUG so that you see every bit of information.
--Swam
A While back Ken Jenks posted a message on some changes you may need to
> make to application.xml to allow the servlet to see the EJB classes. Have
> you seen this and tried it? It seemed to work for the person he was
> helping at the time.
>
> On Thu, 29 Mar 2001, Swami Iyer wrote:
the tomcatbundle is the
configuration and not the binaries.
Thanks,
Swami
-Original Message-
From: Patrick Buchinger [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 29, 2001 11:16 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] bug in the latest few versions of jBoss 2.1
Swami Iyer
as
helping at the time.
On Thu, 29 Mar 2001, Swami Iyer wrote:
> Hi,
> I downloaded the Mar 26th zip file (JBOSS/TOMCAT) from JBOSS site and
> deployed our .ear file and it worked.
>
> I have no explanation as to why the .ear file you have work in earlier
> version and not th
Hi,
I downloaded the Mar 26th zip file (JBOSS/TOMCAT) from JBOSS site and
deployed our .ear file and it worked.
I have no explanation as to why the .ear file you have work in earlier
version and not the new one. Can you check the Context class loaders in
server.xml in tomcat.
THanks,
Swami
---
The way we did was we created our own equivalent mod_jk file which we
included in the httpd.conf of apache. Whenever a new context root needs to
be deployed we modified the equivalent mod_jk file to reflect the changes.
Everything works like a charm.
Thanks,
Swami
-Original Message-
Fro
Just my ten cents worth. The JSP/Servlet settings have a reload property
which can be used to identify when it would be reloaded. But if a JSP
session or servlet session is existing then you have to close the session
before trying out the newly deployed Bean implementation.
Swami
-Original M
]
Subject: Re: [JBoss-user] deploying an .ear
Swami Iyer wrote:
> Put the client side EJB files into the lib directory in your EAR file.
>
> Swami
thank you, for your answer, but still a ClassNotFoundException!
my ear file looked the following:
app .jar
app.war
META-INF/application.x
The EAR should be used in the final stages of the product which is during
the QA/production. The directory deployment is good during the development
process. The APACHE-TOMCAT integration gives you the webserver/servlet
container combination where you could stretch the whole thing by making the
AP
Put the client side EJB files into the lib directory in your EAR file.
Swami
-Original Message-
From: Patrtick Buchinger [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 27, 2001 3:29 AM
To: Jboss (E-mail)
Subject: [JBoss-user] deploying an .ear
hi everybody!
sorry if this is an RTFM,
There is something wrong with the class file. Why don't you try doing this
javap -classpath interest.jar ex.web.in.Interest and you can see the bad
class error. You got to fix this before you deploy.
Swami
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Frida
11 matches
Mail list logo