Hi,
I'm trying to use xalan 2.5.1 in an application, but I'm running into
NoClassDefFound error's.
This is the code to create the Transformer (snip 2) and the
code that tries to translate (snip 1):
== code snip 1 =
import javax.xml.transform.Transformer;
// get XSLT Transformer
Tra
Hello JBoss users,
> > This task is performed by a class called DAOBuilder. It parses an XML
file
> > (for example, AccountDAO.xml), generates some java code (i.e.
> > AccountDAO.java) and compiles it (AccountDAO.class)
> > The generated classes are copied into a spool directory that has been
add
Hello Chris,
> I don't know which version you're running, but with JBoss 3.0, I had to
unfortunately I am using JBoss-2.4.4.
Thanks anyway,
--
Ludovico Basili
Software Engineer
Allied Telesis K.K.
Phone +39 02 41411245 - FAX +39 02 41411260 - email
[EMAIL PROTECTED]
___
Hello, Dan
> > The generated classes are copied into a spool directory that has been
added
> > to the JBOSS_CLASSPATH variable at startup.
>
> Don't do that. put the generated classes into your ejb jar file instead.
>
How can I do it ? When I compile the classes the ejbs are already deployed
and
Ludovico Basili wrote:
> Hello,
> I use the Data Access Object pattern to separate my EJBs from the data tier.
> The DAO classes are automatically generated from XML files and compiled at
> runtime.
> This task is performed by a class called DAOBuilder. It parses an XML file
> (for example, Accoun
Hi,
I don't know which version you're running, but with JBoss 3.0, I had to
manually add in an additional classpath element that will look for files
under /lib/ext directory. So what I did was add the following line to my
jboss-service.xml:
Thanks,
Chris
At 10:13 AM 06/05/2002, you wro
Hello,
I use the Data Access Object pattern to separate my EJBs from the data tier.
The DAO classes are automatically generated from XML files and compiled at
runtime.
This task is performed by a class called DAOBuilder. It parses an XML file
(for example, AccountDAO.xml), generates some java code
t;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 24, 2001 11:59 PM
Subject: Re: [JBoss-user] Classloader problem in ear
> Scott M Stark wrote:
>
> > This is the expected behavior given the current ear deployer. EJB classes
> > are made available to wars
Scott M Stark wrote:
> This is the expected behavior given the current ear deployer. EJB classes
> are made available to wars and if you put you servlets in the ejb-jar archive
> it will be seen there first as this is ahead of the war classes. If you don't
> want this behavior only include the se
e war.
- Original Message -
From: "Remus Jivcu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 20, 2001 4:37 AM
Subject: [JBoss-user] Classloader problem in ear
> Hi,
>
> During deploying some applications on JBoss I've discovered following
> Source please.
>
> r.b.
Here it comes :
MyServlet.java
***
package test.servlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.RequestDispatcher;
import java.io.IOException;
>1) If my servlet class is placed ONLY in test.war, then the classloader
>for the servlet is : AdaptiveClassLoader (normal case, I assume);
>2) If I place my servlet ALSO in test.jar (let's say by mistake), then
>the classloader for the servlet is : java.net.URLClassLoader@4df764
>3) If I place my
Hi,
During deploying some applications on JBoss I've discovered following
interesting thing :
Suppose I have this structure in my ear file :
- test.jar (simple session bean - not used at all in this case)
- test.war (one simple servlet)
- META-INF folder with application.xml file.
1) If my serv
13 matches
Mail list logo
