date:20031104

Looking For Tomcat5 JK Doc

2003-11-04 Thread Simon Chou

tomcat user,

I've been looking for the document to configure AJP connecting
Tomcat 5.0.7 with Apache 2.0.47.  The on-line JK Documentation
link keep referring me to the binary distribution page of mod_jk
1.2.5
without the configuration document.

I've also read tons of helpful pages for the previous versions
of
Tomcat from the google search and still unable to get the AJP
right.  If someone has configured the Tomcat 5.0.7 + Apache
2.0.47 +
mod_jk 1.2.5 successfully, please point me the direction for
obtaining the right configuration documentation.

Thanks,

SC


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

[Fwd: Struts - Parsing error processing resource path]

2003-11-04 Thread Vijaykumar

 Original Message 
Subject: Struts - Parsing error processing resource path
Date: Tue, 04 Nov 2003 10:13:20 +0530
From: Vijaykumar [EMAIL PROTECTED]
Reply-To: Struts Users Mailing List [EMAIL PROTECTED]
To: Struts [EMAIL PROTECTED]

Hi all,

  I am a newbie in struts.  I am using Tomcat 4.0.1, I get the 
following error message while starting the Tomcat

D:\jakarta-tomcat-4.0.1\bincatalina run
Using CATALINA_BASE: ..
Using CATALINA_HOME: ..
Using CLASSPATH: ..\bin\bootstrap.jar;d:\jdk1.3.1\lib\tools.jar
Using JAVA_HOME: d:\jdk1.3.1
Starting service Tomcat-Standalone
Apache Tomcat/4.0.1
[INFO] PropertyMessageResources - -Initializing, 
config='org.apache.struts.util.LocalStrings', returnNull=true
[INFO] PropertyMessageResources - -Initializing, 
config='org.apache.struts.action.ActionResources', returnNull=true
[ERROR] ActionServlet - -Parsing error processing resource path  
java.lang.NullPointerExc
eption
  at 
org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:941) 

  at 
org.apache.struts.action.ActionServlet.init(ActionServlet.java:465)
  at javax.servlet.GenericServlet.init(GenericServlet.java:258)
  at 
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:852)
  at 
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3267) 

  at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:3384)
  at 
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
  at 
org.apache.catalina.core.StandardHost.start(StandardHost.java:612)
  at 
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
  at 
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:307)
  at 
org.apache.catalina.core.StandardService.start(StandardService.java:388)
  at 
org.apache.catalina.core.StandardServer.start(StandardServer.java:505)
  at org.apache.catalina.startup.Catalina.start(Catalina.java:776)
  at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
  at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
  at java.lang.reflect.Method.invoke(Native Method)
  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)

Starting service Tomcat-Apache
Apache Tomcat/4.0.1
can anyone help me plz.

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

--
Your favorite stores, helpful shopping tools and great gift ideas. 
Experience the convenience of buying online with [EMAIL PROTECTED] 
http://shopnow.netscape.com/

Re: xhtml and Internet Explorer

2003-11-04 Thread Rodrigo Ruiz

Well, not necessarily unreadable, just different ;-)

I usually play with the tag delimiters to allow some readability. For
example, my JSPs usually begin with something like:

[EMAIL PROTECTED] contentType=...
import=...
import=...
errorPage=...
%%!
// class code

// service code

%!DOCTYPE ...
...
And if I need to place two directives with no spaces in between, I write

jsp:useBean
id=data scope=request class=my.Data
/jsp:getProperty
name=data property=aField
/

It is not as clean as a directive per line, but at least it doesn't hurt too much :-P

Regards,
Rodrigo
Marius Scurtescu wrote:

Hi,

Yes, I totally agree that this issue should be brought
up with the JSP specification. I will look into that.
Even if the suggestion is accepted it will be quite
a while until a specification will deal with this
issue and then even longer until there is going to
be a Tomcat implementation supporting it. We are
talking years I guess :-(
For what I know the specification is not saying
anything about this issue and if Tomcat is implementing
it right now it will not go against the spec.
Keeping strictly with the JSP directives (the issue
can be extended to the JSP tags as well, but it
gets more complicated) common sense is enough, I
hope, to realize that whenever you add a directive
you really don't want an empty line in your output.
These empty lines are annoying at best (every time
you check the source of a page generated by JSP you
first see an empty page - quite stupid), and breaking
your app at worst (like in the case of IE).
The absolute best proof that there is a problem
here that needs fixing is the fact that developers
make their code unreadable just as a work around.
Cheers,
Marius
Rodrigo Ruiz wrote:

Marius, I think such a feature request should not be addressed to
Tomcat, but to the JSP specification itself. Remember that Tomcat is
being used as the reference implementation of servlet/JSP
technologies, and so it should stick to the specification.

Basically, as I see it, your request means a special treatment for a
subset of directives in a few specific cases. I think it would imply
that tags could be marked as not generating any output, so when in a
single JSP line there were only such marked tags and leading /
trailing spaces among them, the line itself could be omited from the
output. Such a change should be made from the specification.

Regards,
Rodrigo
Marius Scurtescu wrote:

JSP is a templating language which is using a meta
language: the JSP constructs.
The new line is in the JSP indeed, but is it part
of the meta language or part of the literal output?
I would argue that these new lines are part of the
meta language and that they should not be output.
You put them there so the meta language you use is
readable.
See how FreeMarker, another templating language,
is dealing with this issue:
http://freemarker.sourceforge.net/docs/dgui_misc_whitespace.html#dgui_misc_whitespace_stripping

You are not asking the directive to scan anything,
the page compiler could consider white space and newlines
after a directive as part of that directive.
Marius

1 2 >

1 - 100 of 132 matches

Mail list logo