Second Try: Can anyone explain this?

2004-06-16 Thread Worley Brent - bworle
I posted this earlier and received a few leads on what to do, but nothing
worked.  I'm hoping a second look and explanation will help.

The page that is causing the error (search.jsp) uses a taglib to load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).  The .tld
file defines a tag named xslt that uses a class named JspXslt.  JspXslt is
located in WEB-INF/lib/Xslt.jar.  

So here are my questions:

1.  Is anyone familiar with a standard Xslt.jar file that contains the
JspXslt.class object?
2.  Why would Tomcat not find JspXslt.class?

I've included the xml from the .tld file and the errors below.  

taglib
  tlibversion0.0/tlibversion
  jspversion1.0/jspversion
  shortnameacx/shortname
  tag
namexslt/name
tagclassJspXslt/tagclass
bodycontentjsp/bodycontent
attribute
  namexml/name
  requiredfalse/required
  rtexprvaluetrue/rtexprvalue
/attribute
attribute
  namexslt/name
  requiredtrue/required
  rtexprvaluetrue/rtexprvalue
/attribute
attribute
  namenobreak/name
  requiredfalse/required
  rtexprvaluetrue/rtexprvalue
/attribute
  /tag
/taglib

org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
[javac] Compiling 1 source file

/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt 
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
  ^



An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt 
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
 ^



An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt 
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
 
^
Note:
/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java uses or overrides a deprecated API.
Note: Recompile with -deprecation for details.
3 errors


at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
r.java:83)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:3
06)
at
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:398)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:441)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:422)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
07)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
74)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContext
Valve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at

RE: Second Try: Can anyone explain this?

2004-06-16 Thread Shapira, Yoav

Hi,
Someone told you to put JspXslt.class in a package, IIRC.  I think
that's the problem.  Repackage the jar if you have to, for testing
purposes, and change the TLD to refer to the class by whatever package
you put it in, e.g. com.foo.bar.JspXslt.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:32 PM
To: 'Tomcat Users List'
Subject: Second Try: Can anyone explain this?

I posted this earlier and received a few leads on what to do, but
nothing
worked.  I'm hoping a second look and explanation will help.

The page that is causing the error (search.jsp) uses a taglib to load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).  The
.tld
file defines a tag named xslt that uses a class named JspXslt.  JspXslt
is
located in WEB-INF/lib/Xslt.jar.

So here are my questions:

1.  Is anyone familiar with a standard Xslt.jar file that contains the
JspXslt.class object?
2.  Why would Tomcat not find JspXslt.class?

I've included the xml from the .tld file and the errors below.

taglib
  tlibversion0.0/tlibversion
  jspversion1.0/jspversion
  shortnameacx/shortname
  tag
namexslt/name
tagclassJspXslt/tagclass
bodycontentjsp/bodycontent
attribute
  namexml/name
  requiredfalse/required
  rtexprvaluetrue/rtexprvalue
/attribute
attribute
  namexslt/name
  requiredtrue/required
  rtexprvaluetrue/rtexprvalue
/attribute
attribute
  namenobreak/name
  requiredfalse/required
  rtexprvaluetrue/rtexprvalue
/attribute
  /tag
/taglib

org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
[javac] Compiling 1 source file

/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
  ^



An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
 ^



An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);

^
Note:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java uses or overrides a deprecated API.
Note: Recompile with -deprecation for details.
3 errors


   at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorH
andl
e
r.java:83)
   at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.j
ava:
3
06)
   at
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:398)
   at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:441)
   at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:422)
   at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.j
ava:
5
07)
   at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.j
ava:
2
74)
   at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292
)
   at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
   at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic
atio
n
FilterChain.java:237)
   at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil
terC
h
ain.java:157)
   at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVal
ve.j
a
va:214)
   at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC
onte
x
t.java:104)
   at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
520)
   at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardCo
ntex
t
Valve.java:198)
   at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextVal
ve.j
a
va:152)
   at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC
onte
x
t.java:104)
   at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
520)
   at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav
a:13
7
)
   at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC
onte
x

Re: Second Try: Can anyone explain this?

2004-06-16 Thread Tim Funk
And I answered it here:
http://marc.theaimsgroup.com/?l=tomcat-userm=108723827315299w=2
-Tim
Worley Brent - bworle wrote:
I posted this earlier and received a few leads on what to do, but nothing
worked.  I'm hoping a second look and explanation will help.
The page that is causing the error (search.jsp) uses a taglib to load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).  The .tld
file defines a tag named xslt that uses a class named JspXslt.  JspXslt is
located in WEB-INF/lib/Xslt.jar.  

So here are my questions:
1.  Is anyone familiar with a standard Xslt.jar file that contains the
JspXslt.class object?
2.  Why would Tomcat not find JspXslt.class?
I've included the xml from the .tld file and the errors below.  

taglib
  tlibversion0.0/tlibversion
  jspversion1.0/jspversion
  shortnameacx/shortname
  tag
namexslt/name
tagclassJspXslt/tagclass
bodycontentjsp/bodycontent
attribute
  namexml/name
  requiredfalse/required
  rtexprvaluetrue/rtexprvalue
/attribute
attribute
  namexslt/name
  requiredtrue/required
  rtexprvaluetrue/rtexprvalue
/attribute
attribute
  namenobreak/name
  requiredfalse/required
  rtexprvaluetrue/rtexprvalue
/attribute
  /tag
/taglib
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: 55 in the jsp file: /search.jsp
Generated servlet error:
[javac] Compiling 1 source file
/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt 
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
  ^


An error occurred at line: 55 in the jsp file: /search.jsp
Generated servlet error:
/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt 
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
 ^


An error occurred at line: 55 in the jsp file: /search.jsp
Generated servlet error:
/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt 
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
 
^
Note:
/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java uses or overrides a deprecated API.
Note: Recompile with -deprecation for details.
3 errors

at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
r.java:83)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:3
06)
at
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:398)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:441)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:422)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
07)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
74)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContext
Valve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)
 

RE: Second Try: Can anyone explain this?

2004-06-16 Thread Worley Brent - bworle
Tried that and got the same error.  This is what I did

jar -xf Xslt.jar JspXslt.class

Moved JspXslt.class to WEB-INF/classes

No change.

-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:05 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?


And I answered it here:
http://marc.theaimsgroup.com/?l=tomcat-userm=108723827315299w=2

-Tim

Worley Brent - bworle wrote:

 I posted this earlier and received a few leads on what to do, but nothing
 worked.  I'm hoping a second look and explanation will help.
 
 The page that is causing the error (search.jsp) uses a taglib to load
 xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).  The
.tld
 file defines a tag named xslt that uses a class named JspXslt.  JspXslt is
 located in WEB-INF/lib/Xslt.jar.  
 
 So here are my questions:
 
 1.  Is anyone familiar with a standard Xslt.jar file that contains the
 JspXslt.class object?
 2.  Why would Tomcat not find JspXslt.class?
 
 I've included the xml from the .tld file and the errors below.  
 
 taglib
   tlibversion0.0/tlibversion
   jspversion1.0/jspversion
   shortnameacx/shortname
   tag
 namexslt/name
 tagclassJspXslt/tagclass
 bodycontentjsp/bodycontent
 attribute
   namexml/name
   requiredfalse/required
   rtexprvaluetrue/rtexprvalue
 /attribute
 attribute
   namexslt/name
   requiredtrue/required
   rtexprvaluetrue/rtexprvalue
 /attribute
 attribute
   namenobreak/name
   requiredfalse/required
   rtexprvaluetrue/rtexprvalue
 /attribute
   /tag
 /taglib
 
 org.apache.jasper.JasperException: Unable to compile class for JSP
 
 An error occurred at line: 55 in the jsp file: /search.jsp
 
 Generated servlet error:
 [javac] Compiling 1 source file
 

/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
 search_jsp.java:295: cannot resolve symbol
 symbol  : class JspXslt 
 location: class org.apache.jsp.search_jsp
   JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
 _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
   ^
 
 
 
 An error occurred at line: 55 in the jsp file: /search.jsp
 
 Generated servlet error:

/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
 search_jsp.java:295: cannot resolve symbol
 symbol  : class JspXslt 
 location: class org.apache.jsp.search_jsp
   JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
 _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
  ^
 
 
 
 An error occurred at line: 55 in the jsp file: /search.jsp
 
 Generated servlet error:

/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
 search_jsp.java:295: cannot resolve symbol
 symbol  : class JspXslt 
 location: class org.apache.jsp.search_jsp
   JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
 _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
  
 ^
 Note:

/usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
 search_jsp.java uses or overrides a deprecated API.
 Note: Recompile with -deprecation for details.
 3 errors
 
 
   at

org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
 r.java:83)
   at

org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:3
 06)
   at
 org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:398)
   at org.apache.jasper.compiler.Compiler.compile(Compiler.java:441)
   at org.apache.jasper.compiler.Compiler.compile(Compiler.java:422)
   at

org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
 07)
   at

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
 74)
   at
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
   at

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
 FilterChain.java:237)
   at

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
 ain.java:157)
   at

org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
 va:214)
   at

org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
 t.java:104)
   at

org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
   at

org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContext
 Valve.java:198)
   at

org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
 va:152)
   at

org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
 t.java:104)
   at

org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
   at

org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137

RE: Second Try: Can anyone explain this?

2004-06-16 Thread Shapira, Yoav

Hi,
That doesn't put the class in a package, it only moves the class around.
;(

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 2:07 PM
To: 'Tomcat Users List'
Subject: RE: Second Try: Can anyone explain this?

Tried that and got the same error.  This is what I did

jar -xf Xslt.jar JspXslt.class

Moved JspXslt.class to WEB-INF/classes

No change.

-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:05 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?


And I answered it here:
http://marc.theaimsgroup.com/?l=tomcat-userm=108723827315299w=2

-Tim

Worley Brent - bworle wrote:

 I posted this earlier and received a few leads on what to do, but
nothing
 worked.  I'm hoping a second look and explanation will help.

 The page that is causing the error (search.jsp) uses a taglib to load
 xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).
The
.tld
 file defines a tag named xslt that uses a class named JspXslt.
JspXslt
is
 located in WEB-INF/lib/Xslt.jar.

 So here are my questions:

 1.  Is anyone familiar with a standard Xslt.jar file that contains
the
 JspXslt.class object?
 2.  Why would Tomcat not find JspXslt.class?

 I've included the xml from the .tld file and the errors below.

 taglib
   tlibversion0.0/tlibversion
   jspversion1.0/jspversion
   shortnameacx/shortname
   tag
 namexslt/name
 tagclassJspXslt/tagclass
 bodycontentjsp/bodycontent
 attribute
   namexml/name
   requiredfalse/required
   rtexprvaluetrue/rtexprvalue
 /attribute
 attribute
   namexslt/name
   requiredtrue/required
   rtexprvaluetrue/rtexprvalue
 /attribute
 attribute
   namenobreak/name
   requiredfalse/required
   rtexprvaluetrue/rtexprvalue
 /attribute
   /tag
 /taglib

 org.apache.jasper.JasperException: Unable to compile class for JSP

 An error occurred at line: 55 in the jsp file: /search.jsp

 Generated servlet error:
 [javac] Compiling 1 source file


/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
 search_jsp.java:295: cannot resolve symbol
 symbol  : class JspXslt
 location: class org.apache.jsp.search_jsp
   JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
 _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
   ^



 An error occurred at line: 55 in the jsp file: /search.jsp

 Generated servlet error:

/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
 search_jsp.java:295: cannot resolve symbol
 symbol  : class JspXslt
 location: class org.apache.jsp.search_jsp
   JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
 _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
  ^



 An error occurred at line: 55 in the jsp file: /search.jsp

 Generated servlet error:

/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
 search_jsp.java:295: cannot resolve symbol
 symbol  : class JspXslt
 location: class org.apache.jsp.search_jsp
   JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
 _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);

 ^
 Note:

/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
 search_jsp.java uses or overrides a deprecated API.
 Note: Recompile with -deprecation for details.
 3 errors


  at

org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorH
andl
e
 r.java:83)
  at

org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.j
ava:
3
 06)
  at
 org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:398)
  at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:441)
  at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:422)
  at

org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.j
ava:
5
 07)
  at

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.j
ava:
2
 74)
  at

org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
  at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
  at

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic
atio
n
 FilterChain.java:237)
  at

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil
terC
h
 ain.java:157)
  at

org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVal
ve.j
a
 va:214)
  at

org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC
onte
x
 t.java:104)
  at

org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
520)
  at

org.apache.catalina.core.StandardContextValve.invokeInternal(StandardCo
ntex
t
 Valve.java:198)
  at

org.apache.catalina.core.StandardContextValve.invoke(StandardContextVal
ve.j
a
 va:152

RE: Second Try: Can anyone explain this?

2004-06-16 Thread Mike Curwen
so it's still not packaged then?  (it *must* be).


 -Original Message-
 From: Worley Brent - bworle [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, June 16, 2004 1:07 PM
 To: 'Tomcat Users List'
 Subject: RE: Second Try: Can anyone explain this?
 
 
 Tried that and got the same error.  This is what I did
 
 jar -xf Xslt.jar JspXslt.class
 
 Moved JspXslt.class to WEB-INF/classes
 
 No change.
 
 -Original Message-
 From: Tim Funk [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, June 16, 2004 1:05 PM
 To: Tomcat Users List
 Subject: Re: Second Try: Can anyone explain this?
 
 
 And I answered it here: 
 http://marc.theaimsgroup.com/?l=tomcat-userm=108723827315299w=2
 
 -Tim
 
 Worley Brent - bworle wrote:
 
  I posted this earlier and received a few leads on what to do, but 
  nothing worked.  I'm hoping a second look and explanation will help.
  
  The page that is causing the error (search.jsp) uses a 
 taglib to load 
  xslt.tld (%@ taglib prefix=acx 
 uri=WEB-INF/tld/xslt.tld %).  The
 .tld
  file defines a tag named xslt that uses a class named JspXslt.  
  JspXslt is located in WEB-INF/lib/Xslt.jar.
  
  So here are my questions:
  
  1.  Is anyone familiar with a standard Xslt.jar file that 
 contains the 
  JspXslt.class object? 2.  Why would Tomcat not find JspXslt.class?
  
  I've included the xml from the .tld file and the errors below.
  
  taglib
tlibversion0.0/tlibversion
jspversion1.0/jspversion
shortnameacx/shortname
tag
  namexslt/name
  tagclassJspXslt/tagclass
  bodycontentjsp/bodycontent
  attribute
namexml/name
requiredfalse/required
rtexprvaluetrue/rtexprvalue
  /attribute
  attribute
namexslt/name
requiredtrue/required
rtexprvaluetrue/rtexprvalue
  /attribute
  attribute
namenobreak/name
requiredfalse/required
rtexprvaluetrue/rtexprvalue
  /attribute
/tag
  /taglib
  
  org.apache.jasper.JasperException: Unable to compile class for JSP
  
  An error occurred at line: 55 in the jsp file: /search.jsp
  
  Generated servlet error:
  [javac] Compiling 1 source file
  
 
 /usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/o
 rg/apache/jsp/
  search_jsp.java:295: cannot resolve symbol
  symbol  : class JspXslt
  location: class org.apache.jsp.search_jsp
JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
  _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
^
  
  
  
  An error occurred at line: 55 in the jsp file: /search.jsp
  
  Generated servlet error:
 
 /usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/o
 rg/apache/jsp/
  search_jsp.java:295: cannot resolve symbol
  symbol  : class JspXslt
  location: class org.apache.jsp.search_jsp
JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
  _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
   ^
  
  
  
  An error occurred at line: 55 in the jsp file: /search.jsp
  
  Generated servlet error:
 
 /usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/o
 rg/apache/jsp/
  search_jsp.java:295: cannot resolve symbol
  symbol  : class JspXslt
  location: class org.apache.jsp.search_jsp
JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
  _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
   
  ^
  Note:
 
 /usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/o
 rg/apache/jsp/
  search_jsp.java uses or overrides a deprecated API.
  Note: Recompile with -deprecation for details.
  3 errors
  
  
  at
 
 org.apache.jasper.compiler.DefaultErrorHandler.javacError(Defa
 ultErrorHandle
  r.java:83)
  at
 
 org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDis
 patcher.java:3
  06)
  at
  org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:398)
  at 
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:441)
  at 
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:422)
  at
 
 org.apache.jasper.JspCompilationContext.compile(JspCompilation
 Context.java:5
  07)
  at
 
 org.apache.jasper.servlet.JspServletWrapper.service(JspServlet
 Wrapper.java:2
  74)
  at
  
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet
 .java:292)
  at 
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
  at
 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
 er(Application
  FilterChain.java:237)
  at
 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli
 cationFilterCh
  ain.java:157)
  at
 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardW
 rapperValve.ja
  va:214)
  at
 
 org.apache.catalina.core.StandardValveContext.invokeNext(Stand
 ardValveContex
  t.java:104)
  at
 
 org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
 ine.java:520)
  at
 
 org.apache.catalina.core.StandardContextValve.invokeInternal(S
 tandardContext

RE: Second Try: Can anyone explain this?

2004-06-16 Thread Worley Brent - bworle
Someone told you to put JspXslt.class in a package, IIRC.  I think
that's the problem.  Repackage the jar if you have to, for testing
purposes, and change the TLD to refer to the class by whatever package
you put it in, e.g. com.foo.bar.JspXslt.

The problem is the files in Xslt.jar are not our code.  We obtained that
code from somewhere else.  I asked one of the guys around the project when
development started.  He said that he thought it came from Xalan (which I
learned later it did not, or it came from a very, very old version that I'm
unfamiliar with).  Regardless, I have no access to the code to specify it to
a package.

Brent
-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:32 PM
To: 'Tomcat Users List'
Subject: Second Try: Can anyone explain this?

I posted this earlier and received a few leads on what to do, but
nothing
worked.  I'm hoping a second look and explanation will help.

The page that is causing the error (search.jsp) uses a taglib to load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).  The
.tld
file defines a tag named xslt that uses a class named JspXslt.  JspXslt
is
located in WEB-INF/lib/Xslt.jar.

So here are my questions:

1.  Is anyone familiar with a standard Xslt.jar file that contains the
JspXslt.class object?
2.  Why would Tomcat not find JspXslt.class?

I've included the xml from the .tld file and the errors below.

taglib
  tlibversion0.0/tlibversion
  jspversion1.0/jspversion
  shortnameacx/shortname
  tag
namexslt/name
tagclassJspXslt/tagclass
bodycontentjsp/bodycontent
attribute
  namexml/name
  requiredfalse/required
  rtexprvaluetrue/rtexprvalue
/attribute
attribute
  namexslt/name
  requiredtrue/required
  rtexprvaluetrue/rtexprvalue
/attribute
attribute
  namenobreak/name
  requiredfalse/required
  rtexprvaluetrue/rtexprvalue
/attribute
  /tag
/taglib

org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
[javac] Compiling 1 source file

/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
  ^



An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
 ^



An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
  JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);

^
Note:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java uses or overrides a deprecated API.
Note: Recompile with -deprecation for details.
3 errors


   at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorH
andl
e
r.java:83)
   at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.j
ava:
3
06)
   at
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:398)
   at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:441)
   at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:422)
   at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.j
ava:
5
07)
   at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.j
ava:
2
74)
   at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292
)
   at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
   at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic
atio
n
FilterChain.java:237)
   at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil
terC
h
ain.java:157)
   at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVal
ve.j
a
va:214)
   at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC
onte
x
t.java:104)
   at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
520)
   at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardCo
ntex
t
Valve.java:198)
   at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextVal
ve.j
a
va:152

Re: Second Try: Can anyone explain this?

2004-06-16 Thread Tim Funk
Then your out of luck. The java from a JSP page is always placed into a 
package. Becuase of this, you can't have packageless classes.

You alternative is to hack jasper to not use the package statement but doing 
so will be harder than fixing your code.


-Tim
Worley Brent - bworle wrote:
Someone told you to put JspXslt.class in a package, IIRC.  I think
that's the problem.  Repackage the jar if you have to, for testing
purposes, and change the TLD to refer to the class by whatever package
you put it in, e.g. com.foo.bar.JspXslt.

The problem is the files in Xslt.jar are not our code.  We obtained that
code from somewhere else.  I asked one of the guys around the project when
development started.  He said that he thought it came from Xalan (which I
learned later it did not, or it came from a very, very old version that I'm
unfamiliar with).  Regardless, I have no access to the code to specify it to
a package.
Brent
-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:32 PM
To: 'Tomcat Users List'
Subject: Second Try: Can anyone explain this?
I posted this earlier and received a few leads on what to do, but
nothing
worked.  I'm hoping a second look and explanation will help.
The page that is causing the error (search.jsp) uses a taglib to load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).  The
.tld
file defines a tag named xslt that uses a class named JspXslt.  JspXslt
is
located in WEB-INF/lib/Xslt.jar.
So here are my questions:
1.  Is anyone familiar with a standard Xslt.jar file that contains the
JspXslt.class object?
2.  Why would Tomcat not find JspXslt.class?
I've included the xml from the .tld file and the errors below.
taglib
tlibversion0.0/tlibversion
jspversion1.0/jspversion
shortnameacx/shortname
tag
  namexslt/name
  tagclassJspXslt/tagclass
  bodycontentjsp/bodycontent
  attribute
namexml/name
requiredfalse/required
rtexprvaluetrue/rtexprvalue
  /attribute
  attribute
namexslt/name
requiredtrue/required
rtexprvaluetrue/rtexprvalue
  /attribute
  attribute
namenobreak/name
requiredfalse/required
rtexprvaluetrue/rtexprvalue
  /attribute
/tag
/taglib
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: 55 in the jsp file: /search.jsp
Generated servlet error:
  [javac] Compiling 1 source file
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
^

An error occurred at line: 55 in the jsp file: /search.jsp
Generated servlet error:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
   ^

An error occurred at line: 55 in the jsp file: /search.jsp
Generated servlet error:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
^
Note:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java uses or overrides a deprecated API.
Note: Recompile with -deprecation for details.
3 errors
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorH
andl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Second Try: Can anyone explain this?

2004-06-16 Thread Worley Brent - bworle
Is it possible to extract the class files and give them a package-like
structure without the keyword package being in the code?

For example, there are 3 .class files in the jar.  Could I create a
directory called Xslt, copy those classes within it, and then jar the
directory and use a import Xslt.*?

I'm fairly new to Java and do not know if this hack would work.

-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:24 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?


Then your out of luck. The java from a JSP page is always placed into a 
package. Becuase of this, you can't have packageless classes.

You alternative is to hack jasper to not use the package statement but doing

so will be harder than fixing your code.



-Tim

Worley Brent - bworle wrote:

Someone told you to put JspXslt.class in a package, IIRC.  I think
that's the problem.  Repackage the jar if you have to, for testing
purposes, and change the TLD to refer to the class by whatever package
you put it in, e.g. com.foo.bar.JspXslt.
 
 
 The problem is the files in Xslt.jar are not our code.  We obtained that
 code from somewhere else.  I asked one of the guys around the project when
 development started.  He said that he thought it came from Xalan (which I
 learned later it did not, or it came from a very, very old version that
I'm
 unfamiliar with).  Regardless, I have no access to the code to specify it
to
 a package.
 
 Brent
 
-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:32 PM
To: 'Tomcat Users List'
Subject: Second Try: Can anyone explain this?

I posted this earlier and received a few leads on what to do, but
 
 nothing
 
worked.  I'm hoping a second look and explanation will help.

The page that is causing the error (search.jsp) uses a taglib to load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).  The
 
 .tld
 
file defines a tag named xslt that uses a class named JspXslt.  JspXslt
 
 is
 
located in WEB-INF/lib/Xslt.jar.

So here are my questions:

1.  Is anyone familiar with a standard Xslt.jar file that contains the
JspXslt.class object?
2.  Why would Tomcat not find JspXslt.class?

I've included the xml from the .tld file and the errors below.

taglib
 tlibversion0.0/tlibversion
 jspversion1.0/jspversion
 shortnameacx/shortname
 tag
   namexslt/name
   tagclassJspXslt/tagclass
   bodycontentjsp/bodycontent
   attribute
 namexml/name
 requiredfalse/required
 rtexprvaluetrue/rtexprvalue
   /attribute
   attribute
 namexslt/name
 requiredtrue/required
 rtexprvaluetrue/rtexprvalue
   /attribute
   attribute
 namenobreak/name
 requiredfalse/required
 rtexprvaluetrue/rtexprvalue
   /attribute
 /tag
/taglib

org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
   [javac] Compiling 1 source file

/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
 JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
 ^



An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
 JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
^



An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
 JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);

^
Note:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java uses or overrides a deprecated API.
Note: Recompile with -deprecation for details.
3 errors


  at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorH
 
 andl
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


**
The information contained in this communication is
confidential, is intended only for the use of the recipient
named above, and may be legally privileged.
If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, 
distribution, or copying of this communication is strictly
prohibited.
If you have received this communication in error,
please

RE: Second Try: Can anyone explain this?

2004-06-16 Thread Shapira, Yoav

Hi,
No, this wouldn't work, because the package declaration within the class
must match.

You're left looking at indirect options:
- Consider a replacement to Xslt.class (another product maybe)
- Consider contacting the authors of Xslt.class and/or opening a support
ticket if applicable for them to put their class in a package
- Consider writing a replacement yourself
- Consider bytecode manipulation, e.g. BCEL, to see if you can
retroactively put the class in a different package

Ooh, one more idea: try leaving the Xslt class as-is, in its jar, in
WEB-INF/lib, and instead of importing Xslt import org.apache.jasper.Xslt
(and change the tld file's class attribute name to match).

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 2:28 PM
To: 'Tomcat Users List'
Subject: RE: Second Try: Can anyone explain this?

Is it possible to extract the class files and give them a
package-like
structure without the keyword package being in the code?

For example, there are 3 .class files in the jar.  Could I create a
directory called Xslt, copy those classes within it, and then jar the
directory and use a import Xslt.*?

I'm fairly new to Java and do not know if this hack would work.

-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:24 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?


Then your out of luck. The java from a JSP page is always placed into a
package. Becuase of this, you can't have packageless classes.

You alternative is to hack jasper to not use the package statement but
doing

so will be harder than fixing your code.



-Tim

Worley Brent - bworle wrote:

Someone told you to put JspXslt.class in a package, IIRC.  I think
that's the problem.  Repackage the jar if you have to, for testing
purposes, and change the TLD to refer to the class by whatever
package
you put it in, e.g. com.foo.bar.JspXslt.


 The problem is the files in Xslt.jar are not our code.  We obtained
that
 code from somewhere else.  I asked one of the guys around the project
when
 development started.  He said that he thought it came from Xalan
(which I
 learned later it did not, or it came from a very, very old version
that
I'm
 unfamiliar with).  Regardless, I have no access to the code to
specify it
to
 a package.

 Brent

-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:32 PM
To: 'Tomcat Users List'
Subject: Second Try: Can anyone explain this?

I posted this earlier and received a few leads on what to do, but

 nothing

worked.  I'm hoping a second look and explanation will help.

The page that is causing the error (search.jsp) uses a taglib to load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).
The

 .tld

file defines a tag named xslt that uses a class named JspXslt.
JspXslt

 is

located in WEB-INF/lib/Xslt.jar.

So here are my questions:

1.  Is anyone familiar with a standard Xslt.jar file that contains
the
JspXslt.class object?
2.  Why would Tomcat not find JspXslt.class?

I've included the xml from the .tld file and the errors below.

taglib
 tlibversion0.0/tlibversion
 jspversion1.0/jspversion
 shortnameacx/shortname
 tag
   namexslt/name
   tagclassJspXslt/tagclass
   bodycontentjsp/bodycontent
   attribute
 namexml/name
 requiredfalse/required
 rtexprvaluetrue/rtexprvalue
   /attribute
   attribute
 namexslt/name
 requiredtrue/required
 rtexprvaluetrue/rtexprvalue
   /attribute
   attribute
 namenobreak/name
 requiredfalse/required
 rtexprvaluetrue/rtexprvalue
   /attribute
 /tag
/taglib

org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
   [javac] Compiling 1 source file

/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
 JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
 ^



An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
 JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
^



An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java:295: cannot resolve symbol
symbol  : class JspXslt
location: class org.apache.jsp.search_jsp
 JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
_jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class

Re: Second Try: Can anyone explain this?

2004-06-16 Thread Filip Hanik - Dev
the first line in your .java file should be

package mypackage;

when you compile it, with the -d . option, it will put it in a folder called 
mypackage

Filip

- Original Message - 
From: Mike Curwen [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:12 PM
Subject: RE: Second Try: Can anyone explain this?


 so it's still not packaged then?  (it *must* be).
 
 
  -Original Message-
  From: Worley Brent - bworle [mailto:[EMAIL PROTECTED] 
  Sent: Wednesday, June 16, 2004 1:07 PM
  To: 'Tomcat Users List'
  Subject: RE: Second Try: Can anyone explain this?
  
  
  Tried that and got the same error.  This is what I did
  
  jar -xf Xslt.jar JspXslt.class
  
  Moved JspXslt.class to WEB-INF/classes
  
  No change.
  
  -Original Message-
  From: Tim Funk [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, June 16, 2004 1:05 PM
  To: Tomcat Users List
  Subject: Re: Second Try: Can anyone explain this?
  
  
  And I answered it here: 
  http://marc.theaimsgroup.com/?l=tomcat-userm=108723827315299w=2
  
  -Tim
  
  Worley Brent - bworle wrote:
  
   I posted this earlier and received a few leads on what to do, but 
   nothing worked.  I'm hoping a second look and explanation will help.
   
   The page that is causing the error (search.jsp) uses a 
  taglib to load 
   xslt.tld (%@ taglib prefix=acx 
  uri=WEB-INF/tld/xslt.tld %).  The
  .tld
   file defines a tag named xslt that uses a class named JspXslt.  
   JspXslt is located in WEB-INF/lib/Xslt.jar.
   
   So here are my questions:
   
   1.  Is anyone familiar with a standard Xslt.jar file that 
  contains the 
   JspXslt.class object? 2.  Why would Tomcat not find JspXslt.class?
   
   I've included the xml from the .tld file and the errors below.
   
   taglib
 tlibversion0.0/tlibversion
 jspversion1.0/jspversion
 shortnameacx/shortname
 tag
   namexslt/name
   tagclassJspXslt/tagclass
   bodycontentjsp/bodycontent
   attribute
 namexml/name
 requiredfalse/required
 rtexprvaluetrue/rtexprvalue
   /attribute
   attribute
 namexslt/name
 requiredtrue/required
 rtexprvaluetrue/rtexprvalue
   /attribute
   attribute
 namenobreak/name
 requiredfalse/required
 rtexprvaluetrue/rtexprvalue
   /attribute
 /tag
   /taglib
   
   org.apache.jasper.JasperException: Unable to compile class for JSP
   
   An error occurred at line: 55 in the jsp file: /search.jsp
   
   Generated servlet error:
   [javac] Compiling 1 source file
   
  
  /usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/o
  rg/apache/jsp/
   search_jsp.java:295: cannot resolve symbol
   symbol  : class JspXslt
   location: class org.apache.jsp.search_jsp
 JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
   _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
 ^
   
   
   
   An error occurred at line: 55 in the jsp file: /search.jsp
   
   Generated servlet error:
  
  /usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/o
  rg/apache/jsp/
   search_jsp.java:295: cannot resolve symbol
   symbol  : class JspXslt
   location: class org.apache.jsp.search_jsp
 JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
   _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);
^
   
   
   
   An error occurred at line: 55 in the jsp file: /search.jsp
   
   Generated servlet error:
  
  /usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/o
  rg/apache/jsp/
   search_jsp.java:295: cannot resolve symbol
   symbol  : class JspXslt
   location: class org.apache.jsp.search_jsp
 JspXslt _jspx_th_acx_xslt_0 = (JspXslt)
   _jspx_tagPool_acx_xslt_xslt_xml.get(JspXslt.class);

   ^
   Note:
  
  /usr/local/jakarta-tomcat-5.0.24/work/Catalina/localhost/SIT/o
  rg/apache/jsp/
   search_jsp.java uses or overrides a deprecated API.
   Note: Recompile with -deprecation for details.
   3 errors
   
   
   at
  
  org.apache.jasper.compiler.DefaultErrorHandler.javacError(Defa
  ultErrorHandle
   r.java:83)
   at
  
  org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDis
  patcher.java:3
   06)
   at
   org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:398)
   at 
  org.apache.jasper.compiler.Compiler.compile(Compiler.java:441)
   at 
  org.apache.jasper.compiler.Compiler.compile(Compiler.java:422)
   at
  
  org.apache.jasper.JspCompilationContext.compile(JspCompilation
  Context.java:5
   07)
   at
  
  org.apache.jasper.servlet.JspServletWrapper.service(JspServlet
  Wrapper.java:2
   74)
   at
   
  org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet
  .java:292)
   at 
  org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
   at
  
  org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
  er(Application
   FilterChain.java:237

RE: Second Try: Can anyone explain this?

2004-06-16 Thread Worley Brent - bworle
Yoav,

Thanks for your suggestion.  It at least got me a little further.  However,
now I'm getting this error:

org.apache.jasper.JasperException: /search.jsp(56,2) Unable to load tag
handler class org.apache.jasper.Xslt for tag acx:xslt
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.
java:39)

I want to make sure I did things correctly.  This is what I did:

1.  In search.jsp, I added this line:

%@ page import=org.apache.jasper.Xslt %

2.  In my xslt.tld file, I did the following:

taglib
  tlibversion0.0/tlibversion
  jspversion1.0/jspversion
  shortnameacx/shortname
  tag
namexslt/name
tagclassorg.apache.jasper.Xslt/tagclass
bodycontentjsp/bodycontent
...

Is there anything else that needs to be changed?

Thanks 

Brent
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:41 PM
To: Tomcat Users List
Subject: RE: Second Try: Can anyone explain this?



Hi,
No, this wouldn't work, because the package declaration within the class
must match.

You're left looking at indirect options:
- Consider a replacement to Xslt.class (another product maybe)
- Consider contacting the authors of Xslt.class and/or opening a support
ticket if applicable for them to put their class in a package
- Consider writing a replacement yourself
- Consider bytecode manipulation, e.g. BCEL, to see if you can
retroactively put the class in a different package

Ooh, one more idea: try leaving the Xslt class as-is, in its jar, in
WEB-INF/lib, and instead of importing Xslt import org.apache.jasper.Xslt
(and change the tld file's class attribute name to match).

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 2:28 PM
To: 'Tomcat Users List'
Subject: RE: Second Try: Can anyone explain this?

Is it possible to extract the class files and give them a
package-like
structure without the keyword package being in the code?

For example, there are 3 .class files in the jar.  Could I create a
directory called Xslt, copy those classes within it, and then jar the
directory and use a import Xslt.*?

I'm fairly new to Java and do not know if this hack would work.

-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:24 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?


Then your out of luck. The java from a JSP page is always placed into a
package. Becuase of this, you can't have packageless classes.

You alternative is to hack jasper to not use the package statement but
doing

so will be harder than fixing your code.



-Tim

Worley Brent - bworle wrote:

Someone told you to put JspXslt.class in a package, IIRC.  I think
that's the problem.  Repackage the jar if you have to, for testing
purposes, and change the TLD to refer to the class by whatever
package
you put it in, e.g. com.foo.bar.JspXslt.


 The problem is the files in Xslt.jar are not our code.  We obtained
that
 code from somewhere else.  I asked one of the guys around the project
when
 development started.  He said that he thought it came from Xalan
(which I
 learned later it did not, or it came from a very, very old version
that
I'm
 unfamiliar with).  Regardless, I have no access to the code to
specify it
to
 a package.

 Brent

-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:32 PM
To: 'Tomcat Users List'
Subject: Second Try: Can anyone explain this?

I posted this earlier and received a few leads on what to do, but

 nothing

worked.  I'm hoping a second look and explanation will help.

The page that is causing the error (search.jsp) uses a taglib to load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).
The

 .tld

file defines a tag named xslt that uses a class named JspXslt.
JspXslt

 is

located in WEB-INF/lib/Xslt.jar.

So here are my questions:

1.  Is anyone familiar with a standard Xslt.jar file that contains
the
JspXslt.class object?
2.  Why would Tomcat not find JspXslt.class?

I've included the xml from the .tld file and the errors below.

taglib
 tlibversion0.0/tlibversion
 jspversion1.0/jspversion
 shortnameacx/shortname
 tag
   namexslt/name
   tagclassJspXslt/tagclass
   bodycontentjsp/bodycontent
   attribute
 namexml/name
 requiredfalse/required
 rtexprvaluetrue/rtexprvalue
   /attribute
   attribute
 namexslt/name
 requiredtrue/required
 rtexprvaluetrue/rtexprvalue
   /attribute
   attribute
 namenobreak/name
 requiredfalse/required
 rtexprvaluetrue/rtexprvalue
   /attribute
 /tag
/taglib

org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: 55 in the jsp file: /search.jsp

Generated servlet error:
   [javac] Compiling 1 source file

/usr/local/jakarta-tomcat-
5.0.24/work/Catalina/localhost/SIT/org/apache/jsp/
search_jsp.java

Re: Second Try: Can anyone explain this?

2004-06-16 Thread Jérôme Duval
Then your out of luck. The java from a JSP page is always placed into a
package. Becuase of this, you can't have packageless classes.

Tim, perhaps I don't understand what you are saying correctly, but I have no
trouble using classes that are not in a package in my application. Once I am
done developing they will be in a package, but for now, I don't see the
point and my app works fine.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Second Try: Can anyone explain this?

2004-06-16 Thread Shapira, Yoav

Hi,
Oh well, that was worth a shot.  You did the two steps I suggested, it
didn't work, that's too bad.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 3:03 PM
To: 'Tomcat Users List'
Subject: RE: Second Try: Can anyone explain this?

Yoav,

Thanks for your suggestion.  It at least got me a little further.
However,
now I'm getting this error:

org.apache.jasper.JasperException: /search.jsp(56,2) Unable to load tag
handler class org.apache.jasper.Xslt for tag acx:xslt
   at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHan
dler
.
java:39)

I want to make sure I did things correctly.  This is what I did:

1.  In search.jsp, I added this line:

%@ page import=org.apache.jasper.Xslt %

2.  In my xslt.tld file, I did the following:

taglib
  tlibversion0.0/tlibversion
  jspversion1.0/jspversion
  shortnameacx/shortname
  tag
namexslt/name
tagclassorg.apache.jasper.Xslt/tagclass
bodycontentjsp/bodycontent
...

Is there anything else that needs to be changed?

Thanks

Brent
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:41 PM
To: Tomcat Users List
Subject: RE: Second Try: Can anyone explain this?



Hi,
No, this wouldn't work, because the package declaration within the
class
must match.

You're left looking at indirect options:
- Consider a replacement to Xslt.class (another product maybe)
- Consider contacting the authors of Xslt.class and/or opening a
support
ticket if applicable for them to put their class in a package
- Consider writing a replacement yourself
- Consider bytecode manipulation, e.g. BCEL, to see if you can
retroactively put the class in a different package

Ooh, one more idea: try leaving the Xslt class as-is, in its jar, in
WEB-INF/lib, and instead of importing Xslt import
org.apache.jasper.Xslt
(and change the tld file's class attribute name to match).

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 2:28 PM
To: 'Tomcat Users List'
Subject: RE: Second Try: Can anyone explain this?

Is it possible to extract the class files and give them a
package-like
structure without the keyword package being in the code?

For example, there are 3 .class files in the jar.  Could I create a
directory called Xslt, copy those classes within it, and then jar
the
directory and use a import Xslt.*?

I'm fairly new to Java and do not know if this hack would work.

-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:24 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?


Then your out of luck. The java from a JSP page is always placed into
a
package. Becuase of this, you can't have packageless classes.

You alternative is to hack jasper to not use the package statement but
doing

so will be harder than fixing your code.



-Tim

Worley Brent - bworle wrote:

Someone told you to put JspXslt.class in a package, IIRC.  I think
that's the problem.  Repackage the jar if you have to, for testing
purposes, and change the TLD to refer to the class by whatever
package
you put it in, e.g. com.foo.bar.JspXslt.


 The problem is the files in Xslt.jar are not our code.  We obtained
that
 code from somewhere else.  I asked one of the guys around the
project
when
 development started.  He said that he thought it came from Xalan
(which I
 learned later it did not, or it came from a very, very old version
that
I'm
 unfamiliar with).  Regardless, I have no access to the code to
specify it
to
 a package.

 Brent

-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:32 PM
To: 'Tomcat Users List'
Subject: Second Try: Can anyone explain this?

I posted this earlier and received a few leads on what to do, but

 nothing

worked.  I'm hoping a second look and explanation will help.

The page that is causing the error (search.jsp) uses a taglib to
load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).
The

 .tld

file defines a tag named xslt that uses a class named JspXslt.
JspXslt

 is

located in WEB-INF/lib/Xslt.jar.

So here are my questions:

1.  Is anyone familiar with a standard Xslt.jar file that contains
the
JspXslt.class object?
2.  Why would Tomcat not find JspXslt.class?

I've included the xml from the .tld file and the errors below.

taglib
 tlibversion0.0/tlibversion
 jspversion1.0/jspversion
 shortnameacx/shortname
 tag
   namexslt/name
   tagclassJspXslt/tagclass
   bodycontentjsp/bodycontent
   attribute
 namexml/name
 requiredfalse/required
 rtexprvaluetrue/rtexprvalue
   /attribute
   attribute
 namexslt/name
 requiredtrue/required
 rtexprvaluetrue/rtexprvalue
   /attribute
   attribute
 namenobreak/name
 requiredfalse/required

RE: Second Try: Can anyone explain this?

2004-06-16 Thread Worley Brent - bworle
I have xalan installed.  Could I use it to accomplish the same thing (which
all the page appears to be doing is reading in an xsl file and translating
it to a jsp).

-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 2:04 PM
To: Tomcat Users List
Subject: RE: Second Try: Can anyone explain this?



Hi,
Oh well, that was worth a shot.  You did the two steps I suggested, it
didn't work, that's too bad.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 3:03 PM
To: 'Tomcat Users List'
Subject: RE: Second Try: Can anyone explain this?

Yoav,

Thanks for your suggestion.  It at least got me a little further.
However,
now I'm getting this error:

org.apache.jasper.JasperException: /search.jsp(56,2) Unable to load tag
handler class org.apache.jasper.Xslt for tag acx:xslt
   at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHan
dler
.
java:39)

I want to make sure I did things correctly.  This is what I did:

1.  In search.jsp, I added this line:

%@ page import=org.apache.jasper.Xslt %

2.  In my xslt.tld file, I did the following:

taglib
  tlibversion0.0/tlibversion
  jspversion1.0/jspversion
  shortnameacx/shortname
  tag
namexslt/name
tagclassorg.apache.jasper.Xslt/tagclass
bodycontentjsp/bodycontent
...

Is there anything else that needs to be changed?

Thanks

Brent
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:41 PM
To: Tomcat Users List
Subject: RE: Second Try: Can anyone explain this?



Hi,
No, this wouldn't work, because the package declaration within the
class
must match.

You're left looking at indirect options:
- Consider a replacement to Xslt.class (another product maybe)
- Consider contacting the authors of Xslt.class and/or opening a
support
ticket if applicable for them to put their class in a package
- Consider writing a replacement yourself
- Consider bytecode manipulation, e.g. BCEL, to see if you can
retroactively put the class in a different package

Ooh, one more idea: try leaving the Xslt class as-is, in its jar, in
WEB-INF/lib, and instead of importing Xslt import
org.apache.jasper.Xslt
(and change the tld file's class attribute name to match).

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 2:28 PM
To: 'Tomcat Users List'
Subject: RE: Second Try: Can anyone explain this?

Is it possible to extract the class files and give them a
package-like
structure without the keyword package being in the code?

For example, there are 3 .class files in the jar.  Could I create a
directory called Xslt, copy those classes within it, and then jar
the
directory and use a import Xslt.*?

I'm fairly new to Java and do not know if this hack would work.

-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:24 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?


Then your out of luck. The java from a JSP page is always placed into
a
package. Becuase of this, you can't have packageless classes.

You alternative is to hack jasper to not use the package statement but
doing

so will be harder than fixing your code.



-Tim

Worley Brent - bworle wrote:

Someone told you to put JspXslt.class in a package, IIRC.  I think
that's the problem.  Repackage the jar if you have to, for testing
purposes, and change the TLD to refer to the class by whatever
package
you put it in, e.g. com.foo.bar.JspXslt.


 The problem is the files in Xslt.jar are not our code.  We obtained
that
 code from somewhere else.  I asked one of the guys around the
project
when
 development started.  He said that he thought it came from Xalan
(which I
 learned later it did not, or it came from a very, very old version
that
I'm
 unfamiliar with).  Regardless, I have no access to the code to
specify it
to
 a package.

 Brent

-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:32 PM
To: 'Tomcat Users List'
Subject: Second Try: Can anyone explain this?

I posted this earlier and received a few leads on what to do, but

 nothing

worked.  I'm hoping a second look and explanation will help.

The page that is causing the error (search.jsp) uses a taglib to
load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).
The

 .tld

file defines a tag named xslt that uses a class named JspXslt.
JspXslt

 is

located in WEB-INF/lib/Xslt.jar.

So here are my questions:

1.  Is anyone familiar with a standard Xslt.jar file that contains
the
JspXslt.class object?
2.  Why would Tomcat not find JspXslt.class?

I've included the xml from the .tld file and the errors below.

taglib
 tlibversion0.0/tlibversion
 jspversion1.0/jspversion
 shortnameacx/shortname

RE: Second Try: Can anyone explain this?

2004-06-16 Thread Shapira, Yoav

Hi,
Ask on the xalan-user mailing list, I'm nearly sure the answer is yes,
and they'll give more detailed help there.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 3:18 PM
To: 'Tomcat Users List'
Subject: RE: Second Try: Can anyone explain this?

I have xalan installed.  Could I use it to accomplish the same thing
(which
all the page appears to be doing is reading in an xsl file and
translating
it to a jsp).

-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 2:04 PM
To: Tomcat Users List
Subject: RE: Second Try: Can anyone explain this?



Hi,
Oh well, that was worth a shot.  You did the two steps I suggested, it
didn't work, that's too bad.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 3:03 PM
To: 'Tomcat Users List'
Subject: RE: Second Try: Can anyone explain this?

Yoav,

Thanks for your suggestion.  It at least got me a little further.
However,
now I'm getting this error:

org.apache.jasper.JasperException: /search.jsp(56,2) Unable to load
tag
handler class org.apache.jasper.Xslt for tag acx:xslt
  at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHa
n
dler
.
java:39)

I want to make sure I did things correctly.  This is what I did:

1.  In search.jsp, I added this line:

%@ page import=org.apache.jasper.Xslt %

2.  In my xslt.tld file, I did the following:

taglib
  tlibversion0.0/tlibversion
  jspversion1.0/jspversion
  shortnameacx/shortname
  tag
namexslt/name
tagclassorg.apache.jasper.Xslt/tagclass
bodycontentjsp/bodycontent
...

Is there anything else that needs to be changed?

Thanks

Brent
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:41 PM
To: Tomcat Users List
Subject: RE: Second Try: Can anyone explain this?



Hi,
No, this wouldn't work, because the package declaration within the
class
must match.

You're left looking at indirect options:
- Consider a replacement to Xslt.class (another product maybe)
- Consider contacting the authors of Xslt.class and/or opening a
support
ticket if applicable for them to put their class in a package
- Consider writing a replacement yourself
- Consider bytecode manipulation, e.g. BCEL, to see if you can
retroactively put the class in a different package

Ooh, one more idea: try leaving the Xslt class as-is, in its jar, in
WEB-INF/lib, and instead of importing Xslt import
org.apache.jasper.Xslt
(and change the tld file's class attribute name to match).

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 2:28 PM
To: 'Tomcat Users List'
Subject: RE: Second Try: Can anyone explain this?

Is it possible to extract the class files and give them a
package-like
structure without the keyword package being in the code?

For example, there are 3 .class files in the jar.  Could I create a
directory called Xslt, copy those classes within it, and then jar
the
directory and use a import Xslt.*?

I'm fairly new to Java and do not know if this hack would work.

-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:24 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?


Then your out of luck. The java from a JSP page is always placed into
a
package. Becuase of this, you can't have packageless classes.

You alternative is to hack jasper to not use the package statement
but
doing

so will be harder than fixing your code.



-Tim

Worley Brent - bworle wrote:

Someone told you to put JspXslt.class in a package, IIRC.  I think
that's the problem.  Repackage the jar if you have to, for testing
purposes, and change the TLD to refer to the class by whatever
package
you put it in, e.g. com.foo.bar.JspXslt.


 The problem is the files in Xslt.jar are not our code.  We obtained
that
 code from somewhere else.  I asked one of the guys around the
project
when
 development started.  He said that he thought it came from Xalan
(which I
 learned later it did not, or it came from a very, very old version
that
I'm
 unfamiliar with).  Regardless, I have no access to the code to
specify it
to
 a package.

 Brent

-Original Message-
From: Worley Brent - bworle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 1:32 PM
To: 'Tomcat Users List'
Subject: Second Try: Can anyone explain this?

I posted this earlier and received a few leads on what to do, but

 nothing

worked.  I'm hoping a second look and explanation will help.

The page that is causing the error (search.jsp) uses a taglib to
load
xslt.tld (%@ taglib prefix=acx uri=WEB-INF/tld/xslt.tld %).
The

 .tld

file defines a tag named xslt that uses a class named JspXslt

Re: Second Try: Can anyone explain this?

2004-06-16 Thread Tim Funk
It a 1.4 JVM thing (not 1.3)
Consider class Cowbell in package more.
file: Cowbell.java
--
package more;
import Fever
public class Cowbell {
}
Then consider a class called Fever without a package.
file: Fever.java
--
public class Fever {
}
Now try to compile them. The compiler will barf because it can't find Fever 
because its packageless.

$JAVA_HOME/bin/javac -d out/ Fever.java more/Cowbell.java
You should get:
more/Cowbell.java:3: '.' expected
import Fever;
^
1 error
-Tim
Jérôme Duval wrote:
Then your out of luck. The java from a JSP page is always placed into a
package. Becuase of this, you can't have packageless classes.
Tim, perhaps I don't understand what you are saying correctly, but I have no
trouble using classes that are not in a package in my application. Once I am
done developing they will be in a package, but for now, I don't see the
point and my app works fine.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Second Try: Can anyone explain this?

2004-06-16 Thread Jérôme Duval
Now I see what you mean. It's just that I never develop with classes that
reuse code that is located in other folders, so the classloader can always
find the classes I need. 

-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 16, 2004 3:21 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?

It a 1.4 JVM thing (not 1.3)


Consider class Cowbell in package more.

file: Cowbell.java
--
package more;
import Fever
public class Cowbell {
}

Then consider a class called Fever without a package.
file: Fever.java
--
public class Fever {
}

Now try to compile them. The compiler will barf because it can't find Fever
because its packageless.

$JAVA_HOME/bin/javac -d out/ Fever.java more/Cowbell.java

You should get:
more/Cowbell.java:3: '.' expected
import Fever;
 ^
1 error

-Tim

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Second Try: Can anyone explain this?

2004-06-16 Thread Shapira, Yoav

Hi,

Now I see what you mean. It's just that I never develop with classes
that
reuse code that is located in other folders, so the classloader can
always
find the classes I need.

Wow ;)

Yoav


-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 3:21 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?

It a 1.4 JVM thing (not 1.3)


Consider class Cowbell in package more.

file: Cowbell.java
--
package more;
import Fever
public class Cowbell {
}

Then consider a class called Fever without a package.
file: Fever.java
--
public class Fever {
}

Now try to compile them. The compiler will barf because it can't find
Fever
because its packageless.

$JAVA_HOME/bin/javac -d out/ Fever.java more/Cowbell.java

You should get:
more/Cowbell.java:3: '.' expected
import Fever;
 ^
1 error

-Tim

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Second Try: Can anyone explain this?

2004-06-16 Thread Wade Chandler
Shapira, Yoav wrote:
Hi,

Now I see what you mean. It's just that I never develop with classes
that
reuse code that is located in other folders, so the classloader can
always
find the classes I need.

Wow ;)
Yoav

-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 3:21 PM
To: Tomcat Users List
Subject: Re: Second Try: Can anyone explain this?
It a 1.4 JVM thing (not 1.3)
Consider class Cowbell in package more.
file: Cowbell.java
--
package more;
import Fever
public class Cowbell {
}
Then consider a class called Fever without a package.
file: Fever.java
--
public class Fever {
}
Now try to compile them. The compiler will barf because it can't find
Fever
because its packageless.
$JAVA_HOME/bin/javac -d out/ Fever.java more/Cowbell.java
You should get:
more/Cowbell.java:3: '.' expected
import Fever;
   ^
1 error
-Tim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This e-mail, including any attachments, is a confidential business communication, 
and may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ditto.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]