Re: svn commit: r906902 - in /geronimo/specs/trunk: geronimo-atinject_1.0_spec/src/main/java/javax/inject/ geronimo-el_2.2_spec/src/main/java/javax/el/ geronimo-jcdi_1.0_spec/ geronimo-jcdi_1.0_spec/s
I went ahead to commit the changes of
*GERONIMO-5657https://issues.apache.org/jira/browse/GERONIMO-5657
*
If any problem, please figure it out, thanks.
2010/10/20 Ivan xhh...@gmail.com
I found some changes have been done to the el package, From the comments,
the changes are for jcdi and atinject, is it also required by the signature
testing ? IMO, the changes should not be required.
Thanks.
2010/2/5 rickmcgu...@apache.org
Author: rickmcguire
Date: Fri Feb 5 11:23:22 2010
New Revision: 906902
URL: http://svn.apache.org/viewvc?rev=906902view=rev
Log:
GERONIMO-5121 Update geronimo-jcdi and geronimo-atinject to pass TCK
Signature Tests
Patch provided by Gurkan Erdogdu
Modified:
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Inject.java
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Named.java
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Qualifier.java
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Scope.java
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Singleton.java
geronimo/specs/trunk/geronimo-el_2.2_spec/src/main/java/javax/el/CompositeELResolver.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/pom.xml
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/context/BusyConversationException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/context/ContextException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/context/ContextNotActiveException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/context/NonexistentConversationException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/event/ObserverException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/inject/AmbiguousResolutionException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/inject/CreationException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/inject/IllegalProductException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/inject/InjectionException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/inject/ResolutionException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/inject/UnproxyableResolutionException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/inject/UnsatisfiedResolutionException.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/inject/spi/InterceptionType.java
geronimo/specs/trunk/geronimo-jcdi_1.0_spec/src/main/java/javax/enterprise/inject/spi/SessionBeanType.java
Modified:
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Inject.java
URL:
http://svn.apache.org/viewvc/geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Inject.java?rev=906902r1=906901r2=906902view=diff
==
---
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Inject.java
(original)
+++
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Inject.java
Fri Feb 5 11:23:22 2010
@@ -30,9 +30,9 @@
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
-...@documented
@Target(value={ElementType.METHOD,ElementType.CONSTRUCTOR,ElementType.FIELD})
@Retention(value=RetentionPolicy.RUNTIME)
+...@documented
public @interface Inject
{
Modified:
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Named.java
URL:
http://svn.apache.org/viewvc/geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Named.java?rev=906902r1=906901r2=906902view=diff
==
---
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Named.java
(original)
+++
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Named.java
Fri Feb 5 11:23:22 2010
@@ -35,9 +35,9 @@
* given webbeans component, its name is null.
* /p
*/
+...@qualifier
@Documented
@Retention(value=RetentionPolicy.RUNTIME)
-...@qualifier
public @interface Named
{
Modified:
geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Qualifier.java
URL:
http://svn.apache.org/viewvc/geronimo/specs/trunk/geronimo-atinject_1.0_spec/src/main/java/javax/inject/Qualifier.java?rev=906902r1=906901r2=906902view=diff
==
---
[BUILD] trunk: Failed for Revision: 1024538
Geronimo Revision: 1024538 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020/unit-test-reports 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.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.openwebbeans:openwebbeans-ejb-common:jar': Cannot find parent: org.apache.openwebbeans:openwebbeans for project: null:openwebbeans-ejb-common:jar:1.0.0-SNAPSHOT for project null:openwebbeans-ejb-common:jar:1.0.0-SNAPSHOT org.apache.openwebbeans:openwebbeans-ejb-common:jar:1.0.0-SNAPSHOT from the specified remote repositories: openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), java.net (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), JBoss Repository (https://repository.jboss.org/nexus/content/groups/public-jboss/), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/), openejb-3rdparty-builds (http://svn.apache.org/repos/asf/openejb/repo/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), central (http://repo1.maven.org/maven2), local (file:///home/geronimo/.m2/jtidy.repository), apache-m2-snapshot (http://repository.apache.org/snapshots/), openqa-releases (http://nexus.openqa.org/content/repositories/releases) Path to dependency: 1) org.apache.geronimo.modules:geronimo-openejb:bundle:3.0-SNAPSHOT 2) org.apache.openejb:openejb-core:jar:3.2-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:430) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:435) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:316) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1499) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'org.apache.openwebbeans:openwebbeans-ejb-common:jar': Cannot find parent: org.apache.openwebbeans:openwebbeans for project: null:openwebbeans-ejb-common:jar:1.0.0-SNAPSHOT for project null:openwebbeans-ejb-common:jar:1.0.0-SNAPSHOT at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:200) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedArtifact(MavenMetadataSource.java:94) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:387) ... 24 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.apache.openwebbeans:openwebbeans for project: null:openwebbeans-ejb-common:jar:1.0.0-SNAPSHOT for project null:openwebbeans-ejb-common:jar:1.0.0-SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:255) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:163) ... 26 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.openwebbeans:openwebbeans' not found in repository: Unable to download the artifact from any repository org.apache.openwebbeans:openwebbeans:pom:1.0.0-SNAPSHOT from the specified remote repositories: openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo
[jira] Commented: (GERONIMO-5604) Failed to expand deploy failed information in Deployer porlet if fail to deploy an application with Firefox and IE 6.0
[
https://issues.apache.org/jira/browse/GERONIMO-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12922893#action_12922893
]
viola.lu commented on GERONIMO-5604:
This issue is cozed by https://issues.apache.org/jira/browse/GERONIMO-5563
patch, which automatically add target=_parent in IE and firefox:
if(link != null link.indexOf(/console/portal/)==-1){
if (document.all) {//IE
elements[i].target=_parent;
} else if (document.getElementById) { //firefox
elements[i].setAttribute(target, _parent);
}
}
Failed to expand deploy failed information in Deployer porlet if fail to
deploy an application with Firefox and IE 6.0
Key: GERONIMO-5604
URL: https://issues.apache.org/jira/browse/GERONIMO-5604
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 3.0
Environment: OS: winxp,
Firefox 3.5.12, IE 6.0
Reporter: viola.lu
Assignee: viola.lu
Fix For: 3.0
1.Deploy an txt file, it's deployed failed with error message: The
application was not deployed.
2.Click + before the The application was not deployed., but it just shows
the javascript: show/hide at the bottom of browser, no any response, but
it works on google chrome
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: svn commit: r1025519 - /geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java
Hmm, I do not see this scenario exists, currentPattern is never used while
calculating the role based security.
Do we get any cases failed ?
2010/10/20 genspr...@apache.org
Author: genspring
Date: Wed Oct 20 11:55:31 2010
New Revision: 1025519
URL: http://svn.apache.org/viewvc?rev=1025519view=rev
Log:
Somehow, once currentRolePatterns = new HashMapString, URLPattern(); is
executed.currentPatterns will point to the same reference of
currentRolePatterns.
Pull (currentPatterns ==null) out of the loop to avoid the unexpected logic
caused by the problem above.
Modified:
geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java
Modified:
geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java?rev=1025519r1=1025518r2=1025519view=diff
==
---
geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java
(original)
+++
geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java
Wed Oct 20 11:55:31 2010
@@ -108,10 +108,13 @@ public class SpecSecurityBuilder {
currentPatterns = uncheckedPatterns;
}
String transport = securityConstraint.userDataConstraint ==
null ? NONE : securityConstraint.userDataConstraint;
+
+boolean isRolebasedPatten = (currentPatterns == null);
+
for (WebResourceCollectionInfo webResourceCollection :
securityConstraint.webResourceCollections) {
//Calculate HTTP methods list
for (String urlPattern : webResourceCollection.urlPatterns)
{
-if (currentPatterns == null) {
+if (isRolebasedPatten) {
for (String roleName : roleNames) {
MapString, URLPattern currentRolePatterns =
rolesPatterns.get(roleName);
if (currentRolePatterns == null) {
--
Ivan
[jira] Resolved: (GERONIMO-5604) Failed to expand deploy failed information in Deployer porlet if fail to deploy an application with Firefox and IE 6.0
[ https://issues.apache.org/jira/browse/GERONIMO-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-5604. --- Resolution: Fixed fixed with tr...@r1025516 2...@r1025517, thanks Viola for pointing out the root cause. Failed to expand deploy failed information in Deployer porlet if fail to deploy an application with Firefox and IE 6.0 Key: GERONIMO-5604 URL: https://issues.apache.org/jira/browse/GERONIMO-5604 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Environment: OS: winxp, Firefox 3.5.12, IE 6.0 Reporter: viola.lu Assignee: viola.lu Fix For: 3.0 1.Deploy an txt file, it's deployed failed with error message: The application was not deployed. 2.Click + before the The application was not deployed., but it just shows the javascript: show/hide at the bottom of browser, no any response, but it works on google chrome -- 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: 1024466
Geronimo Revision: 1024466 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101020/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101020/unit-test-reports [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.fileprofileactiva...@3c7a3c7a [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.jdkprefixprofileactiva...@3c7a3c7a Downloading: https://repository.apache.org/content/repositories/orgapacheopenejb-006//org/apache/cxf/cxf-tools-java2ws/2.1.10/cxf-tools-java2ws-2.1.10.jar [INFO] Unable to find resource 'org.apache.cxf:cxf-tools-java2ws:jar:2.1.10' in repository openejb313staging (https://repository.apache.org/content/repositories/orgapacheopenejb-006/) Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/cxf/cxf-tools-java2ws/2.1.10/cxf-tools-java2ws-2.1.10.jar 111K downloaded (cxf-tools-java2ws-2.1.10.jar) Downloading: https://repository.apache.org/content/repositories/orgapacheopenejb-006//org/apache/cxf/cxf-tools-wsdlto-core/2.1.10/cxf-tools-wsdlto-core-2.1.10.jar [INFO] Unable to find resource 'org.apache.cxf:cxf-tools-wsdlto-core:jar:2.1.10' in repository openejb313staging (https://repository.apache.org/content/repositories/orgapacheopenejb-006/) Downloading: http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/cxf/cxf
[BUILD] trunk: Failed for Revision: 1025544
Geronimo Revision: 1025544 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020/unit-test-reports [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.components:geronimo-jaspi:jar:1.2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-jaspi -Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-jaspi -Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:geronimo-security:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.components:geronimo-jaspi:jar:1.2-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.framework:geronimo-security:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) 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.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.components:geronimo-jaspi:jar:1.2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-jaspi -Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.components -DartifactId=geronimo-jaspi -Dversion=1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:geronimo-security:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.components:geronimo-jaspi:jar:1.2-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.framework:geronimo-security:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com
Re: Pull the latest Tomcat codes to our own repository
On Oct 20, 2010, at 2:25 AM, Ivan wrote: Just find an annoying change in the latest Tomcat codes, a class HTMLManagerServlet in the catalina package refers to a class in the catalina-ha. I plan to move this class to the catalina-ha package, seems that this class is not refered by any other classes in the Tomcat code base. or anyone has better ideas ? I expect that the following is your intention, but I think it's worth stating -- this should be taken up with the Tomcat community. Our goal should be to not have any long-term changes to Tomcat. We should be working with the Tomcat community to understand our problems and have our updates applied to Tomcat, not in our externals release. In this instance, I don't understand why HTMLManagerServlet needs to be aware of the specific Manager sub-class, at all. Seems like the Manager interface could have provided an appropriate method for retrieving the desired information. --kevan
Re: Pull the latest Tomcat codes to our own repository
Yes, I know it is better to solve this from its root, but from the experience in the past ... I will try. 2010/10/20 Kevan Miller kevan.mil...@gmail.com On Oct 20, 2010, at 2:25 AM, Ivan wrote: Just find an annoying change in the latest Tomcat codes, a class HTMLManagerServlet in the catalina package refers to a class in the catalina-ha. I plan to move this class to the catalina-ha package, seems that this class is not refered by any other classes in the Tomcat code base. or anyone has better ideas ? I expect that the following is your intention, but I think it's worth stating -- this should be taken up with the Tomcat community. Our goal should be to not have any long-term changes to Tomcat. We should be working with the Tomcat community to understand our problems and have our updates applied to Tomcat, not in our externals release. In this instance, I don't understand why HTMLManagerServlet needs to be aware of the specific Manager sub-class, at all. Seems like the Manager interface could have provided an appropriate method for retrieving the desired information. --kevan -- Ivan
Re: Is it possible to make those xml digest class serializable ?
Hi, devs, I posted some initial ideas to MYFACES-2945, and very appriciated with any comment :-) Once we have final result, I will try to create a patch. thanks. 2010/10/19 Jakob Korherr jakob.korh...@gmail.com Hi Ivan, Great to hear from the Geronimo team :) If you need some more than the currently available SPIs, please just create an issue in the JIRA and we'll take care of it! Regards, Jakob 2010/10/18 Leonardo Uribe lu4...@gmail.com: Hi Yes, please create an issue on myfaces issue tracker, so we can handle it there. Maybe the solution is add some methods on FaceletConfigResourceProvider, so you can provide the org.apache.myfaces.config.impl.digester.elements.FacesConfig file from a specified URL: public Object getFacesConfig(ExternalContext context, URL url) throws IOException; Suggestions are welcome. regards, Leonardo 2010/10/18 Ivan xhh...@gmail.com Yes, I moved this thread to the dev mail list. Those classes I mention are in the package org.apache.myfaces.config.impl.digester.elements, e.g. FacesConfig. From the source codes, it seems that they just hold some collection variables. I think that adding the serializable interface should not break the spec rules. If I missed anythings, please help to figure out. I found that MyFaces does provide some SPI classes, like AnnotationProvider, but I might need more. I hope to scan the annotation and combine all the configuration resources in the deployment process of Geronimo, and finally I got a object instance FacesConfig. While the applicaation starts, I just need to deserialize the instance. thanks. 2010/10/18 Werner Punz werner.p...@gmail.com Am 17.10.10 16:11, schrieb Ivan: Hi, I am looking at the integration work between myfaces and Geronimo, I am thinking that is it possible to make those xml digest class serializable, like FacesConfig, etc. So that, MyFaces could just scan annotation and sort configuration files once, and de-serialize those classes on each startup. Seems that only adding the serializable interface is enough. Thanks. Hi I think since this is integration work between myfaces and geronimo that it might be good to also post that in the developers list of myfaces. You might also raise a ticket for this issue. The main issue is simply that in the interface and API section we are bound by what the spec allows in the implementatiom section we can do mostly whatever we want as long as it does not break the API. Werner -- Ivan -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Ivan
[jira] Resolved: (GERONIMO-5612) Filter no permission functions for built-in user monitor
[ https://issues.apache.org/jira/browse/GERONIMO-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-5612. --- Resolution: Fixed Fix Version/s: 2.2.1 Fixed in 2...@r1025608 ,tr...@r1025609 Filter no permission functions for built-in user monitor -- Key: GERONIMO-5612 URL: https://issues.apache.org/jira/browse/GERONIMO-5612 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Reporter: Han Hong Fang Assignee: Shawn Jiang Fix For: 2.2.1, 3.0 Login admin console with monitor/password, then click advance radio button at the top of nagivation tree area There are some functions on navigation tree, which monitor has no permission to access, such as Application Server/Shutdown. Once this item is clicked, following error occurs: HTTP Status 403 - type Status report message description Access to the specified resource () has been forbidden. Need to filter such functions for monitor to avoid this error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Is it possible to make those xml digest class serializable ?
Hi
Some answers to your post below:
IV Just some ideas for the integration improvment, please help to give
some comments.
IV a. Create a new SPI provider and a provider factory, might name
FacesConfigurationProvider/
IV FacesConfigurationProviderFactory, which has a method
IV FacesConfig getFacesConfig(ExternalContext context);
IVThis method is designed to get the final combined the FacesConfig
instance, which including
IV application resource configuration + annotation + default web
application resource
IV And move those logic about merge/annotaiton scanning from
FacesConfigurator and
IV AnnotationConfigurator to the default implementation provider
Yes, it could be good to have another SPI provider in this case, but I don't
know how that interface should
looks like. In theory, at some point we have a consolidate FacesConfig, but
without the annotation information.
The reason is not all information provided by annotations is on
faces-config.xml format.
IV b. Make some classes in the
org.apache.myfaces.config.impl.digester.elements package serializable,
IV this might be optional...
IV From the integration side, the third-party container could implement
their own
IV FacesConfigurationProvider, they might return the FacesConfig object
directly from their own structure.
Yes, it could be good to provide a way to expose that configuration
information.
IV c. I saw some codes in the ***ProviderFactory is commented out,
IV//AnnotationProviderFactory instance = (AnnotationProviderFactory)
ctx.getApplicationMap().get(FACTORY_KEY);
IV//if (instance != null)
IV//{
IV//return instance;
IV//}
IV Did it cause any issue ? Or I hope to recover them, as it will be
more easier to set other implemtations
IV for other containers. The commons-discovery package might not work
correctly in OSGI environment. as they
IV will try to search META-INF/services folder, and this way sometimes
might not work correctly in OSGi environment.
IV thanks.
I commented that code because AnnotationProviderFactory,
FaceletConfigResourceProviderFactory
and FacesConfigResourceProviderFactory are only used once in the application
lifetime (during initialization)
so it does not have sense to put them on application map.
In theory, it should work even in OSGi. The reason is to JSF work correctly
in OSGi, it should be provided a
ThreadContextClassLoader (TCCL) that could find resources all bundles that
the web application uses. That's necessary
to make javax.faces.FactoryFinder class work correctly, and it is know that
libraries like SpringDM, or containers like
GlassFish do that to keep code working. Unfortunately, there is no other
option because by the spec it is not possible to
change the way FactoryFinder works (I can't add a BundleActivator on
myfaces-api.jar because this class is public-api).
regards,
Leonardo Uribe
2010/10/20 Ivan xhh...@gmail.com
Hi, devs, I posted some initial ideas to MYFACES-2945, and very appriciated
with any comment :-) Once we have final result, I will try to create a
patch.
thanks.
2010/10/19 Jakob Korherr jakob.korh...@gmail.com
Hi Ivan,
Great to hear from the Geronimo team :)
If you need some more than the currently available SPIs, please just
create an issue in the JIRA and we'll take care of it!
Regards,
Jakob
2010/10/18 Leonardo Uribe lu4...@gmail.com:
Hi
Yes, please create an issue on myfaces issue tracker, so we can handle
it
there. Maybe the solution is add some methods on
FaceletConfigResourceProvider, so you can provide the
org.apache.myfaces.config.impl.digester.elements.FacesConfig file from a
specified URL:
public Object getFacesConfig(ExternalContext context, URL url) throws
IOException;
Suggestions are welcome.
regards,
Leonardo
2010/10/18 Ivan xhh...@gmail.com
Yes, I moved this thread to the dev mail list.
Those classes I mention are in the package
org.apache.myfaces.config.impl.digester.elements, e.g. FacesConfig.
From the
source codes, it seems that they just hold some collection variables. I
think that adding the serializable interface should not break the spec
rules. If I missed anythings, please help to figure out.
I found that MyFaces does provide some SPI classes, like
AnnotationProvider, but I might need more. I hope to scan the
annotation and
combine all the configuration resources in the deployment process of
Geronimo, and finally I got a object instance FacesConfig. While the
applicaation starts, I just need to deserialize the instance.
thanks.
2010/10/18 Werner Punz werner.p...@gmail.com
Am 17.10.10 16:11, schrieb Ivan:
Hi,
I am looking at the integration work between myfaces and Geronimo,
I
am
thinking that is it possible to make those xml digest class
serializable,
like FacesConfig, etc. So that, MyFaces could just scan annotation
and
sort
configuration files once, and de-serialize those classes on each
startup.
Re: Bean Validation problems in trunk.
On Thu, Oct 14, 2010 at 9:49 PM, Vamsavardhana Reddy c1vams...@gmail.comwrote: On Thu, Oct 14, 2010 at 8:03 AM, Vamsavardhana Reddy c1vams...@gmail.comwrote: On Wed, Oct 13, 2010 at 11:47 PM, Rick McGuire rick...@gmail.com wrote: The recent changes to the bean validation support appear to be causing failures in both the TCK and the bean validation testsuite. I've tried to do a little problem determination, but I think Vamsi is probably going to need to take a look at this. In the testsuite failures, it looks to me that the validation factory configuration is not getting set up correctly so that not all of the constraints are getting applied in the tests. Many of the failures are just using the default constraint classes. I see that only those constraint classes that are within the same test project are being used in the validation, but the default ones are not. I will take a look at what is happening. As of rev 1005583 (by which the earlier test is reorganized and EJB test is added) the tests are passing. Rev 1005852 is the only other rev that touched plugins\bval, but the change in that rev seems to have not affected the test status. I will investigate further. When I start the server, I see one warning message indicating DefaultConstraints.properties could not be loaded... Starting Geronimo Application Server v3.0-SNAPSHOT [] 42% 10s Starting org.apache.ger...2010-10-20 22:19:07,359 WARN [ConstraintDefaults] cannot find org/apache/bval/jsr303/DefaultConstraints.properties Surely this is causing the tests with default constraints to fail. I see that the classLoader from which the resource is to get loaded is org.eclipse.osgi.internal.baseadaptor.defaultclassloa...@15a4a77 which has a delegate BundleLoader(org.apache.geronimo.framework.geronimo-system_3.0.0.SNAPSHOT) In the case where the tests are passing (before the regression), DefaultConstraints.properties is getting loaded from[BundleClassLoader] org.apache.geronimo.framework.j2ee-security_3.0.0.SNAPSHOT [74] In the TCK, I'm seeing a lot of the same failures where the test was expecting constraint failures and not getting any, so this is probably the same thing. There's at least one other problem with the TCK. A number of tests are getting deploy failures because of errors with the validation.xml. Since these tests actually ARE tests for the invalid XML. this suggests that any parsing errors discovered at deploy time should not be terminal. hmm... I will change the deployment exceptions to log warning messages instead. I have changed the code to log debug messages instead of throwing deployment exceptions. Commited in revision 1022595. This should take care of the TCK tests related to invalid XML. Rick -- Vamsi -- Vamsi -- Vamsi
Re: Bean Validation problems in trunk.
On Wed, Oct 20, 2010 at 10:41 PM, Vamsavardhana Reddy c1vams...@gmail.comwrote: On Thu, Oct 14, 2010 at 9:49 PM, Vamsavardhana Reddy c1vams...@gmail.comwrote: On Thu, Oct 14, 2010 at 8:03 AM, Vamsavardhana Reddy c1vams...@gmail.com wrote: On Wed, Oct 13, 2010 at 11:47 PM, Rick McGuire rick...@gmail.comwrote: The recent changes to the bean validation support appear to be causing failures in both the TCK and the bean validation testsuite. I've tried to do a little problem determination, but I think Vamsi is probably going to need to take a look at this. In the testsuite failures, it looks to me that the validation factory configuration is not getting set up correctly so that not all of the constraints are getting applied in the tests. Many of the failures are just using the default constraint classes. I see that only those constraint classes that are within the same test project are being used in the validation, but the default ones are not. I will take a look at what is happening. As of rev 1005583 (by which the earlier test is reorganized and EJB test is added) the tests are passing. Rev 1005852 is the only other rev that touched plugins\bval, but the change in that rev seems to have not affected the test status. I will investigate further. When I start the server, I see one warning message indicating DefaultConstraints.properties could not be loaded... Forgot to mention that this warning message is logged while loading org.apache.geronimo.configs/remote-deploy-tomcat/3.0-SNAPSHOT/car Starting Geronimo Application Server v3.0-SNAPSHOT [] 42% 10s Starting org.apache.ger...2010-10-20 22:19:07,359 WARN [ConstraintDefaults] cannot find org/apache/bval/jsr303/DefaultConstraints.properties Surely this is causing the tests with default constraints to fail. I see that the classLoader from which the resource is to get loaded is org.eclipse.osgi.internal.baseadaptor.defaultclassloa...@15a4a77 which has a delegate BundleLoader(org.apache.geronimo.framework.geronimo-system_3.0.0.SNAPSHOT) In the case where the tests are passing (before the regression), DefaultConstraints.properties is getting loaded from[BundleClassLoader] org.apache.geronimo.framework.j2ee-security_3.0.0.SNAPSHOT [74] In the TCK, I'm seeing a lot of the same failures where the test was expecting constraint failures and not getting any, so this is probably the same thing. There's at least one other problem with the TCK. A number of tests are getting deploy failures because of errors with the validation.xml. Since these tests actually ARE tests for the invalid XML. this suggests that any parsing errors discovered at deploy time should not be terminal. hmm... I will change the deployment exceptions to log warning messages instead. I have changed the code to log debug messages instead of throwing deployment exceptions. Commited in revision 1022595. This should take care of the TCK tests related to invalid XML. Rick -- Vamsi -- Vamsi -- Vamsi -- Vamsi
Are we getting close to being able to have a 3.0-M2 release?
We've made a lot of progress on Geronimo 3.0 since the M1 release and are starting to get close to passing the Web Profile TCK. I'm thinking it's time to start discussing plans for doing another release update. I'm assuming we'd want to do this shortly after we can be certified as passing the Web Profile TCK. At that time, we'll have a number of SNAPSHOT dependencies we'll need to have releases on. The biggest dependencies that will need to resolved (and which likely can only be handled after getting the TCK to pass cleanly) are openejb, openwebbeans, and xbean. Two other critical components we'd need are a new tomcat external release and a Jetty release (currently using 8.0.0.M2-SNAPSHOT) Other snapshots we're using: - the txmanager and connector (probably can only be released toward the end) - jaspi (probably can be released at any time) - the ejb spec (probably can be released at any time) - the el spec (Just had an update to a number of files, might want to wait a little on this one). - scout (used only for web services, so this will likely be removed). - axiom (ditto) - activemq 5.4-SNAPSHOT (5.4.1 is out...can we use that one? This is something we should investigate now). For the 3.0-M1 release, the big hold up was the long chain of snapshot dependencies that needed to be resolved. The more we can get resolved now, the better the chances of avoiding the same chain-reaction pileup we experienced the last time. Implicit in the above is the M2 release would receive the same sort of pruning that was performed on the M1 release to remove all of the web services elements that really have not had received any attention yet. If not, then we'll need to chase after some additional components like scout. Rick
[BUILD] trunk: Failed for Revision: 1025678
Geronimo Revision: 1025678 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 37 minutes 14 seconds
[INFO] Finished at: Wed Oct 20 15:38:28 EDT 2010
[INFO] Final Memory: 456M/997M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020/logs-1500-tomcat/
[INFO] No sources to compile
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/corba-marshal-client-3.0-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[WARNING] Skipping verification of legal files in artifacts:
[WARNING]
org.apache.geronimo.testsuite:corba-marshal-client:jar:3.0-SNAPSHOT
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/corba-marshal-client-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/corba-marshal-client/3.0-SNAPSHOT/corba-marshal-client-3.0-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo TestSuite :: CORBA TestSuite :: Marshal EAR
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [ear:generate-application-xml {execution:
default-generate-application-xml}]
[INFO] Generating application.xml
[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/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/resources
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] [ear:ear {execution: default-ear}]
[INFO] Copying
artifact[ejb:org.apache.geronimo.testsuite:corba-marshal-ejb:3.0-SNAPSHOT]
to[corba-marshal-ejb-3.0-SNAPSHOT.jar]
[INFO] Copying
artifact[jar:org.apache.geronimo.testsuite:corba-marshal-client:3.0-SNAPSHOT]
to[corba-marshal-client-3.0-SNAPSHOT.jar]
[INFO] Copy ear resources to
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT
[INFO] Could not find manifest file:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/application/META-INF/MANIFEST.MF
- Generating one
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT.ear
[INFO] [geronimo:start-server {execution: start-geronimo}]
[INFO] Using assembly configuration: tomcat
[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/corba-testsuite/corba-marshal/corba-marshal-ear/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/corba-testsuite/corba-marshal/corba-marshal-ear/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Initialized with URL:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector,
environment: {jmx.remote.credentials=[Ljava.lang.String;@ad93f6}
[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
Re: Are we getting close to being able to have a 3.0-M2 release?
Some info for the MyFaces integration, after communicating with MyFaces community, they are now working on some imprvoments for better integration with third-party containers. Except for the improvment, there might be some annotation bug fix ( Seem not covered by TCK). I am not sure whether we would have time for it, guess not, as a new MyFaces release might be required. For Tomcat, I found some improper dependencies between catalina and catalina-ha modules, I will post a message to Tomcat community, but this should not block us release new Tomcat external release, I will pull the latest Tomcat codes soon. Also, we got a bug fix (or improvment) in el-api, I think that it is better to have a new geronimo-el release. thanks. 2010/10/21 Rick McGuire rick...@gmail.com We've made a lot of progress on Geronimo 3.0 since the M1 release and are starting to get close to passing the Web Profile TCK. I'm thinking it's time to start discussing plans for doing another release update. I'm assuming we'd want to do this shortly after we can be certified as passing the Web Profile TCK. At that time, we'll have a number of SNAPSHOT dependencies we'll need to have releases on. The biggest dependencies that will need to resolved (and which likely can only be handled after getting the TCK to pass cleanly) are openejb, openwebbeans, and xbean. Two other critical components we'd need are a new tomcat external release and a Jetty release (currently using 8.0.0.M2-SNAPSHOT) Other snapshots we're using: - the txmanager and connector (probably can only be released toward the end) - jaspi (probably can be released at any time) - the ejb spec (probably can be released at any time) - the el spec (Just had an update to a number of files, might want to wait a little on this one). - scout (used only for web services, so this will likely be removed). - axiom (ditto) - activemq 5.4-SNAPSHOT (5.4.1 is out...can we use that one? This is something we should investigate now). For the 3.0-M1 release, the big hold up was the long chain of snapshot dependencies that needed to be resolved. The more we can get resolved now, the better the chances of avoiding the same chain-reaction pileup we experienced the last time. Implicit in the above is the M2 release would receive the same sort of pruning that was performed on the M1 release to remove all of the web services elements that really have not had received any attention yet. If not, then we'll need to chase after some additional components like scout. Rick -- Ivan
Welcome Janet Hong Fang Han as a new committer
I would like to welcome Janet aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (hanhongfang), so you should start seeing some commits from her soon. -- Ivan
Re: Welcome Janet Hong Fang Han as a new committer
Congrats, Janet~! Jeff On Thu, Oct 21, 2010 at 9:11 AM, Ivan xhh...@gmail.com wrote: I would like to welcome Janet aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (hanhongfang), so you should start seeing some commits from her soon. -- Ivan
Re: Are we getting close to being able to have a 3.0-M2 release?
Is activemq a must-have ? JMS is not a part of web-profile. Openwebbeans is releasing 1.0.0, could we just use it ? On Thu, Oct 21, 2010 at 2:32 AM, Rick McGuire rick...@gmail.com wrote: We've made a lot of progress on Geronimo 3.0 since the M1 release and are starting to get close to passing the Web Profile TCK. I'm thinking it's time to start discussing plans for doing another release update. I'm assuming we'd want to do this shortly after we can be certified as passing the Web Profile TCK. At that time, we'll have a number of SNAPSHOT dependencies we'll need to have releases on. The biggest dependencies that will need to resolved (and which likely can only be handled after getting the TCK to pass cleanly) are openejb, openwebbeans, and xbean. Two other critical components we'd need are a new tomcat external release and a Jetty release (currently using 8.0.0.M2-SNAPSHOT) Other snapshots we're using: - the txmanager and connector (probably can only be released toward the end) - jaspi (probably can be released at any time) - the ejb spec (probably can be released at any time) - the el spec (Just had an update to a number of files, might want to wait a little on this one). - scout (used only for web services, so this will likely be removed). - axiom (ditto) - activemq 5.4-SNAPSHOT (5.4.1 is out...can we use that one? This is something we should investigate now). For the 3.0-M1 release, the big hold up was the long chain of snapshot dependencies that needed to be resolved. The more we can get resolved now, the better the chances of avoiding the same chain-reaction pileup we experienced the last time. Implicit in the above is the M2 release would receive the same sort of pruning that was performed on the M1 release to remove all of the web services elements that really have not had received any attention yet. If not, then we'll need to chase after some additional components like scout. Rick -- Shawn
Re: svn commit: r1025519 - /geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java
Right,I also can't find any code logic error. it's a strange run-time
behavior.
The snippet under (currentPatterns ==null) only get executed once because
(currentPatterns ==null) =false after that. In Eclipse debug session, I
could see currentPatterns's object id the same as that of the first
currentRolePatterns object.
On Wed, Oct 20, 2010 at 8:04 PM, Ivan xhh...@gmail.com wrote:
Hmm, I do not see this scenario exists, currentPattern is never used while
calculating the role based security.
Do we get any cases failed ?
2010/10/20 genspr...@apache.org
Author: genspring
Date: Wed Oct 20 11:55:31 2010
New Revision: 1025519
URL: http://svn.apache.org/viewvc?rev=1025519view=rev
Log:
Somehow, once currentRolePatterns = new HashMapString, URLPattern(); is
executed.currentPatterns will point to the same reference of
currentRolePatterns.
Pull (currentPatterns ==null) out of the loop to avoid the unexpected
logic caused by the problem above.
Modified:
geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java
Modified:
geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java?rev=1025519r1=1025518r2=1025519view=diff
==
---
geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java
(original)
+++
geronimo/server/trunk/plugins/j2ee/geronimo-web/src/main/java/org/apache/geronimo/web/security/SpecSecurityBuilder.java
Wed Oct 20 11:55:31 2010
@@ -108,10 +108,13 @@ public class SpecSecurityBuilder {
currentPatterns = uncheckedPatterns;
}
String transport = securityConstraint.userDataConstraint ==
null ? NONE : securityConstraint.userDataConstraint;
+
+boolean isRolebasedPatten = (currentPatterns == null);
+
for (WebResourceCollectionInfo webResourceCollection :
securityConstraint.webResourceCollections) {
//Calculate HTTP methods list
for (String urlPattern :
webResourceCollection.urlPatterns) {
-if (currentPatterns == null) {
+if (isRolebasedPatten) {
for (String roleName : roleNames) {
MapString, URLPattern currentRolePatterns =
rolesPatterns.get(roleName);
if (currentRolePatterns == null) {
--
Ivan
--
Shawn
Re: Welcome Janet Hong Fang Han as a new committer
Congrats ! On Thu, Oct 21, 2010 at 9:11 AM, Ivan xhh...@gmail.com wrote: I would like to welcome Janet aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (hanhongfang), so you should start seeing some commits from her soon. -- Ivan -- Shawn
[BUILD] trunk: Failed for Revision: 1025806
Geronimo Revision: 1025806 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020/unit-test-reports 1) org.apache.geronimo.modules:geronimo-jetty8-builder:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.components:geronimo-jaspi:jar:tests:1.2-SNAPSHOT [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error transferring file: Server returned HTTP response code: 502 for URL: http://repository.apache.org/snapshots/org/apache/geronimo/components/geronimo-jaspi/1.2-SNAPSHOT/geronimo-jaspi-1.2-20101020.151015-1-tests.jar org.apache.geronimo.components:geronimo-jaspi:jar:1.2-20101020.151015-1 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8-builder:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.components:geronimo-jaspi:jar:tests:1.2-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) 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.artifact.resolver.ArtifactResolutionException: Error transferring file: Server returned HTTP response code: 502 for URL: http://repository.apache.org/snapshots/org/apache/geronimo/components/geronimo-jaspi/1.2-SNAPSHOT/geronimo-jaspi-1.2-20101020.151015-1-tests.jar org.apache.geronimo.components:geronimo-jaspi:jar:1.2-20101020.151015-1 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8-builder:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.components:geronimo-jaspi:jar:tests:1.2-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:233) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90) at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.resolveArtifact(DefaultArtifactResolver.java:456) at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.run
Re: [BUILD] trunk: Failed for Revision: 1025806
Just deployed geronimo-jaspi:jar and geronimo-jaspi:jar:tests to fix this. On Thu, Oct 21, 2010 at 9:47 AM, ga...@apache.org wrote: Geronimo Revision: 1025806 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20101020/unit-test-reports 1) org.apache.geronimo.modules:geronimo-jetty8-builder:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.components:geronimo-jaspi:jar:tests:1.2-SNAPSHOT [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error transferring file: Server returned HTTP response code: 502 for URL: http://repository.apache.org/snapshots/org/apache/geronimo/components/geronimo-jaspi/1.2-SNAPSHOT/geronimo-jaspi-1.2-20101020.151015-1-tests.jar org.apache.geronimo.components:geronimo-jaspi:jar:1.2-20101020.151015-1 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots ), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org ( http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8-builder:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.components:geronimo-jaspi:jar:tests:1.2-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) 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.artifact.resolver.ArtifactResolutionException: Error transferring file: Server returned HTTP response code: 502 for URL: http://repository.apache.org/snapshots/org/apache/geronimo/components/geronimo-jaspi/1.2-SNAPSHOT/geronimo-jaspi-1.2-20101020.151015-1-tests.jar org.apache.geronimo.components:geronimo-jaspi:jar:1.2-20101020.151015-1 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots ), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org ( http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8-builder:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.components:geronimo-jaspi:jar:tests:1.2-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:233) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90) at org.apache.maven.artifact.resolver.DefaultArtifactResolver
Re: Welcome Janet Hong Fang Han as a new committer
Congrats and welcome! 2010/10/21 Ivan xhh...@gmail.com I would like to welcome Janet aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (hanhongfang), so you should start seeing some commits from her soon. -- Ivan -- Lei Wang (Rex) rwonly AT apache.org
Re: Are we getting close to being able to have a 3.0-M2 release?
On Oct 20, 2010, at 6:38 PM, Shawn Jiang wrote: Is activemq a must-have ? JMS is not a part of web-profile. I'd rather ship with amq if it works. It's pretty useful -- I'd say more useful that remote ejbs. Openwebbeans is releasing 1.0.0, could we just use it ? no, we need some bug fixes. david jencks On Thu, Oct 21, 2010 at 2:32 AM, Rick McGuire rick...@gmail.com wrote: We've made a lot of progress on Geronimo 3.0 since the M1 release and are starting to get close to passing the Web Profile TCK. I'm thinking it's time to start discussing plans for doing another release update. I'm assuming we'd want to do this shortly after we can be certified as passing the Web Profile TCK. At that time, we'll have a number of SNAPSHOT dependencies we'll need to have releases on. The biggest dependencies that will need to resolved (and which likely can only be handled after getting the TCK to pass cleanly) are openejb, openwebbeans, and xbean. Two other critical components we'd need are a new tomcat external release and a Jetty release (currently using 8.0.0.M2-SNAPSHOT) Other snapshots we're using: - the txmanager and connector (probably can only be released toward the end) - jaspi (probably can be released at any time) - the ejb spec (probably can be released at any time) - the el spec (Just had an update to a number of files, might want to wait a little on this one). - scout (used only for web services, so this will likely be removed). - axiom (ditto) - activemq 5.4-SNAPSHOT (5.4.1 is out...can we use that one? This is something we should investigate now). For the 3.0-M1 release, the big hold up was the long chain of snapshot dependencies that needed to be resolved. The more we can get resolved now, the better the chances of avoiding the same chain-reaction pileup we experienced the last time. Implicit in the above is the M2 release would receive the same sort of pruning that was performed on the M1 release to remove all of the web services elements that really have not had received any attention yet. If not, then we'll need to chase after some additional components like scout. Rick -- Shawn
Re: Welcome Janet Hong Fang Han as a new committer
Congrats Janet! Great to have you joining the Geronimo project! --kevan On Oct 20, 2010, at 9:11 PM, Ivan wrote: I would like to welcome Janet aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (hanhongfang), so you should start seeing some commits from her soon. -- Ivan
Re: Welcome Janet Hong Fang Han as a new committer
Congrats Janet!! On Thu, Oct 21, 2010 at 6:41 AM, Ivan xhh...@gmail.com wrote: I would like to welcome Janet aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (hanhongfang), so you should start seeing some commits from her soon. -- Ivan -- Vamsi
[BUILD] branches/2.2: Failed for Revision: 1025649
Geronimo Revision: 1025649 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101020/build-1400.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.2/20101020 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 42 minutes 4 seconds [INFO] Finished at: Wed Oct 20 14:45:20 EDT 2010 [INFO] Final Memory: 309M/996M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101020/logs-1400-tomcat/ [INFO] Running TestSuite [INFO] Tests run: 40, Failures: 21, Errors: 0, Skipped: 0, Time elapsed: 214.786 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 73.491 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 69.281 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20101020/logs-1400-jetty/ [INFO] Running TestSuite [INFO] Tests run: 116, Failures: 3, Errors: 0, Skipped: 113, Time elapsed: 16.62 sec FAILURE! [INFO] Running TestSuite [INFO] Tests run: 12, Failures: 6, Errors: 0, Skipped: 0, Time elapsed: 107.028 sec FAILURE! -- [INFO] Running TestSuite [INFO] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 7.786 sec FAILURE! Samples: branches/2.2 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.2/20101020/samples-1400.log Build status: FAILED
Re: Are we getting close to being able to have a 3.0-M2 release?
On Thu, Oct 21, 2010 at 11:24 AM, David Jencks david_jen...@yahoo.comwrote: On Oct 20, 2010, at 6:38 PM, Shawn Jiang wrote: Is activemq a must-have ? JMS is not a part of web-profile. I'd rather ship with amq if it works. It's pretty useful -- I'd say more useful that remote ejbs. I agree it's useful. But amq is not part of current geronimo web-profile server for now. I don't know if we could fully enable it without a new amq release before m2. Openwebbeans is releasing 1.0.0, could we just use it ? no, we need some bug fixes. david jencks On Thu, Oct 21, 2010 at 2:32 AM, Rick McGuire rick...@gmail.com wrote: We've made a lot of progress on Geronimo 3.0 since the M1 release and are starting to get close to passing the Web Profile TCK. I'm thinking it's time to start discussing plans for doing another release update. I'm assuming we'd want to do this shortly after we can be certified as passing the Web Profile TCK. At that time, we'll have a number of SNAPSHOT dependencies we'll need to have releases on. The biggest dependencies that will need to resolved (and which likely can only be handled after getting the TCK to pass cleanly) are openejb, openwebbeans, and xbean. Two other critical components we'd need are a new tomcat external release and a Jetty release (currently using 8.0.0.M2-SNAPSHOT) Other snapshots we're using: - the txmanager and connector (probably can only be released toward the end) - jaspi (probably can be released at any time) - the ejb spec (probably can be released at any time) - the el spec (Just had an update to a number of files, might want to wait a little on this one). - scout (used only for web services, so this will likely be removed). - axiom (ditto) - activemq 5.4-SNAPSHOT (5.4.1 is out...can we use that one? This is something we should investigate now). For the 3.0-M1 release, the big hold up was the long chain of snapshot dependencies that needed to be resolved. The more we can get resolved now, the better the chances of avoiding the same chain-reaction pileup we experienced the last time. Implicit in the above is the M2 release would receive the same sort of pruning that was performed on the M1 release to remove all of the web services elements that really have not had received any attention yet. If not, then we'll need to chase after some additional components like scout. Rick -- Shawn -- Shawn
