Re: svn commit: r980317 - /geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java

2010-07-28 Thread David Jencks
I'm not sure it would make a difference to the effect of the permission you end 
up with, but the code with the hashset eliminates duplicates.  I think you can 
have duplicates in the "everything leftover" permission (IIRC 
/::: Hi, Jarek:
> What is the difference between the old one and the new one ? While I did 
> it in the past, I just feel that there is no need to create an extra HashSet.
> 
> 2010/7/29 
> Author: gawor
> Date: Thu Jul 29 05:54:33 2010
> New Revision: 980317
> 
> URL: http://svn.apache.org/viewvc?rev=980317&view=rev
> Log:
> restore old code which seems to work better
> 
> Modified:
>
> geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java
> 
> Modified: 
> geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java
> URL: 
> http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java?rev=980317&r1=980316&r2=980317&view=diff
> ==
> --- 
> geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java
>  (original)
> +++ 
> geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java
>  Thu Jul 29 05:54:33 2010
> @@ -76,21 +76,20 @@ public class URLPattern {
> if (type == EXACT) {
> return pattern;
> } else {
> -//HashSet bucket = new HashSet();
> +HashSet bucket = new HashSet();
> StringBuilder result = new StringBuilder(pattern);
> +
> // Collect a set of qualifying patterns, depending on the type of 
> this pattern.
> for (URLPattern p : patterns) {
> if (type.check(this, p)) {
> -//bucket.add(p.pattern);
> -result.append(':');
> -result.append(p.pattern);
> +bucket.add(p.pattern);
> }
> }
> // append the set of qualifying patterns
> -/*for (String aBucket : bucket) {
> +for (String aBucket : bucket) {
> result.append(':');
> result.append(aBucket);
> -}*/
> +}
> return result.toString();
> }
> }
> 
> 
> 
> 
> 
> -- 
> Ivan



[jira] Updated: (GERONIMO-5481) Add test cases for jsp 2.2 new features into the testsuite.

2010-07-28 Thread Guang Zhe Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guang Zhe Wang updated GERONIMO-5481:
-

Description: 
The new feature tested in this patch includes:

configuration element  and 
 under  in the web.xml.

The  works incorrectly on tomcat-assembly which has been 
been reported in JIRA: GERONIMO-5478.

  was:
The new feature tested in this patch includes:

configuration element  and 
 under  in the web.xml.


> Add test cases for jsp 2.2 new features into the testsuite.
> ---
>
> Key: GERONIMO-5481
> URL: https://issues.apache.org/jira/browse/GERONIMO-5481
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: testsuite
>Affects Versions: 3.0
>Reporter: Guang Zhe Wang
> Fix For: 3.0
>
> Attachments: jsp2.2-testsuite.patch
>
>
> The new feature tested in this patch includes:
> configuration element  and 
>  under  in the web.xml.
> The  works incorrectly on tomcat-assembly which has 
> been been reported in JIRA: GERONIMO-5478.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Closed: (GERONIMO-5483) jetty needs to give jasper the merged metadata complete web.xml

2010-07-28 Thread David Jencks (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Jencks closed GERONIMO-5483.
--

Resolution: Fixed

rev 980334.  Also set the default web.xml version to 3.0 in openejb rev 980333

> jetty needs to give jasper the merged metadata complete web.xml
> ---
>
> Key: GERONIMO-5483
> URL: https://issues.apache.org/jira/browse/GERONIMO-5483
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: javaee6, Jetty
>Affects Versions: 3.0
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 3.0
>
>
> jasper needs a web.xml to check the version for a few settings like enabling 
> el.  If there isn't one in the war, we can feed the complete one we construct 
> to jasper as a servlet context attribute.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (GERONIMO-5483) jetty needs to give jasper the merged metadata complete web.xml

2010-07-28 Thread David Jencks (JIRA)
jetty needs to give jasper the merged metadata complete web.xml
---

 Key: GERONIMO-5483
 URL: https://issues.apache.org/jira/browse/GERONIMO-5483
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: javaee6, Jetty
Affects Versions: 3.0
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 3.0


jasper needs a web.xml to check the version for a few settings like enabling 
el.  If there isn't one in the war, we can feed the complete one we construct 
to jasper as a servlet context attribute.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMO-5453) Add testing about Servlet-3.0's new secuirty features into Testsuite

2010-07-28 Thread Forrest Xia (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893534#action_12893534
 ] 

Forrest Xia commented on GERONIMO-5453:
---

Committed revision 980331 to trunk. thanks LiWenQin!

> Add testing about Servlet-3.0's new secuirty features into Testsuite
> 
>
> Key: GERONIMO-5453
> URL: https://issues.apache.org/jira/browse/GERONIMO-5453
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: testsuite
>Affects Versions: 3.0
>Reporter: LiWenQin
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 3.0
>
> Attachments: GERONIMO-5453.patch, 
> servlet3.0-security-test-modifyTestng.patch, servlet3.0-security-test.patch
>
>
> Add tests into web-testsuite, which makes testing Servlet 3.0's new security 
> features automatically.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5482) Add test cases for el 2.2 new features into the testsuite.

2010-07-28 Thread Guang Zhe Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guang Zhe Wang updated GERONIMO-5482:
-

Attachment: el2.2-testsuite.patch

> Add test cases for el 2.2 new features into the testsuite.
> --
>
> Key: GERONIMO-5482
> URL: https://issues.apache.org/jira/browse/GERONIMO-5482
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: testsuite
>Affects Versions: 3.0
>Reporter: Guang Zhe Wang
> Fix For: 3.0
>
> Attachments: el2.2-testsuite.patch
>
>
> The new feature of EL 2.2 tested in this patch is method invocation with 
> parameters. It runs incorrectly in the tomcat-assembly when the parameter is 
> integer which has been reported in JIRA: GERONIMO-5479. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (GERONIMO-5482) Add test cases for el 2.2 new features into the testsuite.

2010-07-28 Thread Guang Zhe Wang (JIRA)
Add test cases for el 2.2 new features into the testsuite.
--

 Key: GERONIMO-5482
 URL: https://issues.apache.org/jira/browse/GERONIMO-5482
 Project: Geronimo
  Issue Type: Task
  Security Level: public (Regular issues)
Affects Versions: 3.0
Reporter: Guang Zhe Wang
 Fix For: 3.0
 Attachments: el2.2-testsuite.patch

The new feature of EL 2.2 tested in this patch is method invocation with 
parameters. It runs incorrectly in the tomcat-assembly when the parameter is 
integer which has been reported in JIRA: GERONIMO-5479. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5482) Add test cases for el 2.2 new features into the testsuite.

2010-07-28 Thread Guang Zhe Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guang Zhe Wang updated GERONIMO-5482:
-

Component/s: testsuite

> Add test cases for el 2.2 new features into the testsuite.
> --
>
> Key: GERONIMO-5482
> URL: https://issues.apache.org/jira/browse/GERONIMO-5482
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: testsuite
>Affects Versions: 3.0
>Reporter: Guang Zhe Wang
> Fix For: 3.0
>
> Attachments: el2.2-testsuite.patch
>
>
> The new feature of EL 2.2 tested in this patch is method invocation with 
> parameters. It runs incorrectly in the tomcat-assembly when the parameter is 
> integer which has been reported in JIRA: GERONIMO-5479. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5481) Add test cases for jsp 2.2 new features into the testsuite.

2010-07-28 Thread Guang Zhe Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guang Zhe Wang updated GERONIMO-5481:
-

Attachment: jsp2.2-testsuite.patch

> Add test cases for jsp 2.2 new features into the testsuite.
> ---
>
> Key: GERONIMO-5481
> URL: https://issues.apache.org/jira/browse/GERONIMO-5481
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: testsuite
>Affects Versions: 3.0
>Reporter: Guang Zhe Wang
> Fix For: 3.0
>
> Attachments: jsp2.2-testsuite.patch
>
>
> The new feature tested in this patch includes:
> configuration element  and 
>  under  in the web.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (GERONIMO-5481) Add test cases for jsp 2.2 new features into the testsuite.

2010-07-28 Thread Guang Zhe Wang (JIRA)
Add test cases for jsp 2.2 new features into the testsuite.
---

 Key: GERONIMO-5481
 URL: https://issues.apache.org/jira/browse/GERONIMO-5481
 Project: Geronimo
  Issue Type: Task
  Security Level: public (Regular issues)
  Components: testsuite
Affects Versions: 3.0
Reporter: Guang Zhe Wang
 Fix For: 3.0
 Attachments: jsp2.2-testsuite.patch

The new feature tested in this patch includes:

configuration element  and 
 under  in the web.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: svn commit: r980317 - /geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java

2010-07-28 Thread Ivan
Hi, Jarek:
What is the difference between the old one and the new one ? While I did
it in the past, I just feel that there is no need to create an extra
HashSet.

2010/7/29 

> Author: gawor
> Date: Thu Jul 29 05:54:33 2010
> New Revision: 980317
>
> URL: http://svn.apache.org/viewvc?rev=980317&view=rev
> Log:
> restore old code which seems to work better
>
> Modified:
>
>  
> geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java
>
> Modified:
> geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java
> URL:
> http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java?rev=980317&r1=980316&r2=980317&view=diff
>
> ==
> ---
> geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java
> (original)
> +++
> geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/URLPattern.java
> Thu Jul 29 05:54:33 2010
> @@ -76,21 +76,20 @@ public class URLPattern {
> if (type == EXACT) {
> return pattern;
> } else {
> -//HashSet bucket = new HashSet();
> +HashSet bucket = new HashSet();
> StringBuilder result = new StringBuilder(pattern);
> +
> // Collect a set of qualifying patterns, depending on the type
> of this pattern.
> for (URLPattern p : patterns) {
> if (type.check(this, p)) {
> -//bucket.add(p.pattern);
> -result.append(':');
> -result.append(p.pattern);
> +bucket.add(p.pattern);
> }
> }
> // append the set of qualifying patterns
> -/*for (String aBucket : bucket) {
> +for (String aBucket : bucket) {
> result.append(':');
> result.append(aBucket);
> -}*/
> +}
> return result.toString();
> }
> }
>
>
>


-- 
Ivan


[jira] Updated: (GERONIMO-5453) Add testing about Servlet-3.0's new secuirty features into Testsuite

2010-07-28 Thread LiWenQin (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

LiWenQin updated GERONIMO-5453:
---

Attachment: servlet3.0-security-test-modifyTestng.patch

Find the the suite name in testng.xml should be modified.
Add a small patch about it.
Details:
 
-
+

> Add testing about Servlet-3.0's new secuirty features into Testsuite
> 
>
> Key: GERONIMO-5453
> URL: https://issues.apache.org/jira/browse/GERONIMO-5453
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: testsuite
>Affects Versions: 3.0
>Reporter: LiWenQin
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 3.0
>
> Attachments: GERONIMO-5453.patch, 
> servlet3.0-security-test-modifyTestng.patch, servlet3.0-security-test.patch
>
>
> Add tests into web-testsuite, which makes testing Servlet 3.0's new security 
> features automatically.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5473) Add testing about EJB-3.1-Lite's new features into Testsuite

2010-07-28 Thread LiWenQin (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

LiWenQin updated GERONIMO-5473:
---

Attachment: test-ejb3.1-Lite-add-testng.patch

Sorry, I forgot to add testng.xml in the previous patch.
Add a new patch contains testng.xml.

> Add testing about EJB-3.1-Lite's new features into Testsuite
> 
>
> Key: GERONIMO-5473
> URL: https://issues.apache.org/jira/browse/GERONIMO-5473
> Project: Geronimo
>  Issue Type: Task
>  Security Level: public(Regular issues) 
>  Components: testsuite
>Affects Versions: 3.0
>Reporter: LiWenQin
>Assignee: Forrest Xia
> Fix For: 3.0
>
> Attachments: ejb3.1lite-test.patch, test-ejb3.1-Lite-add-testng.patch
>
>
> I have created a patch for EJB3.1 Lite testsuite.
> It tests new features in EJB 3.1 Lite:
> a.A simplified Local view that provides Session Bean access without a 
> separate Local Business interface.
> b.Packaging and deployment of EJB components directly in a .war without an 
> ejb-jar.
> c.A Singleton session bean.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (GERONIMO-5480) Web security does not work on Equinox

2010-07-28 Thread Jarek Gawor (JIRA)
Web security does not work on Equinox
-

 Key: GERONIMO-5480
 URL: https://issues.apache.org/jira/browse/GERONIMO-5480
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 3.0-M1
Reporter: Jarek Gawor
 Fix For: 3.0


Authentication is not requested when running secure web applications on 
Geronimo on Equinox. That is, things behave as the user is already 
authenticated. This can be easily observed with the admin console or 
security-testsuite. Authentication works as expected on Felix.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5479) EL 2.2 new feature: method invocation with parameters works incorrectly when the parameter is Integer.

2010-07-28 Thread Guang Zhe Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guang Zhe Wang updated GERONIMO-5479:
-

Description: 
I create a simple JSF app to test this new feature. In the managed bean User 
class, I defined a method: 

public int calYear(int x) {
return (age + x);
}

and in the page I call it with #{user.calYear(5)}, in both tomcat and jetty 
assemblies an error occurs:

java.lang.NoSuchMethodException: 
org.apache.geronimo.testsuite.el22.app.User.calYear(java.lang.Long) which 
implies that the container recognizes 5 as Long.

The error stack:

javax.faces.FacesException: java.lang.NoSuchMethodException: 
org.apache.geronimo.testsuite.el22.app.User.calYear(java.lang.Long)
at 
org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241)
at 
org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156)
at 
org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:222)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:532)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:456)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:230)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:966)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:391)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:902)
at 
org.apache.geronimo.jetty8.handler.GeronimoWebAppContext.doScope(GeronimoWebAppContext.java:125)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245)
at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
at org.eclipse.jetty.server.Server.handle(Server.java:338)
at 
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:568)
at 
org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1010)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:775)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:228)
at 
org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:403)
at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:474)
at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214)
at 
org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoSuchMethodException: 
org.apache.geronimo.testsuite.el22.app.User.calYear(java.lang.Long)
at java.lang.Class.getMethod(Unknown Source)
at javax.el.BeanELResolver.invoke(BeanELResolver.java:394)
at javax.el.CompositeELResolver.invoke(CompositeELResolver.java:228)
at org.apache.el.parser.AstValue.getValue(AstValue.java:158)
at 
org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192)
at 
org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:84)
at 
javax.faces.component._DeltaStateHelper.eval(_DeltaStateHelper.java:243)
at javax.faces.component.UIOutput.getValue(UIOutput.java:71)
at 
org.apache.myfaces.shared_impl.renderkit.RendererUtils.getValue(RendererUtils.java:349)
at 
org.apache.myfaces.shared_impl.renderkit.RendererUtils.getStringValue(RendererUtils.java:301)
at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.renderOutput(HtmlTextRendererBase.java:81)
at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.encodeEnd(HtmlTextRendererBase.java:68)
at 
javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:486)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:618)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:614)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:614)
at 
org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.renderView(FaceletViewDeclarationLanguage.java:1117)
at 
org.apache.myfaces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.

[jira] Created: (GERONIMO-5479) EL 2.2 new feature: method invocation with parameters works incorrectly when the parameter is Integer.

2010-07-28 Thread Guang Zhe Wang (JIRA)
EL 2.2 new feature: method invocation with parameters works incorrectly when 
the parameter is Integer.
--

 Key: GERONIMO-5479
 URL: https://issues.apache.org/jira/browse/GERONIMO-5479
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: javaee6
Affects Versions: 3.0
Reporter: Guang Zhe Wang
 Fix For: 3.0


I create a simple JSF app to test this new feature. In the managed bean User 
class, I defined a method: 

public int calYear(int x) {
return (age + x);
}

and in the page I call it with #{user.calYear(5)}, in both tomcat and 
assemblies an error occurs:

java.lang.NoSuchMethodException: 
org.apache.geronimo.testsuite.el22.app.User.calYear(java.lang.Long) which 
implies that the container recognizes 5 as Long.

The error stack:

javax.faces.FacesException: java.lang.NoSuchMethodException: 
org.apache.geronimo.testsuite.el22.app.User.calYear(java.lang.Long)
at 
org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241)
at 
org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156)
at 
org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:222)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:532)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:456)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:230)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:966)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:391)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:902)
at 
org.apache.geronimo.jetty8.handler.GeronimoWebAppContext.doScope(GeronimoWebAppContext.java:125)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245)
at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
at org.eclipse.jetty.server.Server.handle(Server.java:338)
at 
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:568)
at 
org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1010)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:775)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:228)
at 
org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:403)
at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:474)
at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214)
at 
org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoSuchMethodException: 
org.apache.geronimo.testsuite.el22.app.User.calYear(java.lang.Long)
at java.lang.Class.getMethod(Unknown Source)
at javax.el.BeanELResolver.invoke(BeanELResolver.java:394)
at javax.el.CompositeELResolver.invoke(CompositeELResolver.java:228)
at org.apache.el.parser.AstValue.getValue(AstValue.java:158)
at 
org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192)
at 
org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:84)
at 
javax.faces.component._DeltaStateHelper.eval(_DeltaStateHelper.java:243)
at javax.faces.component.UIOutput.getValue(UIOutput.java:71)
at 
org.apache.myfaces.shared_impl.renderkit.RendererUtils.getValue(RendererUtils.java:349)
at 
org.apache.myfaces.shared_impl.renderkit.RendererUtils.getStringValue(RendererUtils.java:301)
at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.renderOutput(HtmlTextRendererBase.java:81)
at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.encodeEnd(HtmlTextRendererBase.java:68)
at 
javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:486)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:618)
at javax.faces.component.UIComponent.encodeAll(UICo

[jira] Commented: (GERONIMODEVTOOLS-619) Implement Blueprint XML form editor

2010-07-28 Thread Delos Dai (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893500#action_12893500
 ] 

Delos Dai commented on GERONIMODEVTOOLS-619:


Kan,

Thanks! I've corrected it.

> Implement Blueprint XML form editor
> ---
>
> Key: GERONIMODEVTOOLS-619
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-619
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 3.0
>Reporter: Tim McConnell
>Assignee: Delos Dai
> Fix For: 3.0
>
> Attachments: GERONIMODEVTOOLS-619.patch
>
>
> Should be modeled on the web.xml and geronimo-web.xml form editor support

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMODEVTOOLS-663) Remove duplicated License and Notice files in each jar when we issue "mvn release:prepare"

2010-07-28 Thread Delos Dai (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893498#action_12893498
 ] 

Delos Dai commented on GERONIMODEVTOOLS-663:


During release process, LICENSE and NOTICE file will automatically pulled in 
MANIFEST directory of final jar file. So we don't need to keep LICENSE.txt and 
NOTICE.txt in source code of each plugins.

> Remove duplicated License and Notice files in each jar when we issue "mvn 
> release:prepare"
> --
>
> Key: GERONIMODEVTOOLS-663
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-663
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.6, 2.2.1, 3.0
>Reporter: Delos Dai
>Assignee: Delos Dai
> Fix For: 2.1.6, 2.2.1, 3.0
>
>
> Remove duplicated License and Notice files in each jar when we issue " mvn 
> release:prepare"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMODEVTOOLS-648) Source release assembly contains temporary files generated in build process

2010-07-28 Thread Delos Dai (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893496#action_12893496
 ] 

Delos Dai commented on GERONIMODEVTOOLS-648:


Keep this JIRA open until we finally verify the release process for branches 
2.2 

> Source release assembly contains temporary files generated in build process
> ---
>
> Key: GERONIMODEVTOOLS-648
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-648
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.6, 2.2.1, 3.0_M1, 3.0
>Reporter: Delos Dai
>Assignee: Delos Dai
> Fix For: 2.1.6, 2.2.1, 3.0_M1, 3.0
>
>
> Currently, apache 5 is the parent of geronimo-eclipse-plugin.Besides, I added 
> configuration to its pom.xml introduced here 
> http://maven.apache.org/developers/release/apache-release.html. But the 
> result is, after we complete release prepare and perform, the source assembly 
> contains all the temporary files generated by maven, such as target directory 
> and pom.releaseBackup. Seems the configuration doesn't work for GEP. 
> I found source assembly for Geronimo Server works fine because it uses a 
> different source assembly dependency from apache 5 or 6, that is 
> apache-source-release-assembly-descriptor in group 
> org.apache.geronimo.genesis. So I did these changes to root pom.xml.
> 1) Update apache 5 to apache 6, which is also used by Geronimo server 3.0
> 2) copy apache-release profile snippet from genesis-2.0.pom 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMODEVTOOLS-623) Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime

2010-07-28 Thread Delos Dai (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Delos Dai updated GERONIMODEVTOOLS-623:
---

Priority: Minor  (was: Major)

I think Admin Console will finally provide portlet for user to 
start/stop/restart OSGi artifacts. So it may be duplicated. 
Update the task with lower priority. 

> Implement finer granularity of start/stop/restart operations on OSGi 
> artifacts deployed on the Geronimo runtime
> ---
>
> Key: GERONIMODEVTOOLS-623
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 3.0
>Reporter: Tim McConnell
>Assignee: Delos Dai
>Priority: Minor
> Fix For: 3.0
>
>
> Must include the following artifacts:
> o EBA
> o WAB
> o OSGi bundle 
> o OSGi Blueprint bundle

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Assigned: (GERONIMODEVTOOLS-623) Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime

2010-07-28 Thread Delos Dai (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Delos Dai reassigned GERONIMODEVTOOLS-623:
--

Assignee: Delos Dai

> Implement finer granularity of start/stop/restart operations on OSGi 
> artifacts deployed on the Geronimo runtime
> ---
>
> Key: GERONIMODEVTOOLS-623
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>  Components: eclipse-plugin
>Affects Versions: 3.0
>Reporter: Tim McConnell
>Assignee: Delos Dai
> Fix For: 3.0
>
>
> Must include the following artifacts:
> o EBA
> o WAB
> o OSGi bundle 
> o OSGi Blueprint bundle

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5478) JSP 2.2 new configuration element under works incorrectly on tomcat-assembly server.

2010-07-28 Thread Guang Zhe Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guang Zhe Wang updated GERONIMO-5478:
-

Comment: was deleted

(was: This is the test case I used for JSP 2.2 new feature.)

> JSP 2.2 new configuration element  under 
>   works incorrectly on tomcat-assembly server.
> -
>
> Key: GERONIMO-5478
> URL: https://issues.apache.org/jira/browse/GERONIMO-5478
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 3.0
>Reporter: Guang Zhe Wang
> Fix For: 3.0
>
> Attachments: jsp2.2-testsuite.patch
>
>
>  is said to specify the default response contentType if 
> the page directive does not include a contentType attribute in the JSP 2.2 
> spec documentation. So does it mean if the page directive have included a 
> contentType attribute, the configuration in  will take 
> no effect? In jetty-assembly, it does like this. But in tomcat-assembly, it  
> sends out an exception:
> org.apache.jasper.JasperException: /defaultCtype/page1.jsp(17,1) Page 
> directive: illegal to have multiple occurrences of contentType with different 
> values (old: text/xml, new: text/html)
> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
>   
> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
>   
> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236)
>   
> org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:133)
>   org.apache.jasper.compiler.Node$PageDirective.accept(Node.java:590)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)
>   org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2428)
>   org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2434)
>   org.apache.jasper.compiler.Node$Root.accept(Node.java:475)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)
>   
> org.apache.jasper.compiler.Validator.validateDirectives(Validator.java:1733)
>   org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:195)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:360)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)
>   
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:594)
>   
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315)
>   org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
>   org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> I patched the test case I use and uploaded it. You can apply it on trunk. And 
> then build and deploy it on tomcat-assembly to see the result.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Issue Comment Edited: (GERONIMO-5478) JSP 2.2 new configuration element under works incorrectly on tomcat-assembly server.

2010-07-28 Thread Guang Zhe Wang (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893483#action_12893483
 ] 

Guang Zhe Wang edited comment on GERONIMO-5478 at 7/28/10 10:46 PM:


This is the test case I used for JSP 2.2 new feature.

  was (Author: wgzlllfc):
This the test case I used for JSP 2.2 new feature.
  
> JSP 2.2 new configuration element  under 
>   works incorrectly on tomcat-assembly server.
> -
>
> Key: GERONIMO-5478
> URL: https://issues.apache.org/jira/browse/GERONIMO-5478
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 3.0
>Reporter: Guang Zhe Wang
> Fix For: 3.0
>
> Attachments: jsp2.2-testsuite.patch
>
>
>  is said to specify the default response contentType if 
> the page directive does not include a contentType attribute in the JSP 2.2 
> spec documentation. So does it mean if the page directive have included a 
> contentType attribute, the configuration in  will take 
> no effect? In jetty-assembly, it does like this. But in tomcat-assembly, it  
> sends out an exception:
> org.apache.jasper.JasperException: /defaultCtype/page1.jsp(17,1) Page 
> directive: illegal to have multiple occurrences of contentType with different 
> values (old: text/xml, new: text/html)
> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
>   
> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
>   
> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236)
>   
> org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:133)
>   org.apache.jasper.compiler.Node$PageDirective.accept(Node.java:590)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)
>   org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2428)
>   org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2434)
>   org.apache.jasper.compiler.Node$Root.accept(Node.java:475)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)
>   
> org.apache.jasper.compiler.Validator.validateDirectives(Validator.java:1733)
>   org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:195)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:360)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)
>   
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:594)
>   
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315)
>   org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
>   org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> I patched the test case I use and uploaded it. You can apply it on trunk. And 
> then build and deploy it on tomcat-assembly to see the result.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-5478) JSP 2.2 new configuration element under works incorrectly on tomcat-assembly server.

2010-07-28 Thread Guang Zhe Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guang Zhe Wang updated GERONIMO-5478:
-

 Patch Info: [Patch Available]
Description: 
 is said to specify the default response contentType if 
the page directive does not include a contentType attribute in the JSP 2.2 spec 
documentation. So does it mean if the page directive have included a 
contentType attribute, the configuration in  will take no 
effect? In jetty-assembly, it does like this. But in tomcat-assembly, it  sends 
out an exception:

org.apache.jasper.JasperException: /defaultCtype/page1.jsp(17,1) Page 
directive: illegal to have multiple occurrences of contentType with different 
values (old: text/xml, new: text/html)

org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)

org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)

org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236)

org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:133)
org.apache.jasper.compiler.Node$PageDirective.accept(Node.java:590)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2428)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2434)
org.apache.jasper.compiler.Node$Root.accept(Node.java:475)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)

org.apache.jasper.compiler.Validator.validateDirectives(Validator.java:1733)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:195)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:360)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)

org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:594)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:668)

I patched the test case I use and uploaded it. You can apply it on trunk. And 
then build and deploy it on tomcat-assembly to see the result.


  was:
 is said to specify the default response contentType if 
the page directive does not include a contentType attribute in the JSP 2.2 spec 
documentation. So does it mean if the page directive have included a 
contentType attribute, the configuration in  will take no 
effect? In jetty-assembly, it does like this. But in tomcat-assembly, it  sends 
out an exception:

org.apache.jasper.JasperException: /defaultCtype/page1.jsp(17,1) Page 
directive: illegal to have multiple occurrences of contentType with different 
values (old: text/xml, new: text/html)

org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)

org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)

org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236)

org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:133)
org.apache.jasper.compiler.Node$PageDirective.accept(Node.java:590)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2428)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2434)
org.apache.jasper.compiler.Node$Root.accept(Node.java:475)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)

org.apache.jasper.compiler.Validator.validateDirectives(Validator.java:1733)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:195)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:360)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)

org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:594)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:668)

The test case 



> JSP 2.2 new configuration element  under 
>   works incorrectly on tomcat-assembly server.
> -
>
> Key: GERONIMO-5478
> URL: https://issues.apache.org/jira/browse/GERONIMO-5478
> Proj

[jira] Updated: (GERONIMO-5478) JSP 2.2 new configuration element under works incorrectly on tomcat-assembly server.

2010-07-28 Thread Guang Zhe Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guang Zhe Wang updated GERONIMO-5478:
-

Attachment: jsp2.2-testsuite.patch

This the test case I used for JSP 2.2 new feature.

> JSP 2.2 new configuration element  under 
>   works incorrectly on tomcat-assembly server.
> -
>
> Key: GERONIMO-5478
> URL: https://issues.apache.org/jira/browse/GERONIMO-5478
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tomcat
>Affects Versions: 3.0
>Reporter: Guang Zhe Wang
> Fix For: 3.0
>
> Attachments: jsp2.2-testsuite.patch
>
>
>  is said to specify the default response contentType if 
> the page directive does not include a contentType attribute in the JSP 2.2 
> spec documentation. So does it mean if the page directive have included a 
> contentType attribute, the configuration in  will take 
> no effect? In jetty-assembly, it does like this. But in tomcat-assembly, it  
> sends out an exception:
> org.apache.jasper.JasperException: /defaultCtype/page1.jsp(17,1) Page 
> directive: illegal to have multiple occurrences of contentType with different 
> values (old: text/xml, new: text/html)
> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
>   
> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
>   
> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236)
>   
> org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:133)
>   org.apache.jasper.compiler.Node$PageDirective.accept(Node.java:590)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)
>   org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2428)
>   org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2434)
>   org.apache.jasper.compiler.Node$Root.accept(Node.java:475)
>   org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)
>   
> org.apache.jasper.compiler.Validator.validateDirectives(Validator.java:1733)
>   org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:195)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:360)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
>   org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)
>   
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:594)
>   
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315)
>   org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
>   org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> I patched the test case I use and uploaded it. You can apply it on trunk. And 
> then build and deploy it on tomcat-assembly to see the result.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[BUILD] trunk: Failed for Revision: 980280

2010-07-28 Thread gawor
Geronimo Revision: 980280 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 40 minutes 48 seconds
[INFO] Finished at: Wed Jul 28 21:44:22 EDT 2010
[INFO] Final Memory: 506M/1001M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/logs-2100-tomcat/
 
 
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/commands-testsuite/3.0-SNAPSHOT/commands-testsuite-3.0-SNAPSHOT.pom
[INFO] 
[INFO] Building Geronimo TestSuite :: Commands Testsuite :: Deployer
[INFO]task-segment: [install]
[INFO] 
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/plugins/maven-failsafe-plugin/2.5/maven-failsafe-plugin-2.5.pom
9K downloaded  (maven-failsafe-plugin-2.5.pom)
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/surefire/surefire/2.5/surefire-2.5.pom
6K downloaded  (surefire-2.5.pom)
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/maven-parent/15/maven-parent-15.pom
23K downloaded  (maven-parent-15.pom)
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/plugins/maven-failsafe-plugin/2.5/maven-failsafe-plugin-2.5.jar
46K downloaded  (maven-failsafe-plugin-2.5.jar)
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar: 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/deploy-3.0-SNAPSHOT.jar
[org.codehaus.mojo.pluginsupport.logging.Logging] : Initialized
[INFO] [geronimo:start-server {execution: start-geronimo}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:3.0-SNAPSHOT: checking 
for updates from codehaus.snapshots
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:3.0-SNAPSHOT: checking 
for updates from apache.snapshots
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0-SNAPSHOT/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting

[jira] Created: (GERONIMO-5478) JSP 2.2 new configuration element under works incorrectly on tomcat-assembly server.

2010-07-28 Thread Guang Zhe Wang (JIRA)
JSP 2.2 new configuration element  under 
  works incorrectly on tomcat-assembly server.
-

 Key: GERONIMO-5478
 URL: https://issues.apache.org/jira/browse/GERONIMO-5478
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Tomcat
Affects Versions: 3.0
Reporter: Guang Zhe Wang
 Fix For: 3.0


 is said to specify the default response contentType if 
the page directive does not include a contentType attribute in the JSP 2.2 spec 
documentation. So does it mean if the page directive have included a 
contentType attribute, the configuration in  will take no 
effect? In jetty-assembly, it does like this. But in tomcat-assembly, it  sends 
out an exception:

org.apache.jasper.JasperException: /defaultCtype/page1.jsp(17,1) Page 
directive: illegal to have multiple occurrences of contentType with different 
values (old: text/xml, new: text/html)

org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)

org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)

org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236)

org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:133)
org.apache.jasper.compiler.Node$PageDirective.accept(Node.java:590)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2428)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2434)
org.apache.jasper.compiler.Node$Root.accept(Node.java:475)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376)

org.apache.jasper.compiler.Validator.validateDirectives(Validator.java:1733)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:195)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:360)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)

org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:594)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:668)

The test case 


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugins

2010-07-28 Thread Delos
my own +1.

Is there anyone can take a look at this?

2010/7/27 Delos 

> Hi all,
>
> Hope you're not surprised at this voting. Actually, I have discussed it
> with Kevan and Donald.
>
> As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to
> maven dependencies and add them into artifact dependency list.But now, we
> have to update the plugin to accommodate new requirements. See more details
> here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658
>
> I will prompt the new plugins once it passes the voting.
>
> 
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachegeronimo-030/
>
>
> svn tag at:
> http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/
>
> [ ] +1 go for it
> [ ] 0
> [ ] -1 whoa, hold on a minute
>
>
> --
> Best Regards,
>
> Delos
>



-- 
Best Regards,

Delos


[BUILD] trunk: Failed for Revision: 980165

2010-07-28 Thread gawor
Geronimo Revision: 980165 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 38 minutes 8 seconds
[INFO] Finished at: Wed Jul 28 15:43:10 EDT 2010
[INFO] Final Memory: 480M/980M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/logs-1500-tomcat/
 
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 23.978 sec <<< 
FAILURE!
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.446 sec <<< 
FAILURE!
--
Running TestSuite
Tests run: 22, Failures: 14, Errors: 0, Skipped: 0, Time elapsed: 28.375 sec 
<<< FAILURE!
 
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: 
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; 
ignoring: java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectEx

[BUILD] trunk: Failed for Revision: 980045

2010-07-28 Thread gawor
Geronimo Revision: 980045 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/build-0900.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 45 minutes 5 seconds
[INFO] Finished at: Wed Jul 28 09:50:05 EDT 2010
[INFO] Final Memory: 543M/988M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/logs-0900-tomcat/
 
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 23.457 sec <<< 
FAILURE!
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.442 sec <<< 
FAILURE!
--
Running TestSuite
Tests run: 22, Failures: 14, Errors: 0, Skipped: 0, Time elapsed: 29.2 sec <<< 
FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/logs-0900-jetty/
 
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 21.973 sec <<< 
FAILURE!
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.466 sec <<< 
FAILURE!
--
Running TestSuite
Tests run: 22, Failures: 14, Errors: 0, Skipped: 0, Time elapsed: 30.846 sec 
<<< FAILURE!
 
Samples: trunk
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/samples-0900.log
 
Build status: FAILED
 


[BUILD] branches/2.2: Failed for Revision: 980029

2010-07-28 Thread gawor
Geronimo Revision: 980029 built with tests included
 
See the full build-0800.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100728/build-0800.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100728/unit-test-reports
 
[INFO] Building jar: 
/home/geronimo/geronimo/2.2/plugins/jetty7/geronimo-jetty7-builder/target/geronimo-jetty7-builder-2.2.2-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-jetty7-builder-2.2.2-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing 
/home/geronimo/geronimo/2.2/plugins/jetty7/geronimo-jetty7-builder/target/geronimo-jetty7-builder-2.2.2-SNAPSHOT.jar
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-jetty7-builder/2.2.2-SNAPSHOT/geronimo-jetty7-builder-2.2.2-SNAPSHOT.jar
[INFO] 
[INFO] Building Geronimo Plugins, Jetty :: Deployer
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/plugins/jetty7/jetty7-deployer/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/plugins/jetty7/jetty7-deployer/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated: 
/home/geronimo/geronimo/2.2/plugins/jetty7/jetty7-deployer/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[INFO] [car:package]
[INFO] Packaging module configuration: 
/home/geronimo/geronimo/2.2/plugins/jetty7/jetty7-deployer/target/work/plan.xml
[INFO] Started deployer: 
org.apache.geronimo.framework/geronimo-gbean-deployer/2.2.2-SNAPSHOT/car
[INFO] [car:prepare-metadata]
[INFO] [car:archive-car]
[INFO] Building jar: 
/home/geronimo/geronimo/2.2/plugins/jetty7/jetty7-deployer/target/jetty7-deployer-2.2.2-SNAPSHOT.car
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: jetty7-deployer-2.2.2-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing 
/home/geronimo/geronimo/2.2/plugins/jetty7/jetty7-deployer/target/jetty7-deployer-2.2.2-SNAPSHOT.car
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/configs/jetty7-deployer/2.2.2-SNAPSHOT/jetty7-deployer-2.2.2-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO] 
[INFO] Building Geronimo Plugins, Jasper
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install]
[INFO] Installing /home/geronimo/geronimo/2.2/plugins/jasper/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/plugins/jasper/2.2.2-SNAPSHOT/jasper-2.2.2-SNAPSHOT.pom
[INFO] 
[INFO] Building Geronimo Plugins, Jasper :: Core
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/plugins/jasper/geronimo-jasper/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/plugins/jasper/geronimo-jasper/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 3 source files to 
/home/geronimo/geronimo/2.2/plugins/jasper/geronimo-jasper/target/classes
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Compilation failure

/home/geronimo/geronimo/2.2/plugins/jasper/geronimo-jasper/src/main/java/org/apache/geronimo/jasper/JspServletOptions.java:[31,7]
 org.apache.geronimo.jasper.JspServletOptions is not abstract and does not 
override abstract method getRecompileOnFail() in org.apache.jasper.Options

/home/geronimo/geronimo/2.2/plugins/jasper/geronimo-jasper/src/main/java/org/apache/geronimo/jasper/JspServletOptions.java:[124,19]
 [deprecation] getSendErrorToClient() in org.apache.jas

[BUILD] trunk: Failed for Revision: 979965

2010-07-28 Thread gawor
Geronimo Revision: 979965 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/build-0300.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 37 minutes 49 seconds
[INFO] Finished at: Wed Jul 28 03:41:05 EDT 2010
[INFO] Final Memory: 493M/992M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/logs-0300-tomcat/
 
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 23.849 sec <<< 
FAILURE!
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.44 sec <<< 
FAILURE!
--
Running TestSuite
Tests run: 22, Failures: 14, Errors: 0, Skipped: 0, Time elapsed: 28.694 sec 
<<< FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/logs-0300-jetty/
 
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 22.702 sec <<< 
FAILURE!
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.448 sec <<< 
FAILURE!
--
Running TestSuite
Tests run: 22, Failures: 14, Errors: 0, Skipped: 0, Time elapsed: 30.579 sec 
<<< FAILURE!
 
Samples: trunk
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100728/samples-0300.log
 
Build status: FAILED
 


[BUILD] branches/2.2: Failed for Revision: 979916

2010-07-28 Thread gawor
Geronimo Revision: 979916 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100728/build-2000.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100728
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 394 minutes 30 seconds
[INFO] Finished at: Wed Jul 28 02:41:55 EDT 2010
[INFO] Final Memory: 325M/849M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100728/logs-2000-tomcat/
 
[INFO] Running TestSuite
[INFO] Tests run: 118, Failures: 1, Errors: 0, Skipped: 117, Time elapsed: 
23.222 sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 38, Failures: 1, Errors: 0, Skipped: 37, Time elapsed: 21.543 
sec <<< FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 21.08 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 1, Errors: 0, Skipped: 3, Time elapsed: 21.139 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 1, Errors: 0, Skipped: 3, Time elapsed: 21.471 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 9, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 21.179 
sec <<< FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 21.027 
sec <<< FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 11, Failures: 1, Errors: 0, Skipped: 10, Time elapsed: 21.215 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 38, Failures: 1, Errors: 0, Skipped: 37, Time elapsed: 21.611 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 6, Failures: 1, Errors: 0, Skipped: 5, Time elapsed: 21.17 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 21.088 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 21.094 
sec <<< FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 21.192 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 5, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 21.065 
sec <<< FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100728/logs-2000-jetty/
 
[INFO] Running TestSuite
[INFO] Tests run: 118, Failures: 1, Errors: 0, Skipped: 117, Time elapsed: 
22.934 sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 38, Failures: 1, Errors: 0, Skipped: 37, Time elapsed: 21.458 
sec <<< FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 21.135 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 1, Errors: 0, Skipped: 3, Time elapsed: 21.141 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 1, Errors: 0, Skipped: 3, Time elapsed: 21.042 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 9, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 21.169 
sec <<< FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 21.053 
sec <<< FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 11, Failures: 1, Errors: 0, Skipped: 10, Time elapsed: 21.172 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 38, Failures: 1, Errors: 0, Skipped: 37, Time elapsed: 21.601 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 6, Failures: 1, Errors: 0, Skipped: 5, Time elapsed: 21.224 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 21.054 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 21.02 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 3, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 21.137 
sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 5, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 21.392 
sec <<< FAILURE!
 
Samples: branches/2.2
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100728/samples-2000.log
 
Build status: FAILED