[BUILD] trunk: Failed for Revision: 831814

2009-11-02 Thread gawor
Geronimo Revision: 831814 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091102/build-0300.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091102/unit-test-reports
 
Building Geronimo trunk at Revision: 831814
 
java version 1.6.0_10
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode)
 
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
Downloading: 
http://repo.exist.com/maven2/org/apache/geronimo/genesis/genesis-java6-flava/2.0/genesis-java6-flava-2.0.pom
5K downloaded
Downloading: 
http://repo.exist.com/maven2/org/apache/geronimo/genesis/genesis-default-flava/2.0/genesis-default-flava-2.0.pom
17K downloaded
Downloading: 
http://repo.exist.com/maven2/org/apache/geronimo/genesis/genesis/2.0/genesis-2.0.pom
17K downloaded
Downloading: http://repo.exist.com/maven2/org/apache/apache/6/apache-6.pom
12K downloaded
[INFO] snapshot org.apache.felix.karaf:karaf:1.1.0-SNAPSHOT: checking for 
updates from codehaus.snapshots
[INFO] snapshot org.apache.felix.karaf:karaf:1.1.0-SNAPSHOT: checking for 
updates from apache.snapshots
Downloading: 
http://snapshots.repository.codehaus.org/org/apache/felix/karaf/karaf/1.1.0-SNAPSHOT/karaf-1.1.0-SNAPSHOT.pom
Downloading: 
http://repository.apache.org/snapshots/org/apache/felix/karaf/karaf/1.1.0-SNAPSHOT/karaf-1.1.0-SNAPSHOT.pom
42K downloaded
Downloading: 
http://svn.apache.org/repos/asf/servicemix/m2-repo/org/apache/felix/felix-parent/1.2.1/felix-parent-1.2.1.pom
Downloading: 
http://jansi.fusesource.org/repo/release/org/apache/felix/felix-parent/1.2.1/felix-parent-1.2.1.pom
Downloading: 
http://repo.exist.com/maven2/org/apache/felix/felix-parent/1.2.1/felix-parent-1.2.1.pom
13K downloaded
Downloading: 
http://svn.apache.org/repos/asf/servicemix/m2-repo/org/apache/apache/5/apache-5.pom
Downloading: 
http://jansi.fusesource.org/repo/release/org/apache/apache/5/apache-5.pom
Downloading: http://repo.exist.com/maven2/org/apache/apache/5/apache-5.pom
4K downloaded
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] Error building POM (may not be this project's POM).


Project ID: org.apache.geronimo.configs:system-database
POM Location: 
/home/geronimo/geronimo/trunk/plugins/system-database/system-database/pom.xml
Validation Messages:

[0]  'dependencies.dependency.version' is missing for 
org.apache.geronimo.framework:geronimo-service-builder


Reason: Failed to validate POM for project 
org.apache.geronimo.configs:system-database at 
/home/geronimo/geronimo/trunk/plugins/system-database/system-database/pom.xml


[INFO] 
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for 
project org.apache.geronimo.configs:system-database at 
/home/geronimo/geronimo/trunk/plugins/system-database/system-database/pom.xml
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
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.project.InvalidProjectModelException: Failed to 
validate POM for project org.apache.geronimo.configs:system-database at 
/home/geronimo/geronimo/trunk/plugins/system-database/system-database/pom.xml
at 
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1107)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:877)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:505)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534

Re: There's still hope for 2.2...

2009-11-02 Thread frapien

are there any new release plans for 2.2?
3Q2009 is over and needs an update under
http://cwiki.apache.org/GMOxPMGT/geronimo-22-release-status.html
-- 
View this message in context: 
http://old.nabble.com/There%27s-still-hope-for-2.2...-tp25395776s134p26156696.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.



[BUILD] trunk: Failed for Revision: 831898

2009-11-02 Thread gawor
Geronimo Revision: 831898 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091102/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091102/unit-test-reports
 
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@50145014
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva

[jira] Commented: (GERONIMO-4846) form based security for the web application does not work with Jetty WADI clustering.

2009-11-02 Thread Trygve Hardersen (JIRA)

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

Trygve Hardersen commented on GERONIMO-4846:


I'll try to get this tested sometime later this week. Thanks!

 form based security for the web application does not work with Jetty WADI 
 clustering.
 -

 Key: GERONIMO-4846
 URL: https://issues.apache.org/jira/browse/GERONIMO-4846
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Clustering
Affects Versions: 2.2
Reporter: Shawn Jiang

 This is a part of https://issues.apache.org/jira/browse/GERONIMO-4777,  the 
 major issue has been resolved with the patch from  Trygve Hardersen.  
 Opening this JIRA to track the remaining problems.
 
 However it does not work when combined with form based security for the web 
 application. The first problem is that 
 org.eclipse.jetty.security.authentication.SessionCachingAuthenticator$SessionAuthentication
  and org.eclipse.jetty.security.authentication.SessionCachingAuthenticator 
 are not serializable, so they can not be sent across the network. I made 
 these classes serializable, and then login works as long as there is only one 
 member in the cluster (well, not really a cluster...). When there are 
 multiple members in the cluster, login fails because there is no valid 
 constructor for 
 org.eclipse.jetty.security.authentication.SessionCachingAuthenticator$SessionAuthentication.
  I tried to add a default constructor, but it's an inner class, and it seems 
 to me like theAuthenticator and UserIdentity properties are required for it 
 to work so I did not try to extract the class.
 As I said login works as long as there's only one member in the cluster, but 
 logout does not. Calling javax.servlet.http.HttpSession#invalidate() throws 
 an exception, because the curent session can not be found:
 java.lang.AssertionError: Session 
 [org.apache.geronimo.clustering.wadi.wadisessionadap...@7f488ddb] is undefined
 org.codehaus.wadi.replication.manager.ReplicationKeyNotFoundException: Key 
 [ccge2q2w9dz2] does not exist
 I am attaching the patch for the WADIJettyClusteringBuilder 
 (WADIJettyClusteringBuilder.patch) and a sample project JGS (jgs.tar.gz) that 
 demonstrates the security problems I'm experiencing. The 
 web-formlogin-clustering-plugin of the JGS project uses form based security 
 and WADI clustering. The /customer page is protected, and to access it one 
 must login with any username and password, as long as they are the same. Use 
 test/test for instance. To test session invalidation, manually enter the URL 
 /logout.
 It would be very helpful if someone can comment on the usability of WADI 
 clustering in combination with Jetty7. To me it seems like it has not been 
 tested much, and I think going back to Jetty6 again is the best option for 
 us, unless the issues described above can be easily solved.
 Thanks for your help!
 --

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



xbeans and OSGi

2009-11-02 Thread Rick McGuire
I've been wrestling with some build problems involving xbeans and 
bundles since the middle of last week, and I've finally gotten the 
specific error I was working on to go away.  I'm not entirely happy with 
what I needed to do to fix this, so I think this needs a little 
discussion.  First, some specifics on what I've found.


1)  The problem.  This problem was showing up when trying to build the 
system-database plugin.  It was starting the connector-deployer-1_6 
plugin and getting a NullPointerException inside the xmlbeans runtime 
after calling getEnvironment() on the ConnectorDocument class.  This was 
happening because the xmlbeans runtime was unable to locate the type 
information for the environment property of the document.


2)  The cause.  This situation was occurring because the 
ConnectorDocument class uses property types defined in the 
geronimo-system-builder module.  At first, I thought this was due to 
some missing imports for the org.osgi.geronimo.deployment.xbeans.impl 
and org.osgi.geronimo.deployment.javabean.xbeans.impl packages.  I spent 
a couple days trying to get these imports correctly defined, but adding 
these did not clear up the NullPointerException on the getEnvironment() 
call. 

3)  Finally, after poking around in xmlbeans a little, I figured out the 
issue was not the implementation classes, but rather the .xsb files.  
The directories where these are contained also needed to be exported by 
the defining bundles and also imported by the using bundles. 

Item 3 is where the problems come in.  Because of the way xmlbeans 
generates the type information, there are lots of packages that need to 
be exported and imported to make things work.  Importing was fairly 
easy, since the bnd tool allows wildcards.  Importing is another matter 
entirely.  Since the referencing bundles don't contain any code 
references to these packages, the bnd tool is unable to generate this 
directly.  Any since there are a lot of directories involved that have 
very cryptic names, it really doesn't look practical to hand generate 
each of these either.


A solution that did work is to use Require-Bundle to have all of these 
packages get imported by the using bundle at runtime.  I'm not terribly 
happy with having to resort to this, but bnd doesn't have a capability 
of doing the static equivalent of a Require-Bundle when generating the 
manifest.  The combination of export all of those packages and using 
Require-Bundle finally made the NullPointerException go away.


In the course of fixing this, I also added a couple of enhancements to 
the car-maven-plugin to allow the manifest to be augmented by additional 
Import-Package and Require-Bundle information.  This looks like it is 
going to be additional metadata that we'll require in some of these 
dynamic classloading situations.


I'll update the wiki with the workarounds I've found for this problem 
once we're comfortable with the approach needed to fix this.


Rick


[BUILD] trunk: Failed for Revision: 832083

2009-11-02 Thread gawor
Geronimo Revision: 832083 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091102/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091102/unit-test-reports
 

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-cli:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.bundles:commons-cli:jar:1.0_1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=commons-cli -Dversion=1.0_1-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.bundles 
-DartifactId=commons-cli -Dversion=1.0_1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-cli:bundle:3.0-SNAPSHOT
2) org.apache.geronimo.bundles:commons-cli:jar:1.0_1-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-cli:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
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.bundles:commons-cli:jar:1.0_1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=commons-cli -Dversion=1.0_1-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.bundles 
-DartifactId=commons-cli -Dversion=1.0_1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-cli:bundle:3.0-SNAPSHOT
2) org.apache.geronimo.bundles:commons-cli:jar:1.0_1-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-cli:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies

Re: [BUILD] branches/2.2: Failed for Revision: 831574

2009-11-02 Thread David Jencks
This morning I patched some deployers to add dependencies on  
ejbModuleImpl and now the build seems to be completing OK.


would be great to get a tck run, but I may have a release candidate  
before it can complete.


thanks
david jencks

On Nov 1, 2009, at 11:28 PM, David Jencks wrote:

I committed a partial fix in rev 831811 which gets ejbModuleImpl to  
initialize all the ejbDeployments as it starts.  I think the TSSLink  
and WSLink gbeans will also need dependencies on ejbModule to make  
sure they start after this initialization happens.  I'd appreciate a  
review of the committed change.


thanks
david jencks

On Nov 1, 2009, at 9:01 AM, David Jencks wrote:

I think that the dependency direction changes for ejb singletons  
have broken corba and ejb web services.  Looking into it help  
would be welcome.


For the corba problems, so far I've discovered that we really need  
the deployment info in EjbDeployment initialized before the  
TSSLinkGBean starts.  However, even having a dependency on  
EjbModuleImpl is not sufficient for the EjbDeployment to be  
usable.  Is there some way that EjbModuleImpl could run through the  
EjbDeployment objects and initialize them?


thanks
david jencks

On Oct 31, 2009, at 1:18 PM, ga...@apache.org wrote:


Geronimo Revision: 831574 built with tests included

See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091031/build-1400.log

Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091031
[INFO] BUILD SUCCESSFUL
[INFO]  


[INFO] Total time: 40 minutes 40 seconds
[INFO] Finished at: Sat Oct 31 14:45:34 EDT 2009
[INFO] Final Memory: 322M/1015M
[INFO]  



TESTSUITE RESULTS (Failures only)
=

Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20091031/logs-1400-tomcat/


[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:50.797
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml  
to /home/geronimo/.m2/repository/org/apache/geronimo/testsuite/ 
testsuite/testing/testsuite-testing.pom

[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]  
---

[INFO]
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS  
(0:01:22.391)

[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS  
(0:00:39.683)

[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS  
(0:00:45.972)

[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS  
(0:00:24.215)

[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS  
(0:06:36.063)

[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS  
(0:01:39.190)

[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS  
(0:02:03.305)

[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   FAILURE  
(0:00:50.371) Java returned: 1

[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  FAILURE  
(0:00:43.377) Java returned: 1

[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   FAILURE  
(0:00:43.091) Java returned: 1

[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS  
(0:00:38.182)

[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS  
(0:00:35.599)

[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS  
(0:00:39.983)

[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS  
(0:01:07.558)

[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS  
(0:01:20.983)

[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS  
(0:01:00.172)

[INFO] enterprise-testsuite/sec-client-tests  RUNNING
[INFO] enterprise-testsuite/sec-client-tests  SUCCESS  
(0:00:34.514)

[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests  

Geronimo Blog

2009-11-02 Thread Kevan Miller

All,
A new Geronimo community blog has been created at 
http://blogs.apache.org/geronimo/

If you'd like the ability to post to the blog, reply to this email. At  
the moment, access is limited to Geronimo committers. If this policy  
changes, I'll let everyone know...


--kevan


Re: Geronimo Blog

2009-11-02 Thread Donald Woods

Thanks for setting it up!

ID:  dwoods
Email:  dwoods at apache.org


-Donald

Kevan Miller wrote:

All,
A new Geronimo community blog has been created at 
http://blogs.apache.org/geronimo/


If you'd like the ability to post to the blog, reply to this email. At 
the moment, access is limited to Geronimo committers. If this policy 
changes, I'll let everyone know...


--kevan



Re: xbeans and OSGi

2009-11-02 Thread Ivan
Thanks, Rick, I got this issue too while trying to remove the classloader
plugins :-)
I guess that only those *-builder will need to import those xmlbeans
gernated classes, shall we use a tool to scan and generate the whole package
list, then add them to those pom files.
I remembered that long ago, there is a discussion about removing xmlbeans
from Geronimo, and use jaxb to parse and generate the plan file, Maybe we
could do it in 3.0.

2009/11/3 Rick McGuire rick...@gmail.com

 I've been wrestling with some build problems involving xbeans and bundles
 since the middle of last week, and I've finally gotten the specific error I
 was working on to go away.  I'm not entirely happy with what I needed to do
 to fix this, so I think this needs a little discussion.  First, some
 specifics on what I've found.

 1)  The problem.  This problem was showing up when trying to build the
 system-database plugin.  It was starting the connector-deployer-1_6 plugin
 and getting a NullPointerException inside the xmlbeans runtime after calling
 getEnvironment() on the ConnectorDocument class.  This was happening because
 the xmlbeans runtime was unable to locate the type information for the
 environment property of the document.

 2)  The cause.  This situation was occurring because the ConnectorDocument
 class uses property types defined in the geronimo-system-builder module.  At
 first, I thought this was due to some missing imports for the
 org.osgi.geronimo.deployment.xbeans.impl and
 org.osgi.geronimo.deployment.javabean.xbeans.impl packages.  I spent a
 couple days trying to get these imports correctly defined, but adding these
 did not clear up the NullPointerException on the getEnvironment() call.
 3)  Finally, after poking around in xmlbeans a little, I figured out the
 issue was not the implementation classes, but rather the .xsb files.  The
 directories where these are contained also needed to be exported by the
 defining bundles and also imported by the using bundles.
 Item 3 is where the problems come in.  Because of the way xmlbeans
 generates the type information, there are lots of packages that need to be
 exported and imported to make things work.  Importing was fairly easy, since
 the bnd tool allows wildcards.  Importing is another matter entirely.  Since
 the referencing bundles don't contain any code references to these packages,
 the bnd tool is unable to generate this directly.  Any since there are a lot
 of directories involved that have very cryptic names, it really doesn't look
 practical to hand generate each of these either.

 A solution that did work is to use Require-Bundle to have all of these
 packages get imported by the using bundle at runtime.  I'm not terribly
 happy with having to resort to this, but bnd doesn't have a capability of
 doing the static equivalent of a Require-Bundle when generating the
 manifest.  The combination of export all of those packages and using
 Require-Bundle finally made the NullPointerException go away.

 In the course of fixing this, I also added a couple of enhancements to the
 car-maven-plugin to allow the manifest to be augmented by additional
 Import-Package and Require-Bundle information.  This looks like it is going
 to be additional metadata that we'll require in some of these dynamic
 classloading situations.

 I'll update the wiki with the workarounds I've found for this problem once
 we're comfortable with the approach needed to fix this.

 Rick




-- 
Ivan


[jira] Updated: (GERONIMO-4801) it says JACC manager gbean already present when i deploy PlantsByWebSphere sample

2009-11-02 Thread Ivan (JIRA)

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

Ivan updated GERONIMO-4801:
---

Attachment: (was: Geronimo-4801.patch)

 it says JACC manager gbean already present when i deploy PlantsByWebSphere  
 sample
 

 Key: GERONIMO-4801
 URL: https://issues.apache.org/jira/browse/GERONIMO-4801
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: security
Affects Versions: 2.2
 Environment: windows xp sp2(x86)
 jdk6
Reporter: Bin He
Assignee: Ivan
 Attachments: PlantsByWebSphere.7z, sample-datasource.7z


 1、start server 
 2、deploy  sample-datasource sample
 3、deploy  PlantsByWebSphere sample   but it   says:(but this sample can run 
 well)
 2009-08-19 10:28:52,370 ERROR [EjbModuleBuilder] 
 GeronimoSecurityBuilderImpl.addGBeans() failed: JACC manager gbean already 
 present
 org.apache.geronimo.common.DeploymentException: JACC manager gbean already 
 present
   at 
 org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:224)
   at 
 org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.addGBeans(GeronimoSecurityBuilderImpl.java:150)
   at 
 org.apache.geronimo.openejb.deployment.EjbModuleBuilder.addGBeans(EjbModuleBuilder.java:825)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:652)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:257)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:136)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
   at java.lang.reflect.Method.invoke(Method.java:599)
   at 
 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
   at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
   at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
   at 
 org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
   at 
 org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
   at java.lang.Thread.run(Thread.java:735)
 Caused by: org.apache.geronimo.kernel.GBeanAlreadyExistsException: 
 com.ibm.wasce.samples/pbw/2.1.1.2/car?J2EEApplication=com.ibm.wasce.samples/pbw/2.1.1.2/car,j2eeType=JACCManager,name=JACCManager
   at 
 org.apache.geronimo.kernel.config.Configuration.addGBean(Configuration.java:626)
   at 
 org.apache.geronimo.deployment.DeploymentContext.addGBean(DeploymentContext.java:186)
   at 
 org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:222)
   ... 16 more

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

2009-11-02 Thread gawor
Geronimo Revision: 832261 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091102/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20091102/unit-test-reports
 

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-cli:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.geronimo.bundles:commons-cli:jar:1.0_1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=commons-cli -Dversion=1.0_1-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.bundles 
-DartifactId=commons-cli -Dversion=1.0_1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-cli:bundle:3.0-SNAPSHOT
2) org.apache.geronimo.bundles:commons-cli:jar:1.0_1-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-cli:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
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.bundles:commons-cli:jar:1.0_1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.geronimo.bundles 
-DartifactId=commons-cli -Dversion=1.0_1-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.bundles 
-DartifactId=commons-cli -Dversion=1.0_1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.framework:geronimo-cli:bundle:3.0-SNAPSHOT
2) org.apache.geronimo.bundles:commons-cli:jar:1.0_1-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.framework:geronimo-cli:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies

[jira] Commented: (GERONIMO-4801) it says JACC manager gbean already present when i deploy PlantsByWebSphere sample

2009-11-02 Thread Ivan (JIRA)

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

Ivan commented on GERONIMO-4801:


I think we need to fix this in Geronimo 2.2, it may not cause an issue, but not 
a good user experience.
As said in the last comment, IMO, we could just hold the Exception, do not 
throw it. 


 it says JACC manager gbean already present when i deploy PlantsByWebSphere  
 sample
 

 Key: GERONIMO-4801
 URL: https://issues.apache.org/jira/browse/GERONIMO-4801
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: security
Affects Versions: 2.2
 Environment: windows xp sp2(x86)
 jdk6
Reporter: Bin He
Assignee: Ivan
 Attachments: PlantsByWebSphere.7z, sample-datasource.7z


 1、start server 
 2、deploy  sample-datasource sample
 3、deploy  PlantsByWebSphere sample   but it   says:(but this sample can run 
 well)
 2009-08-19 10:28:52,370 ERROR [EjbModuleBuilder] 
 GeronimoSecurityBuilderImpl.addGBeans() failed: JACC manager gbean already 
 present
 org.apache.geronimo.common.DeploymentException: JACC manager gbean already 
 present
   at 
 org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:224)
   at 
 org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.addGBeans(GeronimoSecurityBuilderImpl.java:150)
   at 
 org.apache.geronimo.openejb.deployment.EjbModuleBuilder.addGBeans(EjbModuleBuilder.java:825)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:652)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:257)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:136)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
   at java.lang.reflect.Method.invoke(Method.java:599)
   at 
 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
   at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850)
   at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237)
   at 
 org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
   at 
 org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
   at java.lang.Thread.run(Thread.java:735)
 Caused by: org.apache.geronimo.kernel.GBeanAlreadyExistsException: 
 com.ibm.wasce.samples/pbw/2.1.1.2/car?J2EEApplication=com.ibm.wasce.samples/pbw/2.1.1.2/car,j2eeType=JACCManager,name=JACCManager
   at 
 org.apache.geronimo.kernel.config.Configuration.addGBean(Configuration.java:626)
   at 
 org.apache.geronimo.deployment.DeploymentContext.addGBean(DeploymentContext.java:186)
   at 
 org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:222)
   ... 16 more

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