[jira] Resolved: (GERONIMO-5544) Geronimo 3.0 console-testsuite/advanced WebServerTest testEditConnector fail. The Network Listeners can not edit.

2010-09-14 Thread Delos Dai (JIRA)

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

Delos Dai resolved GERONIMO-5544.
-

Resolution: Fixed

Connector gbean can't be found when user hopes to update port number. Just 
query the gbean with abstract name, then it works.  Commit the fix in revision 
#996786

 Geronimo 3.0 console-testsuite/advanced WebServerTest testEditConnector fail. 
 The Network Listeners can not edit.
 -

 Key: GERONIMO-5544
 URL: https://issues.apache.org/jira/browse/GERONIMO-5544
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: testsuite
Affects Versions: 3.0
 Environment: OS:ubuntu 8.04
 JVM:sun 1.6.0_20
 Server:geronimo-tomcat7-javaee6-3.0-SNAPSHOT build at 
 2010.08.20-09:46:01.318+0800
Reporter: janel Zhang
Assignee: Delos Dai
 Fix For: 3.0


 1.Create a new Tomcat BIO HTTP Connector through  
 geronimo-tomcat7-javaee6-3.0-SNAPSHOT console:ServerWeb ServerAdd 
 New Tomcat BIO HTTP Connector(name:uniquename2,port 8082)
 2.Edit the uniquename2's port to 8083,but it can not take effect and the port 
 can not edit.

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



[jira] Created: (GERONIMO-5607) geronimo-default keystore file not displayed on the administration console

2010-09-14 Thread maojia (JIRA)
geronimo-default keystore file not displayed on the administration console
--

 Key: GERONIMO-5607
 URL: https://issues.apache.org/jira/browse/GERONIMO-5607
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 3.0
 Environment: Windows platform
Reporter: maojia
Priority: Minor


The geronimo-default keystore file is not displayed on the Keystore portlet on 
the administration console.

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



[jira] Created: (GERONIMO-5608) Update connector attribute list for Tomcat 7

2010-09-14 Thread Delos Dai (JIRA)
Update connector attribute list for Tomcat 7


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


Need to update connector attribute list in TomcatManagerImpl.java per list here 
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html

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



[CANCELED] [VOTE] release javamail 1.8.2 provider and mail components.

2010-09-14 Thread Rick McGuire

 Will restart the vote with a version built using java 5.

Rick

On 9/10/2010 8:04 AM, Rick McGuire wrote:
 This is a bug fix release to fix a problem with the javamail smtp 
provider including the BCC recipients as a header in sent messages.  
The JIRA in question is


https://issues.apache.org/jira/browse/GERONIMO-5587

This is a vote for the javamail providers and combined mail jar.  This 
fix did not require an update to the javamail specs. .


The 2 components up for vote are:

org/apache/geronimo/javamail/geronimo-javamail_1.4_mail/1.8.2/geronimo-javamail_1.4_mail-1.8.2-sources.jar 

org/apache/geronimo/javamail/geronimo-javamail_1.4_provider/1.8.2/geronimo-javamail_1.4_provider-1.8.2-sources.jar 



from the staging repository at:

https://repository.apache.org/content/repositories/orgapachegeronimo-008/

The source repo is:

https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.8.2/ 



 Vote will be open for 72 hours.

 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)


Rick





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

2010-09-14 Thread viola.lu (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909193#action_12909193
 ] 

viola.lu commented on GERONIMO-5479:


Got response from myfaces and tomcat, it's EL implementation problem, geronimo 
just provides el api, use tomcat el implementation, so open a bug on tomcat to 
track it:
https://issues.apache.org/bugzilla/show_bug.cgi?id=49925

 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
 Environment: OS: Windows XP SP3, JDK: sun-jdk-1.6.0_18
Reporter: Wang Guang Zhe
Assignee: viola.lu
Priority: Minor
 Fix For: 3.0


 I create a simple JSF app to test this new feature. You can check it out from 
 trunk: testsuite/javaee6-testsuite/el2.2-test which has been committed at 
 revision 980368.  
 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)
   

[VOTE] release javamail 1.8.2 provider and mail components. (second attempt)

2010-09-14 Thread Rick McGuire
 This is a bug fix release to fix a problem with the javamail smtp 
provider including the BCC recipients as a header in sent messages.  The 
JIRA in question is


https://issues.apache.org/jira/browse/GERONIMO-5587

This is a vote for the javamail providers and combined mail jar.  This 
fix did not require an update to the javamail specs. .


The 2 components up for vote are:

org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.2/geronimo-javamail_1.4-1.8.2-source-release.tar.gz
org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.2/geronimo-javamail_1.4-1.8.2-source-release.zip

from the staging repository at:

https://repository.apache.org/content/repositories/orgapachegeronimo-020/

The source repo is:

https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.8.2/ 



 Vote will be open for 72 hours.

 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)


Rick



[BUILD] trunk: Failed for Revision: 996730

2010-09-14 Thread gawor
Geronimo Revision: 996730 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100913/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100913
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 37 minutes 9 seconds
[INFO] Finished at: Mon Sep 13 21:42:25 EDT 2010
[INFO] Final Memory: 458M/1003M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100913/logs-2100-tomcat/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.004 sec  
FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100913/logs-2100-jetty/
 
 
Samples: trunk
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100913/samples-2100.log
 
Build status: FAILED
 


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

2010-09-14 Thread gawor
Geronimo Revision: 996616 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100913/build-1400.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100913
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 34 minutes 21 seconds
[INFO] Finished at: Mon Sep 13 14:41:52 EDT 2010
[INFO] Final Memory: 305M/974M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100913/logs-1400-tomcat/
 
[INFO] Running TestSuite
[INFO] Tests run: 40, Failures: 31, Errors: 0, Skipped: 0, Time elapsed: 
189.195 sec  FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 12, Failures: 10, Errors: 0, Skipped: 0, Time elapsed: 65.575 
sec  FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100913/logs-1400-jetty/
 
[INFO] Running TestSuite
[INFO] Tests run: 116, Failures: 3, Errors: 0, Skipped: 113, Time elapsed: 
15.763 sec  FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 12, Failures: 10, Errors: 0, Skipped: 0, Time elapsed: 64.521 
sec  FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 7.771 
sec  FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.568 
sec  FAILURE!
 
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] snapshot org.apache.openejb:openejb-core:3.1.3-SNAPSHOT: checking for 
updates from codehaus-snapshot
[INFO] snapshot org.apache.openejb:openejb-core:3.1.3-SNAPSHOT: checking for 
updates from apache-m2-snapshot
[INFO] snapshot org.apache.openejb:openejb-core:3.1.3-SNAPSHOT: checking for 
updates from java.net
[INFO] snapshot org.apache.openejb:container:3.1.3-SNAPSHOT: checking for 
updates from codehaus-snapshot
[INFO] snapshot org.apache.openejb:container:3.1.3-SNAPSHOT: checking for 
updates from apache-m2-snapshot
[INFO] snapshot org.apache.openejb:container:3.1.3-SNAPSHOT: checking for 
updates from java.net
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [:invoke {execution: default}]
[INFO] Invoking: 
/home/geronimo/geronimo/2.2/testsuite/cluster-testsuite/ejb-multicast/pom.xml
[INFO] + Error stacktraces are turned on.
[INFO] [INFO] Scanning for projects...
[INFO] [INFO] 

[INFO] [INFO] Building Geronimo TestSuite :: Cluster Testsuite :: EJB Multicast 
Tests
[INFO] [INFO]task-segment: [install]
[INFO] [INFO] 

[INFO] [INFO] [genesis:validate-configuration {execution: default}]
[INFO] [INFO] [enforcer:enforce {execution: default}]
[INFO] [INFO] Setting property: classpath.resource.loader.class = 
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] [INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] [INFO] Setting property: resource.loader = 'classpath'.
[INFO] [INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [INFO] [remote-resources:process {execution: default}]
[INFO] [INFO] [resources:resources {execution: default-resources}]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 1 resource
[INFO] [INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/testsuite/cluster-testsuite/ejb-multicast/src/main/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [compiler:compile {execution: default-compile}]
[INFO] [INFO] No sources to compile
[INFO] [INFO] [resources:testResources {execution: default-testResources}]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/testsuite/cluster-testsuite/ejb-multicast/src/test/resources
[INFO] [INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/testsuite/cluster-testsuite/ejb-multicast/src/test/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [antrun:run {execution: create-server-instance}]
[INFO] [INFO] Executing tasks
[INFO] 
[INFO] linux:
[INFO]  [echo] 
#
[INFO]  [echo] ##   

[INFO]  [echo] ## Unzipping: assembly 

Re: [VOTE] release javamail 1.8.2 provider and mail components. (second attempt)

2010-09-14 Thread Kevan Miller
+1 Same checks as before -- source, signature, checksum, build -- all look good.

BTW, nice catch Ivan! 

--kevan

On Sep 14, 2010, at 7:43 AM, Rick McGuire wrote:

 This is a bug fix release to fix a problem with the javamail smtp provider 
 including the BCC recipients as a header in sent messages.  The JIRA in 
 question is
 
 https://issues.apache.org/jira/browse/GERONIMO-5587
 
 This is a vote for the javamail providers and combined mail jar.  This fix 
 did not require an update to the javamail specs. .
 
 The 2 components up for vote are:
 
 org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.2/geronimo-javamail_1.4-1.8.2-source-release.tar.gz
 org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.2/geronimo-javamail_1.4-1.8.2-source-release.zip
 
 from the staging repository at:
 
 https://repository.apache.org/content/repositories/orgapachegeronimo-020/
 
 The source repo is:
 
 https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.8.2/
  
 
 Vote will be open for 72 hours.
 
 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)
 
 
 Rick
 



Re: [VOTE] release javamail 1.8.2 provider and mail components. (second attempt)

2010-09-14 Thread Donald Woods
+1  Could build from source and staged jars look good.


-Donald


On 9/14/10 7:43 AM, Rick McGuire wrote:
  This is a bug fix release to fix a problem with the javamail smtp
 provider including the BCC recipients as a header in sent messages.  The
 JIRA in question is
 
 https://issues.apache.org/jira/browse/GERONIMO-5587
 
 This is a vote for the javamail providers and combined mail jar.  This
 fix did not require an update to the javamail specs. .
 
 The 2 components up for vote are:
 
 org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.2/geronimo-javamail_1.4-1.8.2-source-release.tar.gz
 
 org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.2/geronimo-javamail_1.4-1.8.2-source-release.zip
 
 
 from the staging repository at:
 
 https://repository.apache.org/content/repositories/orgapachegeronimo-020/
 
 The source repo is:
 
 https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.8.2/
 
 
  Vote will be open for 72 hours.
 
  [ ] +1  approve
  [ ] +0  no opinion
  [ ] -1  disapprove (and reason why)
 
 
 Rick
 
 


[jira] Commented: (GERONIMO-5606) Bad persistenceUnitRoot for PUs in jars embedded in WARs

2010-09-14 Thread Jarek Gawor (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909431#action_12909431
 ] 

Jarek Gawor commented on GERONIMO-5606:
---

I updated (in revision 997064 and 997066) the jpa test case to demonstrate the 
META-INF/orm.xml discovery problem when the persistenceUnitRoot of a PU is 
computed incorrectly.


 Bad persistenceUnitRoot for PUs in jars embedded in WARs
 

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


 The persistenceUnitRoot for PUs in jars embedded in WARs is computed 
 incorrectly which for example causes the META-INF/orm.xml files not to be 
 discovered by OpenJPA.

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



[jira] Commented: (GERONIMO-5606) Bad persistenceUnitRoot for PUs in jars embedded in WARs

2010-09-14 Thread Jarek Gawor (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909435#action_12909435
 ] 

Jarek Gawor commented on GERONIMO-5606:
---

In revision 997073 I committed a set of changes that represent an attempt at 
fixing the persistenceUnitRoot problem. If a persistence.xml is discovered 
within a jar file, the persistenceUnitRoot of the PU will be a jar type of 
URL. The classloader of the PU is also changed to BundleResourceClassLoader 
which returns jar type of URLs for resources embedded in jar files. Because 
the persistenceUnitRoot URL is now consistent with the URLs returned by 
BundleResourceClassLoader, OpenJPA can successfully discover the orm.xml file 
and other resources.


 Bad persistenceUnitRoot for PUs in jars embedded in WARs
 

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


 The persistenceUnitRoot for PUs in jars embedded in WARs is computed 
 incorrectly which for example causes the META-INF/orm.xml files not to be 
 discovered by OpenJPA.

-- 
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: 997043

2010-09-14 Thread gawor
Geronimo Revision: 997043 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100914/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100914
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 41 minutes 24 seconds
[INFO] Finished at: Tue Sep 14 15:44:21 EDT 2010
[INFO] Final Memory: 458M/1002M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100914/logs-1500-tomcat/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 10.918 sec  
FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100914/logs-1500-jetty/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 10.977 sec  
FAILURE!
Running TestSuite
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.142 sec  
FAILURE!
 
Samples: trunk
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100914/samples-1500.log
 
Build status: OK
 


Re: [VOTE] release javamail 1.8.2 provider and mail components. (second attempt)

2010-09-14 Thread Ivan
+1 The jar looks good.

2010/9/15 Donald Woods dwo...@apache.org

 +1  Could build from source and staged jars look good.


 -Donald


 On 9/14/10 7:43 AM, Rick McGuire wrote:
   This is a bug fix release to fix a problem with the javamail smtp
  provider including the BCC recipients as a header in sent messages.  The
  JIRA in question is
 
  https://issues.apache.org/jira/browse/GERONIMO-5587
 
  This is a vote for the javamail providers and combined mail jar.  This
  fix did not require an update to the javamail specs. .
 
  The 2 components up for vote are:
 
 
 org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.2/geronimo-javamail_1.4-1.8.2-source-release.tar.gz
 
 
 org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.2/geronimo-javamail_1.4-1.8.2-source-release.zip
 
 
  from the staging repository at:
 
 
 https://repository.apache.org/content/repositories/orgapachegeronimo-020/
 
  The source repo is:
 
 
 https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.8.2/
 
 
   Vote will be open for 72 hours.
 
   [ ] +1  approve
   [ ] +0  no opinion
   [ ] -1  disapprove (and reason why)
 
 
  Rick
 
 




-- 
Ivan


Do we need to support ManagedBean annotation ?

2010-09-14 Thread Ivan
Hi,
Currently, all the annotation scan is done by Myfaces while starting the
application, which means those managed bean with any naming injection will
not work.  The interesting thing is that there is no word for the
ManagedBean annotation in the jsf spec and we pass all the jsf tck cases,
after googled, got some history info for that anntation class, also find
some descriptions from the api doc below :
---

These javadoc files constitute the “Faces Managed Bean Annotation
Specification for Containers Conforming to Servlet 2.5 and Beyond”

At the time of this writing, a forthcoming JCP effort is being planned to
extract the specification for managed beans from JSF and place it into its
own specification. To account for this effort and to avoid introducing
classes into JSF 2.0 that would have to be deprecated when this effort is
complete, implementations of JSF 2.0 are not required to implement the
“Faces Managed Bean Annotation Specification for Containers Conforming to
Servlet 2.5”. However, JSF implementations are strongly encouraged to
implement this specification, as it provides significant improvements in
ease of use.

The annotations must be processed as specified in section JSF.11.5.1.

---
It seems that it is not required to support ManagedBean annotation in the
impl, and guess that is why we did not get any error in the jsf tck :-)
So I am thinking whether we need to support this in Geronimo, and actually,
once we integrated the web beans, it should be able to use web bean
annotations.
Thoughts ?

-- 
Ivan


Re: [VOTE] release javamail 1.8.2 provider and mail components. (second attempt)

2010-09-14 Thread Shawn Jiang
+1

The jars looks OK and I could build the source successfully.

On Tue, Sep 14, 2010 at 7:43 PM, Rick McGuire rick...@gmail.com wrote:

  This is a bug fix release to fix a problem with the javamail smtp provider
 including the BCC recipients as a header in sent messages.  The JIRA in
 question is

 https://issues.apache.org/jira/browse/GERONIMO-5587

 This is a vote for the javamail providers and combined mail jar.  This fix
 did not require an update to the javamail specs. .

 The 2 components up for vote are:


 org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.2/geronimo-javamail_1.4-1.8.2-source-release.tar.gz

 org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.2/geronimo-javamail_1.4-1.8.2-source-release.zip

 from the staging repository at:

 https://repository.apache.org/content/repositories/orgapachegeronimo-020/

 The source repo is:


 https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.8.2/

  Vote will be open for 72 hours.

  [ ] +1  approve
  [ ] +0  no opinion
  [ ] -1  disapprove (and reason why)


 Rick




-- 
Shawn


[jira] Assigned: (GERONIMO-5435) Could not package plugin when build sample javaee5\bank

2010-09-14 Thread Ivan (JIRA)

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

Ivan reassigned GERONIMO-5435:
--

Assignee: Ivan

 Could not package plugin when build sample javaee5\bank
 ---

 Key: GERONIMO-5435
 URL: https://issues.apache.org/jira/browse/GERONIMO-5435
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: car-maven-plugin
 Environment: winXP (english) + sun sdk 1.6.0._20
Reporter: Han Hong Fang
Assignee: Ivan
 Fix For: 3.0-M1


 If you try to build any EJB sample's geronimo plugin, you will get exception 
 as below
 [INFO] 
 
 [ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] could not package plugin
 Embedded error: org.apache.openejb.OpenEJBException: Failed Configuring 
 Service(id=DefaultStatelessContainer): Unable to read OpenEJB service-jar 
 file for provider org.apache.openejb at null: Could not find resource 
 'META-INF/org.apache.openejb/service-jar.xml'
 [INFO] 
 
 [INFO] Trace
 org.apache.maven.lifecycle.LifecycleExecutionException: could not package 
 plugin
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
   at 
 org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
   at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 Caused by: org.apache.maven.plugin.MojoExecutionException: could not package 
 plugin
   at 
 org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.java:246)
   at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
   at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
   ... 17 more
 Caused by: org.apache.geronimo.common.DeploymentException: 
 org.apache.openejb.OpenEJBException: Failed Configuring 
 Service(id=DefaultStatelessContainer): Unable to read OpenEJB service-jar 
 file for provider org.apache.openejb at null: Could not find resource 
 'META-INF/org.apache.openejb/service-jar.xml'
   at 
 org.apache.geronimo.openejb.deployment.EjbModuleBuilder.getEjbJarInfo(EjbModuleBuilder.java:601)
   at 
 org.apache.geronimo.openejb.deployment.EjbModuleBuilder.initContext(EjbModuleBuilder.java:509)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:630)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
   at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:856)
   at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
   at 
 

[jira] Updated: (GERONIMO-5578) incorrect behaviour of security-constraint configuration in web.xml

2010-09-14 Thread Han Hong Fang (JIRA)

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

Han Hong Fang updated GERONIMO-5578:


Attachment: GERONIMO-5578.patch

A WebResourcePermission must be added to the corresponding role for each 
distinct combination in the cross-product of url-pattern and role-name 
occurring in the security-constraint elements that contain an auth-constraint 
naming roles.  (ref to chapter 3.1.3.2 of JACC v1.4 spec). 

The problem existed becaused all role-name shared a WebResourcePermission for 
each url-pattern.

The patch is provided together with junit test case.

Please help to review. Thanks!

 incorrect behaviour of security-constraint configuration in web.xml 
 

 Key: GERONIMO-5578
 URL: https://issues.apache.org/jira/browse/GERONIMO-5578
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Tomcat
Affects Versions: 3.0
Reporter: Han Hong Fang
Assignee: Han Hong Fang
 Attachments: GERONIMO-5578.patch


 When have following configuration in web.xml, GET and POST can be accessed by 
 both RoleA and RoleB.
 security-constraint
 web-resource-collection
 web-resource-nameresource2/web-resource-name
 url-pattern/SampleServlet2/url-pattern
 http-methodGET/http-method
 /web-resource-collection
 auth-constraint
 role-nameRoleA/role-name
 /auth-constraint
 /security-constraint
 
 security-constraint
 web-resource-collection
 web-resource-nameresource3/web-resource-name
 url-pattern/SampleServlet2/url-pattern
 http-methodPOST/http-method
 /web-resource-collection
 auth-constraint
 role-nameRoleB/role-name
 /auth-constraint
 /security-constraint

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



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

2010-09-14 Thread gawor
Geronimo Revision: 997151 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100914/build-2000.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100914
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 34 minutes 25 seconds
[INFO] Finished at: Tue Sep 14 20:41:59 EDT 2010
[INFO] Final Memory: 311M/886M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100914/logs-2000-tomcat/
 
[INFO] Running TestSuite
[INFO] Tests run: 40, Failures: 33, Errors: 0, Skipped: 0, Time elapsed: 
173.393 sec  FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 12, Failures: 6, Errors: 0, Skipped: 0, Time elapsed: 88.429 
sec  FAILURE!
--
[INFO] Running TestSuite
[INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 68.732 
sec  FAILURE!
 
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] snapshot org.apache.openejb:openejb-core:3.1.3-SNAPSHOT: checking for 
updates from codehaus-snapshot
[INFO] snapshot org.apache.openejb:openejb-core:3.1.3-SNAPSHOT: checking for 
updates from apache-m2-snapshot
[INFO] snapshot org.apache.openejb:openejb-core:3.1.3-SNAPSHOT: checking for 
updates from java.net
[INFO] snapshot org.apache.openejb:container:3.1.3-SNAPSHOT: checking for 
updates from codehaus-snapshot
[INFO] snapshot org.apache.openejb:container:3.1.3-SNAPSHOT: checking for 
updates from apache-m2-snapshot
[INFO] snapshot org.apache.openejb:container:3.1.3-SNAPSHOT: checking for 
updates from java.net
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [:invoke {execution: default}]
[INFO] Invoking: 
/home/geronimo/geronimo/2.2/testsuite/cluster-testsuite/ejb-multicast/pom.xml
[INFO] + Error stacktraces are turned on.
[INFO] [INFO] Scanning for projects...
[INFO] [INFO] 

[INFO] [INFO] Building Geronimo TestSuite :: Cluster Testsuite :: EJB Multicast 
Tests
[INFO] [INFO]task-segment: [install]
[INFO] [INFO] 

[INFO] [INFO] [genesis:validate-configuration {execution: default}]
[INFO] [INFO] [enforcer:enforce {execution: default}]
[INFO] [INFO] Setting property: classpath.resource.loader.class = 
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] [INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] [INFO] Setting property: resource.loader = 'classpath'.
[INFO] [INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [INFO] [remote-resources:process {execution: default}]
[INFO] [INFO] [resources:resources {execution: default-resources}]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 1 resource
[INFO] [INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/testsuite/cluster-testsuite/ejb-multicast/src/main/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [compiler:compile {execution: default-compile}]
[INFO] [INFO] No sources to compile
[INFO] [INFO] [resources:testResources {execution: default-testResources}]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/testsuite/cluster-testsuite/ejb-multicast/src/test/resources
[INFO] [INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/testsuite/cluster-testsuite/ejb-multicast/src/test/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [antrun:run {execution: create-server-instance}]
[INFO] [INFO] Executing tasks
[INFO] 
[INFO] linux:
[INFO]  [echo] 
#
[INFO]  [echo] ##   

[INFO]  [echo] ## Unzipping: assembly   
  
[INFO]  [echo] ##   

[INFO]  [echo] 
#
[INFO] [mkdir] Created dir: 
/home/geronimo/geronimo/2.2/testsuite/cluster-testsuite/ejb-multicast/server1
[INFO][gunzip] Expanding 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2.2-SNAPSHOT-bin.tar.gz

[jira] Assigned: (GERONIMO-5548) Default user monitor can't login admin console in Geronimo_3.0_trunk

2010-09-14 Thread Han Hong Fang (JIRA)

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

Han Hong Fang reassigned GERONIMO-5548:
---

Assignee: Han Hong Fang

  Default user monitor can't login admin console in Geronimo_3.0_trunk 
 

 Key: GERONIMO-5548
 URL: https://issues.apache.org/jira/browse/GERONIMO-5548
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: security
Affects Versions: 3.0
 Environment: OS:Windows XP SP3
 Java Version: 1.6.0_20
 Server:Geronimo 3.0-SNAPSHOT 
Reporter: Zhen Zhang
Assignee: Han Hong Fang
Priority: Minor
 Fix For: 3.0


 setps to recur:
 1. startup the Geronimo server
 2. open http://localhost:8080/console;
 3. login with User name monitor and default password password
 4.you will find :
 HTTP Status 403 -
 type Status report
 message
 description Access to the specified resource () has been forbidden.

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



[jira] Commented: (GERONIMO-5557) Add more context level configurations for Tomcat

2010-09-14 Thread viola.lu (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909570#action_12909570
 ] 

viola.lu commented on GERONIMO-5557:


Based on Ivan's advice, more context level support makes TomcatWebAppContext 
constructor more complicated, so will try to follow HostGbean using reflection 
and IntrospectionUtils.setProperty , make code simpler.

 Add more context level configurations for Tomcat
 

 Key: GERONIMO-5557
 URL: https://issues.apache.org/jira/browse/GERONIMO-5557
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2.2, 3.0
Reporter: Ivan
Assignee: viola.lu
 Attachments: G5557.patch


 In the latest Tomcat build, more paramter could be configured on the context 
 level
 A request thread in user-geronimo mail list : 
 http://osdir.com/ml/user-geronimo-apache/2010-08/msg3.html

-- 
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: 997162

2010-09-14 Thread gawor
Geronimo Revision: 997162 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100914/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100914
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 35 minutes 40 seconds
[INFO] Finished at: Tue Sep 14 21:41:00 EDT 2010
[INFO] Final Memory: 457M/992M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100914/logs-2100-tomcat/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.005 sec  
FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100914/logs-2100-jetty/
 
Running TestSuite
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.042 sec  
FAILURE!
Running TestSuite
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.064 sec  
FAILURE!
--
Running TestSuite
Tests run: 9, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 170.516 sec  
FAILURE!
 
Samples: trunk
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100914/samples-2100.log
 
Build status: OK
 


[jira] Created: (GERONIMO-5609) Improve web application deployment time

2010-09-14 Thread viola.lu (JIRA)
Improve web application deployment time
---

 Key: GERONIMO-5609
 URL: https://issues.apache.org/jira/browse/GERONIMO-5609
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: web
Affects Versions: 3.0
 Environment: OS: winxp
JDK: 1.6.0_20

Reporter: viola.lu
Assignee: viola.lu
Priority: Minor
 Fix For: 3.0


Currently, a simple web application deployment time seems longer that previous 
version. So open a jira to track this issue.

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