Re: [displaytag-devel] xDoclet, Maven anyone?

Didier Dubois Mon, 28 Jul 2003 11:45:23 -0700

Ok thanks!

Good luck for the mavenisation... If you have some questions.... Just ask. But don't blame me for the delays as I am only online after job and before snowboarding...

As some sides notes - you will notice that we have some package cycle in displaytag, which is not recommended, but really easy to fix. - I guessed the names of contributors... Don't fire me for mistakes and/or errors :-) (see root project.xml) - May be we should define some coding guidelines to ease "checkstyle" stresses... :-) - I removed the CVS related reports in order to reduce traffics with SF. - I appended the PMD reports ... could help too.. :-) - Also notes that Maven promotes TestCases... This is REALLY a great help! - I used the "Inheritance" feature of Maven. So most of works should go to the root project.xml - A lot of other thoughts I forget.... I should force myself to note when I have some ideas...:-(

HTH,
Didier

Fabrizio Giustina wrote:

thanks didier,
I'll try your work soon...

about the error in example-decorator.jsp: this should be already fixed
in cvs, the old package org.apache.taglibs.display.test has been renamed
to org.displaytag.sample

ciao
fabrizio

-----Original Message----- From: Didier Dubois [mailto:[EMAIL PROTECTED] Sent: Monday, July 28, 2003 7:00 PM To: Fabrizio Giustina; [EMAIL PROTECTED] Subject: Re: [displaytag-devel] xDoclet, Maven anyone?

Ciao Fabrizio,

Here is a tarball with
- Script and Templates for migration (this is a beta version!!!!)

Simply unpack the script tar and execute ./migration.sh ../some/located/path/to/display09 A resulting displaytag-maven will be generated

It is Maven b10 compatible.

Generated sites come latter...

HTH,
Didier.

PS: This is on the decorator examples: for instance: examples/example-decorator.jsp I got: (Sorry I didn't take time to investigate. i may be the only one to have the problem. Notes that I got the problem on the "original" display tag site as well as on the maven-ready-one)

HTTP Status 500 -

------------------------------------------------------------------------

*type* Exception report

*message*

*description* _The server encountered an internal error () that prevented it from fulfilling this request._

*exception*

org.apache.jasper.JasperException: Unable to load
org.apache.taglibs.display.test.Wrapper
        at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:248)
        at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
        at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:247)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:193)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:260)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
        at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
        at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:191)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
        at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
        at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:239
6)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:180)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
        at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa
lve.java:170)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:172)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
        at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
        at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:174)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
        at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
        at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:40
5)
        at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:380)
        at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:50
8)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:533)
        at java.lang.Thread.run(Thread.java:566)

*root cause*

javax.servlet.ServletException: Unable to load
org.apache.taglibs.display.test.Wrapper
        at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContex
tImpl.java:494)
        at
org.apache.jsp.example_0002ddecorator_jsp._jspService(example_0002ddecor
ator_jsp.java:261)
        at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:204)
        at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
        at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:247)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:193)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:260)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
        at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
        at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:191)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
        at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
        at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:239
6)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:180)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
        at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa
lve.java:170)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:172)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
        at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
        at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:174)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
        at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
        at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:40
5)
        at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:380)
        at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:50
8)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:533)
        at java.lang.Thread.run(Thread.java:566)

Fabrizio Giustina wrote:

Hi didier, I'm really interested in trying using maven for builds... Can you send me your scripts and generated site by mail? I'll take a look at it and,

if possibile, adapt the display09 cvs source tree for the maven build
Thanks
Fabrizio
PS. What is the problem with org.display.sample.Wrapper in the demo jsp

screens?
-----Original Message-----
From: did [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 27, 2003 4:53 PM
To: [EMAIL PROTECTED]
Subject: Re: [displaytag-devel] xDoclet, Maven anyone?
Dear all,
I currenlty try to understand Maven for my onw projects, and I used the
display09 development  tree to test my knowloedge.
So, if some are interrested here, I can provide a - shell script that makes the migration (sorry I am more fluent in shell script than in Maven or Ant) - Packed with a some default maven configuration files. (Total: 7k in

a

tgz format)

I can also the full generated tree. (850k)

For me it seems to work well. But this raises some questions and tree modifications: - example and library must be splitted. - packaging of the library has been slightly modified. - Some information are now duplicated in the JSP sample and the maven generated site - ....

Is there someone interrested with that quick hack?
BTW I also notice that the org.display.sample.Warpper has some problem
on the demo JSP screens?
Is it just for me?
Regards,
Didier.
Benjamin Simpson wrote:
As we begin to build out after the tree is settled, how about
introducing xDoclet and Maven into our system?
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_0 1 /01 _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel

Re: [displaytag-devel] xDoclet, Maven anyone?

Reply via email to