Re: servicemix.org forwards to the wrong site?
Hiram, do you know where can we change this redirection from servicemix.org? On 11/5/07, Guillaume Nodet [EMAIL PROTECTED] wrote: Yeah, and the incubator site should redirect to servicemix.apache.org I just need to find where to change that ... On 11/5/07, Kristian Köhler [EMAIL PROTECTED] wrote: Hi if you go to service.org you will be forwarded to http://incubator.apache.org/servicemix/home.html shouldn't this be http://servicemix.apache.org/home.html Kristian -- http://gaswerk.sourceforge.net -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[BUILD] 2.1: Failed for Revision: 591907
OpenEJB trunk at 591897
Geronimo Revision: 591907 built with tests included
See the full build-0300.log file at
http://people.apache.org/~prasad/binaries/trunk/20071105/build-0300.log
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/resources/META-INF/plan.xml
[INFO] [car:prepare-metadata]
[INFO] [car:package]
[INFO] Packaging module configuration:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/resources/META-INF/plan.xml
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] Building jar:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/axis-2.1-SNAPSHOT.car
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: axis-2.1-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing
/home/prasad/geronimo/trunk/plugins/axis/axis/target/axis-2.1-SNAPSHOT.car to
/home/prasad/.m2/repository/org/apache/geronimo/configs/axis/2.1-SNAPSHOT/axis-2.1-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO]
[INFO] Building Geronimo Modules :: Webservices :: Builder
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.073 seconds
Time to generate code: 0.106 seconds
Time to compile code: 3.104 seconds
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes/META-INF
[INFO] Copying 2 files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes/META-INF
[INFO] [buildsupport:copy-xmlbeans-schemas {execution: default}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/clover/classes
[INFO] Copying 96 files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/clover/classes
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 6 source files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 1 source file to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.webservices.builder.ParsingTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.448 sec
Results :
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/geronimo-webservices-builder-2.1-SNAPSHOT.jar
to
/home/prasad/.m2/repository/org/apache/geronimo/modules/geronimo-webservices-builder/2.1-SNAPSHOT/geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Modules :: OpenEJB :: Builder
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.078 seconds
Time to generate code: 0.063 seconds
Time to compile code: 2.472 seconds
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/openejb/geronimo-openejb-builder/target/classes
[BUILD] 2.1: Failed for Revision: 591999
OpenEJB trunk at 591982
Geronimo Revision: 591999 built with tests included
See the full build-0900.log file at
http://people.apache.org/~prasad/binaries/trunk/20071105/build-0900.log
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/resources/META-INF/plan.xml
[INFO] [car:prepare-metadata]
[INFO] [car:package]
[INFO] Packaging module configuration:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/resources/META-INF/plan.xml
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] Building jar:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/axis-2.1-SNAPSHOT.car
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: axis-2.1-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing
/home/prasad/geronimo/trunk/plugins/axis/axis/target/axis-2.1-SNAPSHOT.car to
/home/prasad/.m2/repository/org/apache/geronimo/configs/axis/2.1-SNAPSHOT/axis-2.1-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO]
[INFO] Building Geronimo Modules :: Webservices :: Builder
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.08 seconds
Time to generate code: 0.152 seconds
Time to compile code: 3.445 seconds
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes/META-INF
[INFO] Copying 2 files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes/META-INF
[INFO] [buildsupport:copy-xmlbeans-schemas {execution: default}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/clover/classes
[INFO] Copying 96 files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/clover/classes
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 6 source files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 1 source file to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.webservices.builder.ParsingTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.449 sec
Results :
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/geronimo-webservices-builder-2.1-SNAPSHOT.jar
to
/home/prasad/.m2/repository/org/apache/geronimo/modules/geronimo-webservices-builder/2.1-SNAPSHOT/geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Modules :: OpenEJB :: Builder
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.084 seconds
Time to generate code: 0.056 seconds
Time to compile code: 2.567 seconds
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/openejb/geronimo-openejb-builder/target/classes
Re: [VOTE] Release J2G 1.0.0 RC1
+1 Lin On Nov 2, 2007 3:40 PM, Donald Woods [EMAIL PROTECTED] wrote: The J2G 1.0.0 RC1 build is ready for a vote, now that the maven-plugins-1.0 dependencies have been released (should appear on the mirror repos in the next 24 hours.) A 72 hour vote is being called for the following: https://svn.apache.org/repos/asf/geronimo/devtools/j2g/branches/1.0.0 Revision 591322 Binaries can be downloaded from: http://people.apache.org/~dwoods/releases/j2g-1.0.0/ j2g-eclipse-plugin-1.0.0-RC1-deployable.zip - artifacts to extract onto a Eclipse 3.3 installation j2g-eclipse-plugin-1.0.0-RC1-updatesite.zip - artifacts to publish to the Geronimo Eclipse update site when released j2g-eclipse-plugin-repo-1.0.0-RC1.tar.gz - captured build repo Docs are located in the Wiki at - http://cwiki.apache.org/GMOxDOC20/j2g-migration-tool.html http://cwiki.apache.org/GMOxDOC11/j2g-migration-tool.html The source code will be moved to the following location in svn after the release has been approved: https://svn.apache.org/repos/asf/geronimo/devtools/j2g/tags/1.0.0 Please record your vote by 5PM EDT Monday, Nov. 5, 2007. [ ] +1 - I approve of the release [ ] 0 - I neither approve or disapprove of the release [ ] -1 - I disagree with the release because of - _ Thanks, Donald
Re: [DISCUSS/FEEDBACK] Usability improvements to Geronimo
On 11/2/07, Prasad Kashyap [EMAIL PROTECTED] wrote: On 11/2/07, Joe Bohn [EMAIL PROTECTED] wrote: Prasad Kashyap wrote: As we get close to releasing Geronimo 2.1 and look beyond, I'd like to discuss a few usability improvements we can do to G. I am cross-posting this to the user-list so that we can get a direct feedback from our dear users. 1. Dynamic status messages. Some operations may take a certain amount of time which could make the administrator uneasy as he waits. On a local machine, he has the luxury of tailing the geronimo.log or seeing the startup terminal. On a remote machine, he is almost flying blind in the absence of any dynamically updating status messages. It would be nice if we had another portlet at the bottom that showed status of the operation being performed. This is really useful for long running operations. Can you be more specific here? What operations and how does a message make things any more dynamic? Is this a web console only concern or is it also a command line concern? Yes. Let me give you an example. Recently I was deploying a configuration. For a while the wheels turned and then I received an operation successful message. However, the deployment had spewn a boatload of stack traces to the geronimo.log file. In another example, the Websphere App Server shows informational messages as an app is being deployed. That is quite reassuring to an administrator. For now, this is a console-only concern. If we really begin to include multiple portlets on pages then it might get difficult to associate responses with porlets/actions that initiated them. It might be more beneficial to provide some interactive feedback (dojo?) within the portlet. 2. Geronimo Workbench. With the addition of features like Plan Creator and Create Plugin, the Admin Console has slowly begun to tread into the domain of tooling. Now we are introducing features for monitoring the server. It's debatable whether such features should even exist in the console. Purists might want the console to be solely for configuration of the server. But given the fact, that they are already there, we should consider creating tabs at the top or sectional categories in the navigation menu. Since we have a navigation tree which does not collapse, we have already crossed a point where we have to scroll down to see all the links. This is a usability no-no. It's time to transform the Console to a Workbench as more Tooling and Monitoring features find their way in. I agree that the plan creators are more in the domain of tooling and perhaps should not be part of the console. I think of the web console as an Administration Console rather than just a configuration console so I think monitoring makes perfect sense to be included. That aside, I think it makes sense to make the navigation tree collapse. I'd add tabs as a last resort because this is not always intuitive to the user. Along with this I think it would be nice if we could enable the navigation and display area to scroll independently. Initially I too was of the same opinion thinking that wizards like Plan Creator should be part of Devtools like Eclipse-Plugin. However when I posted the idea to user@ list, I received a feedback saying: A template system that incorporated creation of the container specific configuration based on the web.xml and ejb-jar.xml would be a valuable tool within the server administration tool set. I would expect a tool like this to be available within the management console in direct proximity to the deploy application tool! Setting deployment specific environment values falls within this scope as well. Please see http://www.mail-archive.com/[EMAIL PROTECTED]/msg06409.html There were also concerns about using Eclipse plug-in just for the sake of deploying apps into Geronimo saying ...many of us don't use Eclipse and don't want to be forced into it. Please see http://www.mail-archive.com/[EMAIL PROTECTED]/msg06412.html All this lead me thinking in the direction of adding a new portlet to the Admin Console. I also later saw that existing Portlets in Admin Console like Database Pools, JMS Resources, Security Realms etc are nothing but wizards to generate Geronimo deployment plans. So I thought a Plan Creator wizard would be a logical continuation of those existing wizards. And yes it's definitely a usability no-no for having to scroll down to see all the links. +1 for collapsible navigation sections and/or scrollable navigation frames. Sure. Collapsible navigation sections and/or scrollable navigation frame are great improvements. Also, I wonder if plugin creators also fall under the under the domain of tooling along with plan creators. 3. Plugin Creator Enhancements: Our current plugin create feature in the console is limited to exporting an already deployed configuration. It does not
Re: [DISCUSS] 2.1 Release
On 11/1/07, Kevan Miller [EMAIL PROTECTED] wrote: I think it's time to start discussing the particulars of a 2.1 release. There's been a lot of advancements made in our plugin infrastructure. There's also been the pluggable console enhancements. It would be good to get a release out, with these capabilities. They provide a more solid platform for future enhancements, I think. There's also GShell and new monitoring capabilities. I'm probably missing a few other new functions. GERONIMO-3254 Admin Console Wizard to auto generate geronimo-web.xml is almost complete and I can wrap up the remaining work-items within a week or so. And if I get a week/two more I can also complete GERONIMO-3432 Admin Console Wizard to auto generate openejb-jar.xml Finally, IIUC, 2.1 would be able to support a Terracotta plugin. I'd also be very interested to hear what WADI capabilities that could be exposed. I'm willing to bang the release manager drum. I see that Joe has already started tugging on the TCK chain What do others think? How close are we to a 2.1 release? What additional capabilities and bug fixes are needed? Can we wrap up development activities in the next week or two? --kevan -- Shiva
Re: [VOTE] Release J2G 1.0.0 RC1
Thanks Erik. I just corrected this typo in rev 592043. Lin On Nov 4, 2007 4:49 PM, Erik B. Craig [EMAIL PROTECTED] wrote: Donald, The deployable and repo look good... however I found a small potential issue in j2g-eclipse-plugin-1.0.0-RC1-updatesite.zip... Within plugins/org.apache.geronimo.devtools.j2g.properties_1.0.0.jar, I believe the directory org.apache.geronimo.devtools.j2g.sources.dependenc should be org.apache.geronimo.devtools.j2g.sources.dependence, as the latter is how it is still named when looking through j2g-eclipse-plugin-1.0.0-RC1-deployable.zip. -Erik Donald Woods wrote: The J2G 1.0.0 RC1 build is ready for a vote, now that the maven-plugins-1.0 dependencies have been released (should appear on the mirror repos in the next 24 hours.) A 72 hour vote is being called for the following: https://svn.apache.org/repos/asf/geronimo/devtools/j2g/branches/1.0.0 Revision 591322 Binaries can be downloaded from: http://people.apache.org/~dwoods/releases/j2g-1.0.0/ j2g-eclipse-plugin-1.0.0-RC1-deployable.zip - artifacts to extract onto a Eclipse 3.3 installation j2g-eclipse-plugin-1.0.0-RC1-updatesite.zip - artifacts to publish to the Geronimo Eclipse update site when released j2g-eclipse-plugin-repo-1.0.0-RC1.tar.gz - captured build repo Docs are located in the Wiki at - http://cwiki.apache.org/GMOxDOC20/j2g-migration-tool.html http://cwiki.apache.org/GMOxDOC11/j2g-migration-tool.html The source code will be moved to the following location in svn after the release has been approved: https://svn.apache.org/repos/asf/geronimo/devtools/j2g/tags/1.0.0 Please record your vote by 5PM EDT Monday, Nov. 5, 2007. [ ] +1 - I approve of the release [ ] 0 - I neither approve or disapprove of the release [ ] -1 - I disagree with the release because of - _ Thanks, Donald
Re: [DISCUSS] 2.1 Release
Agreed, we seem to have enough new stuff to call for a release. Here is a list trying to consolidate these new functions/improvements - GShell - Console enhancements (dep plan generation, grouping/collapsing?) - Monitoring - Plugin infrastructure - Pluggable console - Security - Configuration (config.xml, config-subst, etc) - Deployment plans - Tooling - ...? We will also need a whole new set of documentation to cover these in GMOxDOC21. Anybody in desperate need for contributing docs for these features? ;-) it will be very much appreciated. Cheers! Hernan Kevan Miller wrote: I think it's time to start discussing the particulars of a 2.1 release. There's been a lot of advancements made in our plugin infrastructure. There's also been the pluggable console enhancements. It would be good to get a release out, with these capabilities. They provide a more solid platform for future enhancements, I think. There's also GShell and new monitoring capabilities. I'm probably missing a few other new functions. Finally, IIUC, 2.1 would be able to support a Terracotta plugin. I'd also be very interested to hear what WADI capabilities that could be exposed. I'm willing to bang the release manager drum. I see that Joe has already started tugging on the TCK chain What do others think? How close are we to a 2.1 release? What additional capabilities and bug fixes are needed? Can we wrap up development activities in the next week or two? --kevan
Security for dynamic content apps -- gettogether at ApacheCon?
I've worked a bit on integrating Roller and Jetspeed2 into Geronimo and one thing that quickly becomes clear is that the authorization security requirements of these dynamic content applications are almost completely unrelated to the javaee security specifications. One small possible overlap is that the JACC spec supplies the possibility of pluggable policies for authorization evaluation. I wondered if people would be interested in getting together to discuss how app servers such as geronimo and security products such as TripleSec could support these non-javaee security requirements and how much commonality there might be across different types of application. I'll be at ApacheCon all week and would be happy to talk to everyone individually or in an informal meeting. Some of the things I've been wondering about are: - permission definition - user administration: how are users added and removed or have their permissions changed. - resource administration: how are resources such as blogs, portal pages, or portlets added or removed or have their user access changed - specification of default policy for new users and new resources: e.g. when a new user signs up what can they do? thanks! david jencks
Re: Security for dynamic content apps -- gettogether at ApacheCon?
Unfortunately I'm not going to be going to ApacheCon's in the US but to the EU ones from now on. However I would love to either get a summary or partake in the discussion if someone can ping me from IRC or via skype. This is something I think will benefit us all. Thanks David for driving these talks. Alex On 11/5/07, David Jencks [EMAIL PROTECTED] wrote: I've worked a bit on integrating Roller and Jetspeed2 into Geronimo and one thing that quickly becomes clear is that the authorization security requirements of these dynamic content applications are almost completely unrelated to the javaee security specifications. One small possible overlap is that the JACC spec supplies the possibility of pluggable policies for authorization evaluation. I wondered if people would be interested in getting together to discuss how app servers such as geronimo and security products such as TripleSec could support these non-javaee security requirements and how much commonality there might be across different types of application. I'll be at ApacheCon all week and would be happy to talk to everyone individually or in an informal meeting. Some of the things I've been wondering about are: - permission definition - user administration: how are users added and removed or have their permissions changed. - resource administration: how are resources such as blogs, portal pages, or portlets added or removed or have their user access changed - specification of default policy for new users and new resources: e.g. when a new user signs up what can they do? thanks! david jencks
[BUILD] 2.1: Failed for Revision: 592134
OpenEJB trunk at 592120
Geronimo Revision: 592134 built with tests included
See the full build-1500.log file at
http://people.apache.org/~prasad/binaries/trunk/20071105/build-1500.log
[INFO] [car:package]
Downloading: http://download.java.net/maven/1//axis/poms/axis-saaj-1.4.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//axis/axis-saaj/1.4/axis-saaj-1.4.pom
Downloading: http://repo1.maven.org/maven2/axis/axis-saaj/1.4/axis-saaj-1.4.pom
[INFO] Packaging module configuration:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/resources/META-INF/plan.xml
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] Building jar:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/axis-2.1-SNAPSHOT.car
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: axis-2.1-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing
/home/prasad/geronimo/trunk/plugins/axis/axis/target/axis-2.1-SNAPSHOT.car to
/home/prasad/.m2/repository/org/apache/geronimo/configs/axis/2.1-SNAPSHOT/axis-2.1-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO]
[INFO] Building Geronimo Modules :: Webservices :: Builder
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.083 seconds
Time to generate code: 0.103 seconds
Time to compile code: 3.406 seconds
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes/META-INF
[INFO] Copying 2 files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes/META-INF
[INFO] [buildsupport:copy-xmlbeans-schemas {execution: default}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/clover/classes
[INFO] Copying 96 files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/clover/classes
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 6 source files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 1 source file to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.webservices.builder.ParsingTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.416 sec
Results :
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/geronimo-webservices-builder-2.1-SNAPSHOT.jar
to
/home/prasad/.m2/repository/org/apache/geronimo/modules/geronimo-webservices-builder/2.1-SNAPSHOT/geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Modules :: OpenEJB :: Builder
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.087 seconds
Time to generate code: 0.059 seconds
Time to compile code: 2.839 seconds
[INFO] [tools:copy-legal-files {execution: install-legal-files
SM-580
I would like to take a crack at SM-580. The patch attached seems to apply to the HttpEndpoint. I would like to do make the fix for HttpProviderEndpoint. It seems easy enough: Add property to endpoint Set property to marshaller in endpoint init Have the marshaller look up property (same as contentType/locationUri) prior to formatting http request Is that about right? My only issue with this is figuring out what to do if the contentType does not evaluate to post, should the existence of a post parameter override content type or an exception raised? Thanks -- View this message in context: http://www.nabble.com/SM-580-tf4754351s12049.html#a13595419 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Tomcat GBean names for valves
Would anybody have a strong objection if I renamed the GBeans for the Tomcat valves from FirstValve and SecondValve to reflect the function of the valves themselves? FirstValve -- AccessLogValve SecondValve -- SingleSignOnValve Joe
Re: Tomcat GBean names for valves
+1 go for it. The first valve/second valve came from it being an example due to the chain...I guess it just kinda stuck ;-) Jeff Joe Bohn wrote: Would anybody have a strong objection if I renamed the GBeans for the Tomcat valves from FirstValve and SecondValve to reflect the function of the valves themselves? FirstValve -- AccessLogValve SecondValve -- SingleSignOnValve Joe
Re: Tomcat GBean names for valves
+1, this will help users wishing to customize their valve chain. Best wishes, Paul On Nov 5, 2007, at 4:19 PM, Joe Bohn wrote: Would anybody have a strong objection if I renamed the GBeans for the Tomcat valves from FirstValve and SecondValve to reflect the function of the valves themselves? FirstValve -- AccessLogValve SecondValve -- SingleSignOnValve Joe
Re: problems with installing plugin
You can make the online deployer work with this patch to framework/ config/jsr88-deploymentfactory/pom.xml: Index: pom.xml === --- pom.xml (revision 591736) +++ pom.xml (working copy) @@ -70,6 +70,27 @@ artifactIdcommons-jexl/artifactId /dependency +!-- used by plugin installer -- +dependency +groupIdjavax.xml.bind/groupId +artifactIdjaxb-api/artifactId +/dependency +dependency +groupIdcom.sun.xml.bind/groupId +artifactIdjaxb-impl/artifactId +/dependency +dependency +groupIdorg.apache.geronimo.specs/groupId +artifactIdgeronimo-stax-api_1.0_spec/artifactId +/dependency +dependency +groupIdwoodstox/groupId +artifactIdwstx-asl/artifactId +/dependency +dependency +groupIdorg.apache.geronimo.specs/groupId +artifactIdgeronimo-activation_1.1_spec/artifactId +/dependency /dependencies build however the offline deployer still doesn't work. I think there's something else wrong but I haven't figured out what. It will probably be tomorrow before I get a good handle on what to do. I've gotten rather confused about how the various deployer/jsr88 configs fit together and what is the actual bootstrap config for many of these servers. If I'm really lucky I'll be able to document some of this. thanks david jencks On Nov 4, 2007, at 6:11 PM, Viet Nguyen wrote: I tried to install the AMQ plugin from the commandline and this is what I got: [EMAIL PROTECTED]:~/g/trunk-clean/target/geronimo-jetty6- javaee5-2.1-SNAPSHOT/bin$ java -jar ./deployer.jar -u system -p manager install-plugin /home/vhnguy2/Desktop/activemq.car 21:07:45,459 WARN [ConfigurationUtil] Could not load gbean org.apache.geronimo.configs/jsr88-deploymentfactory/2.1-SNAPSHOT/ car?ServiceModule=org.apache.geronimo.configs/jsr88- deploymentfactory/2.1-SNAPSHOT/ car,j2eeType=AttributeStore,name=AttributeManager java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamException at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2395) at java.lang.Class.getMethod0(Class.java:2642) at java.lang.Class.getMethod(Class.java:1579) at org.apache.geronimo.gbean.runtime.GBeanAttribute.init (GBeanAttribute.java:237) at org.apache.geronimo.gbean.runtime.GBeanInstance.init (GBeanInstance.java:245) at org.apache.geronimo.kernel.basic.BasicKernel.loadGBean (BasicKernel.java:354) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguration GBeans(ConfigurationUtil.java:433) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start (KernelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConf iguration(SimpleConfigurationManager.java:530) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConf iguration(SimpleConfigurationManager.java:511) at org.apache.geronimo.kernel.config.SimpleConfigurationManager$ $FastClassByCGLIB$$ce77a924.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java:830) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$ $EnhancerByCGLIB$$953213f.startConfiguration(generated) at org.apache.geronimo.kernel.util.MainBootstrapper.loadPersistentConfigu rations(MainBootstrapper.java:56) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.getMain( MainConfigurationBootstrapper.java:58) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main (MainConfigurationBootstrapper.java:38) at org.apache.geronimo.cli.AbstractCLI.executeMain (AbstractCLI.java:67) at org.apache.geronimo.cli.deployer.DeployerCLI.main (DeployerCLI.java:31) Exception in thread main java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamException at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2395) at java.lang.Class.getMethod0(Class.java:2642) at java.lang.Class.getMethod(Class.java:1579)
ServiceMix Client Standalone Jar
Hello, Is there a standalone ServiceMix Client jar that I can use to make calls to ServiceMix from a Tomcat servlet? I was able to run the v3.2 ServiceMix Client JUnit test case to talk to our our services, but it seems like I am including a lot of jars which may be causing us some issues. Any help is appreciated. Thanks, Gordon Dickens
Re: [DISCUSS] 2.1 Release
Gianny, Since there are multiple clustering implementations going on at the same time, could you please keep us aprised of what you are doing so we don't clash? Thanks, Jeff Gianny Damour wrote: Hi, I resumed this week-end some work on clustered deployment. I think this will be completed in about 2-3 weeks. This will allow distribute, uninstall, start, stop, et cetera of configurations to a cluster as a single logic operation. I am keen to get this change in for 2.1, if it does not delay 2.1. Thanks, Gianny On 02/11/2007, at 4:00 AM, Kevan Miller wrote: I think it's time to start discussing the particulars of a 2.1 release. There's been a lot of advancements made in our plugin infrastructure. There's also been the pluggable console enhancements. It would be good to get a release out, with these capabilities. They provide a more solid platform for future enhancements, I think. There's also GShell and new monitoring capabilities. I'm probably missing a few other new functions. Finally, IIUC, 2.1 would be able to support a Terracotta plugin. I'd also be very interested to hear what WADI capabilities that could be exposed. I'm willing to bang the release manager drum. I see that Joe has already started tugging on the TCK chain What do others think? How close are we to a 2.1 release? What additional capabilities and bug fixes are needed? Can we wrap up development activities in the next week or two? --kevan
Re: [DISCUSS] 2.1 Release
Hi, I resumed this week-end some work on clustered deployment. I think this will be completed in about 2-3 weeks. This will allow distribute, uninstall, start, stop, et cetera of configurations to a cluster as a single logic operation. I am keen to get this change in for 2.1, if it does not delay 2.1. Thanks, Gianny On 02/11/2007, at 4:00 AM, Kevan Miller wrote: I think it's time to start discussing the particulars of a 2.1 release. There's been a lot of advancements made in our plugin infrastructure. There's also been the pluggable console enhancements. It would be good to get a release out, with these capabilities. They provide a more solid platform for future enhancements, I think. There's also GShell and new monitoring capabilities. I'm probably missing a few other new functions. Finally, IIUC, 2.1 would be able to support a Terracotta plugin. I'd also be very interested to hear what WADI capabilities that could be exposed. I'm willing to bang the release manager drum. I see that Joe has already started tugging on the TCK chain What do others think? How close are we to a 2.1 release? What additional capabilities and bug fixes are needed? Can we wrap up development activities in the next week or two? --kevan
[jira] Commented: (GERONIMO-3570) Review SQLLoginModule
[ https://issues.apache.org/jira/browse/GERONIMO-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540321 ] David Jencks commented on GERONIMO-3570: In rev 592223 I supplied an AbstractLoginModuleTest that uniformizes the test setups and makes it easier to determine if all relevant tests have been written. This also eliminated the Advanced tests as a separate class. Also relevant to the PropertiesFile and Certificate login module tests. Review SQLLoginModule - Key: GERONIMO-3570 URL: https://issues.apache.org/jira/browse/GERONIMO-3570 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: security Affects Versions: 2.0.x, 2.1 Reporter: Vamsavardhana Reddy Fix For: 2.0.x, 2.1 Review SQLLoginModule for potential violations and security risks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: basic security review
On Nov 1, 2007, at 9:59 AM, Jarek Gawor wrote: Yes, that's a good idea. Also, excellent work with reviewing the LoginModules and adding tests!!! I just added two new LoginModules to look at. I'm particularly concerned about CertificateChainLoginModule since it always returns true in its login() function. But I'm not exactly sure how this is being used. The CertificateChainLoginModule probably isn't much good in real life at this point. My thinking was that if we've set up an SSL connection with a client certificate, that means the SSL machinery has already verified that the client certificate is valid according to the CA's we know about, and we aren't going to get much more definitive about someone's identity than that. The real problem is that in order for this user to do anything we have to assign application level roles to them individually since there is no associated concept of enterprise roles or groups. In our current system this is a major inconvenience. I'm not sure it's worth actually fixing it since we'd get into providing a whole lot of identity enterprise role application role stores (properties file, sql, ldap, ). This kind of mapping is one of the big things I want triplesec to support in an easy-to-use-way. thanks david jencks Jarek On 10/31/07, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: I think we should create JIRAs for each review activity that results in code changes and update the wiki with the JIRA number. This way we will be able to track the progress on each activity in one central place. Also, add important points from this discussion thread to the wiki too. ++Vamsi On 10/30/07, Prasad Kashyap [EMAIL PROTECTED] wrote: I agree. Our strategy to make Geronimo secure should include an elaborate set of unit testcases, a rich set of tests in the security-testsuite in our testsuite framework, along with peer review of code in components that are potential security risks. We should aim to have imbricate or maybe even duplicate tests than have gaps. Towards this end, I created a security-testsuite in our testsuite framework. It contains one test now. I shall add some more soon. Please contribute to this testsuite with more and more tests that you can think of. Thanx Prasad On 10/29/07, Jarek Gawor [EMAIL PROTECTED] wrote: A few security problems were discovered in Geronimo in the last few months and weeks. Most of them were Geronimo-specific except one. Therefore, I think we should spend a little bit of our time to review our code and check for potential security problems. As the first step, I think we should identify components that make security decisions (e.g. LoginModules) or enable access to server management and control (e.g. MEJB) or any other components that might be important for sever security. Once we have a few components identified we can start the review. Besides finding and fixing the potential security problems during the review we must also ensure that we have decent tests for these components that cover a range of inputs. For each problem that we do discover, we must write a test case to make sure it never happens again. Basically, a problem is not fully addressed until we have a test for it. For now, I created the following page where we can keep track of the components and the review: http://cwiki.apache.org/confluence/display/GMOxDEV/Security+Review Feel free to update it in any way. Opinions? Ideas? Thoughts? Jarek
Re: [DISCUSS] 2.1 Release
Hi,
What I am doing does not rely on any clustering implementation. This
is how it will work:
1. User configures a cluster and a set of nodes belonging to it. You
can expect this type of GBeans:
!-- Cluster confuguration --
gbean name=ClusterInfo
class=org.apache.geronimo.clustering.config.BasicClusterInfo
attribute name=name${PlanClusterName}/attribute
reference name=NodeInfos/reference
/gbean
!-- Node configuration --
gbean name=NodeInfo
class=org.apache.geronimo.clustering.config.BasicNodeInfo
attribute name=name${PlanNodeName}/attribute
xml-attribute name=jmxConnectorInfo
ns:javabean xmlns:ns=http://geronimo.apache.org/xml/ns/
deployment/javabean-1.0
class=org.apache.geronimo.clustering.config.BasicExtendedJMXConnectorIn
fo
ns:property name=usernamesystem/ns:property
ns:property name=passwordmanager/ns:property
ns:property name=portocolrmi/ns:property
ns:property name=hostlocalhost/ns:property
ns:property name=port1099/ns:property
ns:property name=urlPath/jndi/rmi://localhost:
1099/JMXConnector/ns:property
/ns:javabean
/xml-attribute
/gbean
!-- Node configuration --
gbean name=SampleRemoteNodeInfo
class=org.apache.geronimo.clustering.config.BasicNodeInfo
attribute name=nameSAMPLE_REMOTE_NODE/attribute
xml-attribute name=jmxConnectorInfo
ns:javabean xmlns:ns=http://geronimo.apache.org/xml/ns/
deployment/javabean-1.0
class=org.apache.geronimo.clustering.config.BasicExtendedJMXConnectorIn
fo
ns:property name=usernamesystem/ns:property
ns:property name=passwordmanager/ns:property
ns:property name=portocolrmi/ns:property
ns:property name=hostlocalhost/ns:property
ns:property name=port1100/ns:property
ns:property name=urlPath/jndi/rmi://localhost:
1100/JMXConnector/ns:property
/ns:javabean
/xml-attribute
/gbean
2. User configures a master repository for clustered artifacts:
gbean name=MasterRepository
class=org.apache.geronimo.system.repository.Maven2Repository
attribute name=rootmaster-repository//attribute
reference name=ServerInfo
nameServerInfo/name
/reference
/gbean
gbean name=MasterConfigurationStore
class=org.apache.geronimo.clustering.deployment.MasterConfigurationStor
e
reference name=Repository
nameMasterRepository/name
/reference
reference name=ClusterConfigurationStoreDelegate
nameClusterConfigurationStoreDelegate/name
/reference
/gbean
gbean name=ClusterConfigurationStoreDelegate
class=org.apache.geronimo.clustering.deployment.BasicClusterConfigurati
onStoreDelegate
reference name=ClusterInfo
nameClusterInfo/name
/reference
/gbean
Note that above configurations are done against a Geronimo server,
which may or not may be a cluster node. In other words, this
configuration could be done against a kind of administration server
having all the necessary deployers.
3. Users deploys its artifacts against the master repository. The
target server builds locally the corresponding ConfigurationData and
sends it to the configured nodes. More accurately, ConfigurationData
is sent through standard RPC over the JMX communication infra. The
content of the ConfigurationData, e.g. jar, war et cetera, is sent
via the remote upload servlet used by the deployer CLI. Note that if
all the servers have access to the master repository, then a user
will simply configure a no-op ClusterConfigurationStoreDelegate so
that the artifact upload step is skipped.
You can expect the same type of approach for the control, i.e. start,
stop et cetera, of cconfigurations.
I also intend to implement remote start and stop of servers by
talking to gshell instances. However, I will work on it after the
above features.
As you are also working on clustering stuff, could you please give us
some heads-up?
Thanks,
Gianny
On 06/11/2007, at 9:34 AM, Jeff Genender wrote:
Gianny,
Since there are multiple clustering implementations going on at the
same
time, could you please keep us aprised of what you are doing so we
don't
clash?
Thanks,
Jeff
Gianny Damour wrote:
Hi,
I resumed this week-end some work on clustered deployment. I think
this
will be completed in about 2-3 weeks. This will allow distribute,
uninstall, start, stop, et cetera of configurations to a cluster as a
single logic operation. I am keen to get this change in for 2.1,
if it
does not delay 2.1.
Thanks,
Gianny
On 02/11/2007, at 4:00 AM, Kevan Miller wrote:
I think it's time to start discussing the particulars of a 2.1
release.
There's been a lot of advancements made in our plugin
[BUILD] 2.1: Failed for Revision: 592223
OpenEJB trunk at 592218
Geronimo Revision: 592223 built with tests included
See the full build-2100.log file at
http://people.apache.org/~prasad/binaries/trunk/20071105/build-2100.log
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/resources/META-INF/plan.xml
[INFO] [car:prepare-metadata]
[INFO] [car:package]
[INFO] Packaging module configuration:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/resources/META-INF/plan.xml
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-axis:2.1-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.configs:openejb:2.1-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] Building jar:
/home/prasad/geronimo/trunk/plugins/axis/axis/target/axis-2.1-SNAPSHOT.car
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: axis-2.1-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing
/home/prasad/geronimo/trunk/plugins/axis/axis/target/axis-2.1-SNAPSHOT.car to
/home/prasad/.m2/repository/org/apache/geronimo/configs/axis/2.1-SNAPSHOT/axis-2.1-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO]
[INFO] Building Geronimo Modules :: Webservices :: Builder
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.112 seconds
Time to generate code: 0.103 seconds
Time to compile code: 3.198 seconds
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes/META-INF
[INFO] Copying 2 files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes/META-INF
[INFO] [buildsupport:copy-xmlbeans-schemas {execution: default}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/clover/classes
[INFO] Copying 96 files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/clover/classes
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 6 source files to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 1 source file to
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.webservices.builder.ParsingTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.447 sec
Results :
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/prasad/geronimo/trunk/plugins/webservices/geronimo-webservices-builder/target/geronimo-webservices-builder-2.1-SNAPSHOT.jar
to
/home/prasad/.m2/repository/org/apache/geronimo/modules/geronimo-webservices-builder/2.1-SNAPSHOT/geronimo-webservices-builder-2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Modules :: OpenEJB :: Builder
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.082 seconds
Time to generate code: 0.15 seconds
Time to compile code: 2.553 seconds
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/prasad/geronimo/trunk/plugins/openejb/geronimo-openejb-builder/target/classes
[jira] Created: (GERONIMODEVTOOLS-249) Add internationalization capable support.
Add internationalization capable support. - Key: GERONIMODEVTOOLS-249 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-249 Project: Geronimo-Devtools Issue Type: Improvement Components: J2G Affects Versions: 1.0.0 Reporter: Kan Ogawa Priority: Minor In J2G eclipse plug-in, the internationalization support is not implemented, which is the creation of external message resources. Reference material is: http://www.ibm.com/developerworks/library/os-i18n/index.html?S_TACT=105AGX44S_CMP=EDU Geronimo development tools committors, this issue is a enhancement task, might be a low priority, and also needs many man-hours. If it is difficult for you to work on it for reasons of the priority of other existing issues, may I start to create the patch from now on? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3570) Review SQLLoginModule
[ https://issues.apache.org/jira/browse/GERONIMO-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540332 ] Vamsavardhana Reddy commented on GERONIMO-3570: --- At revision: 592284 o Merged rev 592223 from trunk. Review SQLLoginModule - Key: GERONIMO-3570 URL: https://issues.apache.org/jira/browse/GERONIMO-3570 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: security Affects Versions: 2.0.x, 2.1 Reporter: Vamsavardhana Reddy Fix For: 2.0.x, 2.1 Review SQLLoginModule for potential violations and security risks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3570) Review SQLLoginModule
[ https://issues.apache.org/jira/browse/GERONIMO-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540335 ] Vamsavardhana Reddy commented on GERONIMO-3570: --- At revision: 592287 o Merging rev 592227 from trunk Review SQLLoginModule - Key: GERONIMO-3570 URL: https://issues.apache.org/jira/browse/GERONIMO-3570 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: security Affects Versions: 2.0.x, 2.1 Reporter: Vamsavardhana Reddy Fix For: 2.0.x, 2.1 Review SQLLoginModule for potential violations and security risks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
problems when deploy ejb in eclipse
here is what I've done. I setup a app server on a machine, say A. And I test it, it works fine. In eclipse I install the server environment, apache Geronimo v2.0. The steps are as follows. 1.windows--preference--server--add 2.choose apache Geronimo v2.0, next 3.choose application Server Installation Directory. ( I chose a place in my computer, say B. I was not able to choose a place in A. Actually, I want to use computer A as my server, then why I have to specify Server Installation Directory on my own computer? Could anyone please tell me?) 4.Finish 5.File--new project--others, choose Server, next 6.In Server's host name, I typed 192.168.X.C, which is computer A, the remote server. next 7. specify the port ,then next. finish. After that I created my EJB project. I followed this tutorial.http://www.eclipse.org/webtools/community/tutorials/ejbtutorial/buildingejbs.html. Instead of using JBoss. I use Geronimo. But when I try to publish the project on computer A in eclipse. It says : Distribution of configuration failed. See log for details. unknown protocol: localhost java.net.MalformedURLException: unknown protocol: localhost at java.net.URL.init(Unknown Source) at java.net.URL.init(Unknown Source) at java.net.URL.init(Unknown Source) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.getRemoteDeployUploadURL(AbstractDeployCommand.java:149) at org.apache.geronimo.deployment.plugin.remote.RemoteDeployUtil.uploadFilesToServer(RemoteDeployUtil.java:59) at org.apache.geronimo.deployment.plugin.remote.DistributeCommand.massageFileNames(DistributeCommand.java:43) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:114) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Unknown Source) And when I stop the server, in console appears: Geronimo Application Server started 14:25:55,722 ERROR [log] failed jsp org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid to gbean: org.apache.geronimo.configs/webconsole-jetty6/2.0.1/car?J2EEApplication=org.apache.geronimo.configs/webconsole-jetty6/2.0.1/car,j2eeType=WebModule,name=standard.war at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87) at org.apache.geronimo.gbean.GBeanLifecycle$$EnhancerByCGLIB$$1187ad47.newInstance(generated) at org.apache.geronimo.jetty6.InternalJettyServletHolder.newInstance(InternalJettyServletHolder.java:81) at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:253) at org.apache.geronimo.jetty6.InternalJettyServletHolder.internalDoStart(InternalJettyServletHolder.java:119) at org.apache.geronimo.jetty6.InternalJettyServletHolder.access$000(InternalJettyServletHolder.java:38) at org.apache.geronimo.jetty6.InternalJettyServletHolder$StartCommand.lifecycleMethod(InternalJettyServletHolder.java:130) at org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:54) at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycleCommand(ThreadClassloaderHandler.java:57) at org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:52) at org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCommand(InstanceContextHandler.java:81) at org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:52) at org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCommand(UserTransactionHandler.java:63) at org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycleCommand(AbstractImmutableHandler.java:52) at org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleCommand(ComponentContextHandler.java:57) at org.apache.geronimo.jetty6.InternalJettyServletHolder.doStart(InternalJettyServletHolder.java:106) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:612) at org.mortbay.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:980) at org.mortbay.jetty.servlet.ServletHandler.setFilterMappings(ServletHandler.java:1016) at org.apache.geronimo.jetty6.JettyFilterMapping.resetJettyFilterMappings(JettyFilterMapping.java:129) at org.apache.geronimo.jetty6.JettyFilterMapping.access$100(JettyFilterMapping.java:35) at org.apache.geronimo.jetty6.JettyFilterMapping$1.memberRemoved(JettyFilterMapping.java:113) at org.apache.geronimo.gbean.runtime.ProxyCollection.removeTarget(ProxyCollection.java:129) at
