[jira] Resolved: (GERONIMO-4733) Unable to starting to configure Apache mod_jk
[ https://issues.apache.org/jira/browse/GERONIMO-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-4733. Resolution: Fixed Commit changes to trunk At revision: 794146, 2.1.5 At revision: 794147. Thanks for the patch, Shawn. Unable to starting to configure Apache mod_jk -- Key: GERONIMO-4733 URL: https://issues.apache.org/jira/browse/GERONIMO-4733 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.5, 2.2 Environment: Windows XP SP2, IE6.0 Reporter: Shiny Cheng Assignee: Shawn Jiang Fix For: 2.1.5, 2.2 Attachments: G4733_21.patch_updated, G4733_trunk.patch_updated From Console Navigation, click Apache HTTP and then Get Started. The following exception will appear, which means this function doesn't work correctly. java.lang.ClassCastException: [Lorg.apache.geronimo.tomcat.connector.TomcatWebConnector; cannot be cast to [Lorg.apache.geronimo.management.geronimo.WebConnector; org.apache.geronimo.console.apache.jk.AJPHandler.actionBeforeView(AJPHandler.java:62) org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:112) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139) javax.servlet.http.HttpServlet.service(HttpServlet.java:693) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121) javax.servlet.http.HttpServlet.service(HttpServlet.java:693) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:65) org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:125) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4743) a bug when the assembled server stops in eclipse
[ https://issues.apache.org/jira/browse/GERONIMO-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bin He updated GERONIMO-4743: - Component/s: (was: Plugins) car-maven-plugin a bug when the assembled server stops in eclipse -- Key: GERONIMO-4743 URL: https://issues.apache.org/jira/browse/GERONIMO-4743 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: car-maven-plugin Affects Versions: 2.2 Environment: jre 1.6 windows xp sp2 Reporter: Bin He Priority: Minor Fix For: 2.2 steps: 1、install eclipse and Geronimo Eclipse Plugin ,and define a Geronimo server and server runtime in Eclipse 2、Install and start Geronimo server 3、Install hello sample 4、Double clicking the Geronimo server will bring up the server editor in the main window. Items for working with the server can be found on the Plugin and plugin group page. Clicking on the Plugin tab and selecting Create Custom Assembly will bring up the New Server Custom Assembly dialog . 5、Enter the name for your assembled server 6、Select the following plugins: Geronimo Assemblies :: Boilerplate; Geronimo Framework, Configs :: GShell Framework; Geronimo Framework, Configs :: GShell Geronimo; Geronimo Framework, Configs :: GShell Remote org.apache.geronimo.configs/tomcat6/x.x.x.x/car org.apache.geronimo.configs/tomcat6-deployer/x.x.x.x/car Hello plugin 7、Click Assemble button 8、Unzip the assembled server %WASCE_HOME%\var\temp\your_assembled_server_name 9、First stop and remove the geronimo server,then install and start the assembled server 10、check if hello sample works fine problems: 1、The assembled server is well started in eclipse.But when it stops ,there is a problem sometimes（not always）: Exception in thread Multicast Discovery Agent Notifier java.lang.NoClassDefFoundError: org/apache/openejb/server/DiscoveryRegistry$ServiceRemovedTask at org.apache.openejb.server.DiscoveryRegistry.serviceRemoved(DiscoveryRegistry.java:129) at org.apache.openejb.server.discovery.MulticastDiscoveryAgent$Listener$2.run(MulticastDiscoveryAgent.java:420) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassNotFoundException: org.apache.openejb.server.DiscoveryRegistry$ServiceRemovedTask in classloader org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:414) at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:256) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) ... 5 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Security configuration principal-role mapping
Previously and in a common way, we do principal-role mapping in a deployment plan (such as geronimo-web.xml,openejb-jar.xml), like: role-mappings role role-name=user principal class=o.a.g.s.r.providers.GeronimoGroupPrincipal name=UserGrp/ /role ... /role-mappings But in Geronimo2.2 , after a jira https://issues.apache.org/jira/browse/GERONIMO-4523 It seems that we can do the principal-role mapping without the need for Geronimo-specific deployment plans. Has the feature been implemented? If so, how to do the mapping? -- Best Regards, Rodger.
[jira] Closed: (GERONIMO-4743) a bug when the assembled server stops in eclipse
[ https://issues.apache.org/jira/browse/GERONIMO-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bin He closed GERONIMO-4743. Resolution: Fixed a bug when the assembled server stops in eclipse -- Key: GERONIMO-4743 URL: https://issues.apache.org/jira/browse/GERONIMO-4743 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: car-maven-plugin Affects Versions: 2.2 Environment: jre 1.6 windows xp sp2 Reporter: Bin He Priority: Minor Fix For: 2.2 steps: 1、install eclipse and Geronimo Eclipse Plugin ,and define a Geronimo server and server runtime in Eclipse 2、Install and start Geronimo server 3、Install hello sample 4、Double clicking the Geronimo server will bring up the server editor in the main window. Items for working with the server can be found on the Plugin and plugin group page. Clicking on the Plugin tab and selecting Create Custom Assembly will bring up the New Server Custom Assembly dialog . 5、Enter the name for your assembled server 6、Select the following plugins: Geronimo Assemblies :: Boilerplate; Geronimo Framework, Configs :: GShell Framework; Geronimo Framework, Configs :: GShell Geronimo; Geronimo Framework, Configs :: GShell Remote org.apache.geronimo.configs/tomcat6/x.x.x.x/car org.apache.geronimo.configs/tomcat6-deployer/x.x.x.x/car Hello plugin 7、Click Assemble button 8、Unzip the assembled server %WASCE_HOME%\var\temp\your_assembled_server_name 9、First stop and remove the geronimo server,then install and start the assembled server 10、check if hello sample works fine problems: 1、The assembled server is well started in eclipse.But when it stops ,there is a problem sometimes（not always）: Exception in thread Multicast Discovery Agent Notifier java.lang.NoClassDefFoundError: org/apache/openejb/server/DiscoveryRegistry$ServiceRemovedTask at org.apache.openejb.server.DiscoveryRegistry.serviceRemoved(DiscoveryRegistry.java:129) at org.apache.openejb.server.discovery.MulticastDiscoveryAgent$Listener$2.run(MulticastDiscoveryAgent.java:420) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassNotFoundException: org.apache.openejb.server.DiscoveryRegistry$ServiceRemovedTask in classloader org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:414) at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:256) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) ... 5 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: The scope and schedule for G 2.2 samples release
djencks wrote: Isn't jsf pretty much a struts replacement? I kinda thought struts and struts 2 were obsolete after jsf came out. Activemq broker and the apache directory plugin both show using spring in geronimo, although not as end-user apps. The reason I add this is that I saw user asking how-to about using struts/spring in geronimo for several times in the mailing list or related forum. So I think it might be helpful if we have a sample about it. For JSF, let me check if we have some available code to contribute. djencks wrote: 4. Add or update a sample to demo JTA ??? do you mean how to use UserTransaction? I'm a little bit confusing here too. Cause I think there are some codes in daytrader using JTA. We may make it clear as progress is forward. djencks wrote: CSA? CSA shorts for Custom Server Assembly :-) djencks wrote: 7. Figure out a way to release JEE application ear/war balls of G samples. IIRC the missing bit is the geronimo plan. I don't think there is an absolute requirement that the plan be inside the javaee application. So I think I would pursue this goal by seeing if we can get the car- maven-plugin to deploy the processed plan as an attached artifact. This will result in separate jetty and tomcat plans which I think is OK. Can you explain more about using car-maven-plugin to deploy the processed plan as an attached artifact? how will it work? thanks! djencks wrote: 8. Ensure G 2.1.2 samples plugins installable and functionable on G 2.2 server. This is not possible due to the large number of class changes in gbeans such as the jetty web app context gbean. So cancel this. djencks wrote: I am going to work on this list and open a JIRA to track it, and will post my progress to this thread from time to time. Welcome any comments! Great to see someone working on this! Glad to be helpful somewhat Regards, Forrest -- View this message in context: http://www.nabble.com/The-scope-and-schedule-for-G-2.2-samples-release-tp24177645s134p24492704.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: Security configuration principal-role mapping
On Jul 14, 2009, at 11:29 PM, Rodger wrote: Previously and in a common way, we do principal-role mapping in a deployment plan (such as geronimo-web.xml,openejb-jar.xml), like: role-mappings role role-name=user principal class=o.a.g.s.r.providers.GeronimoGroupPrincipal name=UserGrp/ /role ... /role-mappings But in Geronimo2.2 , after a jira https://issues.apache.org/jira/browse/GERONIMO-4523 It seems that we can do the principal-role mapping without the need for Geronimo-specific deployment plans. Has the feature been implemented? If so, how to do the mapping? I'm not sure if there is an example of how to do this. 1. In a plan for a geronimo plugin, either a javaee app or service (gbean) plugin, include a security element following the http://geronimo.apache.org/xml/ns/security-2.0 schema. Be sure it has a name attribute. 2. add a dependency on the plugin from (1) to your javaee app. 3. In the geronimo plan for your javaee app, include a security-ref element with a name element referring to the security element in (1). You still need a geronimo plan for the javaee app, this just lets you share the principal-role mapping between several apps. I think that's how it works. david jencks -- Best Regards, Rodger.
Re: The scope and schedule for G 2.2 samples release
On Jul 14, 2009, at 11:40 PM, Forrest_Xia wrote: djencks wrote: Isn't jsf pretty much a struts replacement? I kinda thought struts and struts 2 were obsolete after jsf came out. Activemq broker and the apache directory plugin both show using spring in geronimo, although not as end-user apps. The reason I add this is that I saw user asking how-to about using struts/spring in geronimo for several times in the mailing list or related forum. So I think it might be helpful if we have a sample about it. For JSF, let me check if we have some available code to contribute. djencks wrote: 4. Add or update a sample to demo JTA ??? do you mean how to use UserTransaction? I'm a little bit confusing here too. Cause I think there are some codes in daytrader using JTA. We may make it clear as progress is forward. djencks wrote: CSA? CSA shorts for Custom Server Assembly :-) djencks wrote: 7. Figure out a way to release JEE application ear/war balls of G samples. IIRC the missing bit is the geronimo plan. I don't think there is an absolute requirement that the plan be inside the javaee application. So I think I would pursue this goal by seeing if we can get the car- maven-plugin to deploy the processed plan as an attached artifact. This will result in separate jetty and tomcat plans which I think is OK. Can you explain more about using car-maven-plugin to deploy the processed plan as an attached artifact? how will it work? thanks! I haven't done this in a long time although I think the mojo that actually builds the car file must do something like this... IIRC maven's project object has a method that lets you attach a file to the project, which means it will get deployed into the maven repo. I think we'd want to add a call to this method in the PlanProcessorMojo after we've completely processed the plan. hope this helps a bit :-) david jencks djencks wrote: 8. Ensure G 2.1.2 samples plugins installable and functionable on G 2.2 server. This is not possible due to the large number of class changes in gbeans such as the jetty web app context gbean. So cancel this. djencks wrote: I am going to work on this list and open a JIRA to track it, and will post my progress to this thread from time to time. Welcome any comments! Great to see someone working on this! Glad to be helpful somewhat Regards, Forrest -- View this message in context: http://www.nabble.com/The-scope-and-schedule-for-G-2.2-samples-release-tp24177645s134p24492704.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Commented: (GERONIMO-4723) Replace our dojo repackaging with the released dojo-war
[ https://issues.apache.org/jira/browse/GERONIMO-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731327#action_12731327 ] David Jencks commented on GERONIMO-4723: So, apparently this works fine for current dojo. The legacy 0.4.3 dojo doesn't seem to be released to maven but is in an accessible svn repo. rev 794168 in externals/trunk builds a dojo 0.4.3 war directly from a svn checkout of the dojo source. Could someone see what happens if we build and use this instead of plugins/dojo-legacy/geronimo-dojo-legacy? Replace our dojo repackaging with the released dojo-war --- Key: GERONIMO-4723 URL: https://issues.apache.org/jira/browse/GERONIMO-4723 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: web Affects Versions: 2.2 Reporter: David Jencks Attachments: GERONIMO-2723.patch dojo has a dojo-war that looks pretty similar to our repacked dojo war. I can't quite tell if it works. Maybe someone who understands what dojo does could try it? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Which dojo?
Jay -- many thanks for trying out the patch and committing it. I think the last artifact in our svn repo is the dojo 0.4.3. I can't find it released anywhere but the source code is in a handy svn repo. I cooked up a modification of our war-packaging for it that uses the maven scm plugin to check out the source so it can be packaged easily. I wonder if someone could try this out and see if it works? -- check out new war project and build it svn co https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3 cd geronimo-dojo-0.4.3 mvn clean install -- modify the plugins/dojo-legacy stuff so that geronimo-dojo-legacy is not built the dojo-legacy-jetty and dojo-legacy-tomcat plugins use the geronimo- dojo-0.4.3-1.0-SNAPSHOT war file instead of the geronimo-dojo-legacy war. -- build the server and see if the parts that use the legacy dojo still work (debug views??? I'm not sure) many thanks david jencks On Jul 10, 2009, at 6:58 AM, Kevan Miller wrote: On Jul 9, 2009, at 5:59 PM, David Jencks wrote: On Jul 9, 2009, at 2:44 PM, Jay D. McHugh wrote: Hey David, I'm starting to take a look at it today. They have a 1.3.1 version out - any objections to me switching the patch to use it? Not at all -- I just thought I'd start small since usually I change 18 things at once and then can't tell what change broke what feature :-) I think kevan mentioned offline he might take a look also. I think I've been running locally with this patch for a couple weeks and haven't seen any admin console problems, but that doesn't mean much one way or another. I built with the patch and ran testsuite on Jetty. Everything looked good to me (except for a corba-testsuite test that hung). Jay, If you can test with the latest Dojo version and things look good to you, I'd say go ahead and apply the updates. --kevan
[jira] Created: (GERONIMO-4746) OpenEJB portlet page crushes.
OpenEJB portlet page crushes. - Key: GERONIMO-4746 URL: https://issues.apache.org/jira/browse/GERONIMO-4746 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.2 Environment: r794119 snapshot build Reporter: Kan Ogawa Priority: Critical Is this related to upgrade to Dojo toolkit 1.3.0? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4746) OpenEJB portlet page crushes.
[ https://issues.apache.org/jira/browse/GERONIMO-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kan Ogawa updated GERONIMO-4746: Attachment: GERONIMO-4746_ScreenShot.png OpenEJB portlet page crushes. - Key: GERONIMO-4746 URL: https://issues.apache.org/jira/browse/GERONIMO-4746 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: r794119 snapshot build Reporter: Kan Ogawa Priority: Critical Attachments: GERONIMO-4746_ScreenShot.png Is this related to upgrade to Dojo toolkit 1.3.0? -- 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: 794147
Geronimo Revision: 794147 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 43 minutes 10 seconds
[INFO] Finished at: Wed Jul 15 03:47:42 EDT 2009
[INFO] Final Memory: 431M/972M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/logs-0300-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/logs-0300-jetty/
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:49.131
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/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:13.021)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:36.516)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:40.971)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.907)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:25.416)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:21.949) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:13.264)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:54.701)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:58.624)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.897)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.996)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:35.094)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.690)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.101)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:59.609)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.950)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:32.055)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.864)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:51.103)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:32.864)
[INFO] web-testsuite/test-2.5
[jira] Commented: (GERONIMO-4746) OpenEJB portlet page crushes.
[ https://issues.apache.org/jira/browse/GERONIMO-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731368#action_12731368 ] Rex Wang commented on GERONIMO-4746: Should be.. script type=text/javascript src=/dojo/dojo/dojo.js djConfig=parseOnLoad: true/script from its view.jsp OpenEJB portlet page crushes. - Key: GERONIMO-4746 URL: https://issues.apache.org/jira/browse/GERONIMO-4746 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: r794119 snapshot build Reporter: Kan Ogawa Priority: Critical Attachments: GERONIMO-4746_ScreenShot.png Is this related to upgrade to Dojo toolkit 1.3.0? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4621) Exception occurs when export debugviews-console-tomcat plugin
[ https://issues.apache.org/jira/browse/GERONIMO-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731374#action_12731374 ] Han Hong Fang commented on GERONIMO-4621: - Hi all, I verify the patch with build 20090714, and confirm that the problem is fixed. I close this issue. Janet Exception occurs when export debugviews-console-tomcat plugin -- Key: GERONIMO-4621 URL: https://issues.apache.org/jira/browse/GERONIMO-4621 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: build: geronimo-tomcat6-javaee5-2.1.4-bin.zip OS: Windows XP (English) SP2 Browser:IE 7 Reporter: Han Hong Fang Assignee: Han Hong Fang Fix For: 2.1.5, 2.2 Attachments: GERONIMO-4621.patch Steps to reproduce this problem: - start geronimo - in admin console, open application - plugin - in Create Plugin portlet, select org.apache.geronimo.plugins/debugviews-console-tomcat/2.1.4/car, and then click Export Plugin - Next page, click Save Plugin Data Exception occurs as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IndexOutOfBoundsException: Index: 1, Size: 0 java.util.ArrayList.add(ArrayList.java:394) org.apache.geronimo.console.car.ExportConfigHandler.actionAfterView(ExportConfigHandler.java:184) org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:114) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:125) note The full stack trace of the root cause is available in the Apache Tomcat/6.0.18 logs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4621) Exception occurs when export debugviews-console-tomcat plugin
[ https://issues.apache.org/jira/browse/GERONIMO-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang closed GERONIMO-4621. --- Exception occurs when export debugviews-console-tomcat plugin -- Key: GERONIMO-4621 URL: https://issues.apache.org/jira/browse/GERONIMO-4621 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Environment: build: geronimo-tomcat6-javaee5-2.1.4-bin.zip OS: Windows XP (English) SP2 Browser:IE 7 Reporter: Han Hong Fang Assignee: Han Hong Fang Fix For: 2.1.5, 2.2 Attachments: GERONIMO-4621.patch Steps to reproduce this problem: - start geronimo - in admin console, open application - plugin - in Create Plugin portlet, select org.apache.geronimo.plugins/debugviews-console-tomcat/2.1.4/car, and then click Export Plugin - Next page, click Save Plugin Data Exception occurs as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IndexOutOfBoundsException: Index: 1, Size: 0 java.util.ArrayList.add(ArrayList.java:394) org.apache.geronimo.console.car.ExportConfigHandler.actionAfterView(ExportConfigHandler.java:184) org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:114) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:125) note The full stack trace of the root cause is available in the Apache Tomcat/6.0.18 logs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Which dojo?
I'd like to try it :-) -Rex 2009/7/15 David Jencks david_jen...@yahoo.com Jay -- many thanks for trying out the patch and committing it. I think the last artifact in our svn repo is the dojo 0.4.3. I can't find it released anywhere but the source code is in a handy svn repo. I cooked up a modification of our war-packaging for it that uses the maven scm plugin to check out the source so it can be packaged easily. I wonder if someone could try this out and see if it works? -- check out new war project and build it svn co https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3 cd geronimo-dojo-0.4.3 mvn clean install -- modify the plugins/dojo-legacy stuff so that geronimo-dojo-legacy is not built the dojo-legacy-jetty and dojo-legacy-tomcat plugins use the geronimo-dojo-0.4.3-1.0-SNAPSHOT war file instead of the geronimo-dojo-legacy war. -- build the server and see if the parts that use the legacy dojo still work (debug views??? I'm not sure) many thanks david jencks On Jul 10, 2009, at 6:58 AM, Kevan Miller wrote: On Jul 9, 2009, at 5:59 PM, David Jencks wrote: On Jul 9, 2009, at 2:44 PM, Jay D. McHugh wrote: Hey David, I'm starting to take a look at it today. They have a 1.3.1 version out - any objections to me switching the patch to use it? Not at all -- I just thought I'd start small since usually I change 18 things at once and then can't tell what change broke what feature :-) I think kevan mentioned offline he might take a look also. I think I've been running locally with this patch for a couple weeks and haven't seen any admin console problems, but that doesn't mean much one way or another. I built with the patch and ran testsuite on Jetty. Everything looked good to me (except for a corba-testsuite test that hung). Jay, If you can test with the latest Dojo version and things look good to you, I'd say go ahead and apply the updates. --kevan
Re: Which dojo?
tried it. 1. svn co https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3 mvn clean install success! 2. modify the plugins/dojo-legacy stuff the patch in attachment shows the modification. build successfully 3. I did not build the entire server, but just remove the old one, and install the new one. I believe only the debug-views portlets use this legacy dojo, because when I stop the dojo-legacy-tomcat plugin, only the debugviews-console-tomcat web project stopped autoly. and I also searched all the jsps underneath plugins folder in the server build tree, only show the ones from debugviews holding reference to /dojo/0.4/dojo.js results: Unfortunately, the debugviews portlet don't display corretly... I make some screen shot. Shall we open a jira for this so that I can upload them, which apparently shows dojo not work correctly? HTH Rex. 2009/7/15 Rex Wang rwo...@gmail.com I'd like to try it :-) -Rex 2009/7/15 David Jencks david_jen...@yahoo.com Jay -- many thanks for trying out the patch and committing it. I think the last artifact in our svn repo is the dojo 0.4.3. I can't find it released anywhere but the source code is in a handy svn repo. I cooked up a modification of our war-packaging for it that uses the maven scm plugin to check out the source so it can be packaged easily. I wonder if someone could try this out and see if it works? -- check out new war project and build it svn co https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3 cd geronimo-dojo-0.4.3 mvn clean install -- modify the plugins/dojo-legacy stuff so that geronimo-dojo-legacy is not built the dojo-legacy-jetty and dojo-legacy-tomcat plugins use the geronimo-dojo-0.4.3-1.0-SNAPSHOT war file instead of the geronimo-dojo-legacy war. -- build the server and see if the parts that use the legacy dojo still work (debug views??? I'm not sure) many thanks david jencks On Jul 10, 2009, at 6:58 AM, Kevan Miller wrote: On Jul 9, 2009, at 5:59 PM, David Jencks wrote: On Jul 9, 2009, at 2:44 PM, Jay D. McHugh wrote: Hey David, I'm starting to take a look at it today. They have a 1.3.1 version out - any objections to me switching the patch to use it? Not at all -- I just thought I'd start small since usually I change 18 things at once and then can't tell what change broke what feature :-) I think kevan mentioned offline he might take a look also. I think I've been running locally with this patch for a couple weeks and haven't seen any admin console problems, but that doesn't mean much one way or another. I built with the patch and ran testsuite on Jetty. Everything looked good to me (except for a corba-testsuite test that hung). Jay, If you can test with the latest Dojo version and things look good to you, I'd say go ahead and apply the updates. --kevan dojo-legacy.patch Description: Binary data
Re: Which dojo?
On Jul 15, 2009, at 3:50 AM, David Jencks wrote: Jay -- many thanks for trying out the patch and committing it. I think the last artifact in our svn repo is the dojo 0.4.3. I can't find it released anywhere but the source code is in a handy svn repo. I cooked up a modification of our war-packaging for it that uses the maven scm plugin to check out the source so it can be packaged easily. I wonder if someone could try this out and see if it works? There is one other alternative -- and that's rewriting the admin console debug views, so that they aren't reliant on 0.4.3. If there's someone familiar with Dojo or is interested in learning about Dojo, this would be a good project. It would be nice to get rid of 0.4.3, altogether... --kevan
Re: Which dojo?
agree, the new 1.3.0 also brings some code change to other portlets(see https://issues.apache.org/jira/browse/GERONIMO-4746), in any case, we need to learn it. I'd like to look into it further. -Rex 2009/7/15 Kevan Miller kevan.mil...@gmail.com On Jul 15, 2009, at 3:50 AM, David Jencks wrote: Jay -- many thanks for trying out the patch and committing it. I think the last artifact in our svn repo is the dojo 0.4.3. I can't find it released anywhere but the source code is in a handy svn repo. I cooked up a modification of our war-packaging for it that uses the maven scm plugin to check out the source so it can be packaged easily. I wonder if someone could try this out and see if it works? There is one other alternative -- and that's rewriting the admin console debug views, so that they aren't reliant on 0.4.3. If there's someone familiar with Dojo or is interested in learning about Dojo, this would be a good project. It would be nice to get rid of 0.4.3, altogether... --kevan
Re: Apache Con US '09 Geronimo Track
On Jul 14, 2009, at 10:59 PM, Joe Bohn wrote: Sorry ... I think you should just consider the lack of comments to be silent approval :-). I was, just giving people a reminder... I really am fine with it just as it is worded. However, here are some other thoughts. - Do we need to clearly state that Geronimo delivers (out of the box) a fully compliant Java EE Server in addition to stating that the plugins can be used to assemble one? No. Was kind of thinking ahead to the track description, not just the call for papers. Don't think it hurts. So, will leave it... - In listing the subprojects should we mention JavaMail, Component and Transaction support? Sure. 'etc' was easier than typing. ;-) They are certainly more interesting than 'Specs'... - Do we want to mention anything about choice in core server components when building server configurations - for example support for both Tomcat and Jetty or CXF and Axis2? One other potential topic - custom server assemblies Agreed. Updated version... * Apache Geronimo is a lightweight, flexible, component-based server for building dynamic application server environments. Geronimo plugins can be assembled into a fully compliant Java EE Server. However, it can be easily assembled into a server providing a subset of functionality or a minimal subset required to meet the requirements of a set of applications. In addition to the Apache Geronimo Server, the Geronimo project is also comprised of a number of subprojects: Development Tools, XBean, Yoko, GShell, JavaMail, Connector/Transaction, etc. Potential topics for the Geronimo Track include, but are in no way limited to: * Geronimo architecture, * Systems management, * Custom server assemblies, * Application development and user experiences, * OSGi Blueprint, * Kernel restructuring, * Java EE 6, * etc. * --kevan
[BUILD] trunk: Failed for Revision: 794246
Geronimo Revision: 794246 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 49 minutes 54 seconds
[INFO] Finished at: Wed Jul 15 09:54:46 EDT 2009
[INFO] Final Memory: 401M/992M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/logs-0900-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/logs-0900-jetty/
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:49.552
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/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:15.499)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:35.886)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:39.386)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.517)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:23.870)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:21.293) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:14.193)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:53.952)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:10.791)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:48.186)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.111)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:33.914)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:35.573)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.876)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.876)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.307)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:30.918)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.786)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:50.809)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.864)
[INFO] web-testsuite/test-2.5
[jira] Commented: (GERONIMO-4642) WS-Security support for JAX-WS Web Services
[
https://issues.apache.org/jira/browse/GERONIMO-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731544#action_12731544
]
Jarek Gawor commented on GERONIMO-4642:
---
Rahul,
I modified your patch for web service clients and made it a bit more generic.
Instead of specifying a usertoken element, the user can specify any number of
arbitrary properties that will be set of the port using a property element.
That way we can configure any type of properties, for ws-security or not.
To configure ws-security properties specifically, the user will need to prefix
each property with wss4j.in. (for inbound settings) or wss4j.out. (for
outbound settings). For example:
{code}
property name=wss4j.out.actionUsernameToken Timestamp/property
property name=wss4j.out.userfoo/property
property name=wss4j.out.passwordbar/property
{code}
These changes were committed to trunk (revision 794318). Thanks for the patch!
WS-Security support for JAX-WS Web Services
-
Key: GERONIMO-4642
URL: https://issues.apache.org/jira/browse/GERONIMO-4642
Project: Geronimo
Issue Type: New Feature
Security Level: public(Regular issues)
Components: webservices
Environment: Apache Geronimo, Apache CXF, Apache Axis2, Ws-Security,
Web Services, Java, Linux
Reporter: Rahul Mehta
Priority: Minor
Attachments: site.patch, usernameToken.patch, usernameToken[2].patch
Original Estimate: 2016h
Remaining Estimate: 2016h
To integrate and enable the WS-Security features of Apache Axis2 and Apache
CXF in Apache Geronimo:
--
Apache Geronimo supports two JAX-WS providers: Axis2 and CXF and both of
these libraries have some WS-Security features. But these features are not
integrated/enabled in Geronimo. So the goal is to enable these features from
within Geronimo. That involves basically two things:
1) that the modules (i.e. WSS4J) that provide the WS-Security features for
Axis2 and CXF are installed with Geronimo, and
2) that the WS-Security features such as [XML Security ('XML Signature' -
allows one to send along with the message a digital signature of it, which
assures that no one modified the message content between the sender and
receiver, 'XML Encryption' -allows one to encrypt the message body or only
its part using the given cryptography algorithm) and Tokens ('Username
Tokens' - WS-Security scenario adds username and password values to the
message header, 'Timestamps' - Timestamps specify how long the security data
remains valid, 'SAML Tokens')] can be enabled and configured on web services
via Geronimo deployment descriptors and/or annotations. For example, given
some web service that is annotated with @WebService; so to ensure that the
service only accepts WS-Security -secured messages, it should be something
like to add @WS-Security annotation.
Further in detail, we can consider WS-Security policies which can be applied
to the SOAP messages that pass between web services and web service controls.
A WS-Security is controlled in WS-Security policy files. The WS-Security
policy file (WSSE file) defines the security policy applied to the SOAP
messages that pass between web services and their clients.[1]
So we can use something like following annotation @WS-Security
file=MyWebServicePolicy.wsse Example: @WebService @WS-Security
file=MyWebServicePolicy.wsse
public class xyz
The @WS-Security annotation determines the WS-Security policy file (WSSE) to
be applied to (1) incoming SOAP invocations of the web service's methods and
(2) the outgoing SOAP messages containing the value returned by the web
service's methods.[1]. The attribute file in the above mentioned annotation
specifies the path to the WS-Security policy file (WSSE file -
MyWebServicePolicy.wsse) used by the web service.
Besides configuring WS-Security properties for web services we also need to
configure the same sort of properties for Web Service references
(@WebServiceRef) so that clients can also make WS-Security secured calls.
In addition, I think we can also define some security feature something like
SecurityFeature similar to other WebService Feature(s) such as
AddressingFeature, MTOMFeature and RespectBindingFeature . This new feature
can also have the enabled property like other features that is used to
store whether a particular feature should be enabled or disabled. This type
should provide either a constructor argument and/or a method that will allow
the web service developer to set the enabled property. The meaning of enabled
or disabled is determined by each individual WebServiceFeature. It is
Re: Which dojo?
On Jul 15, 2009, at 6:31 AM, Kevan Miller wrote: On Jul 15, 2009, at 3:50 AM, David Jencks wrote: Jay -- many thanks for trying out the patch and committing it. I think the last artifact in our svn repo is the dojo 0.4.3. I can't find it released anywhere but the source code is in a handy svn repo. I cooked up a modification of our war-packaging for it that uses the maven scm plugin to check out the source so it can be packaged easily. I wonder if someone could try this out and see if it works? There is one other alternative -- and that's rewriting the admin console debug views, so that they aren't reliant on 0.4.3. If there's someone familiar with Dojo or is interested in learning about Dojo, this would be a good project. It would be nice to get rid of 0.4.3, altogether... Of course this would be much much better but I thought that we'd investigated this and Joe Leong said it would be a lot of work and no one volunteered to do it? I thought easier to start over and use a good web framework and portlet 2.0 was the conclusion. thanks david jencks --kevan
Re: Which dojo?
On Jul 15, 2009, at 6:27 AM, Rex Wang wrote: tried it. 1. svn co https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3 mvn clean install success! 2. modify the plugins/dojo-legacy stuff the patch in attachment shows the modification. build successfully 3. I did not build the entire server, but just remove the old one, and install the new one. I believe only the debug-views portlets use this legacy dojo, because when I stop the dojo-legacy-tomcat plugin, only the debugviews-console-tomcat web project stopped autoly. and I also searched all the jsps underneath plugins folder in the server build tree, only show the ones from debugviews holding reference to /dojo/ 0.4/dojo.js results: Unfortunately, the debugviews portlet don't display corretly... I make some screen shot. Shall we open a jira for this so that I can upload them, which apparently shows dojo not work correctly? Or we could try to fix them :-) I looked at the two war files and they are different and I wonder what we actually use. old war (geronimo-dojo-legacy): -rw-r--r--151841 15-May-2007 02:11:02 dojo.js -rw-r--r--326567 15-May-2007 02:11:04 dojo.js.uncompressed.js -rw-r--r-- 1170 15-May-2007 02:06:02 flash6_gateway.swf -rw-r--r-- 2364 15-May-2007 02:06:02 iframe_history.html -rw-r--r-- 11346 15-May-2007 02:06:02 LICENSE -rw-r--r-- 13133 14-Jul-2009 15:01:02 META-INF/LICENSE -rw-r--r-- 587 14-Jul-2009 15:01:02 META-INF/NOTICE -rw-r--r-- 1609 15-May-2007 02:11:32 src/a11y.js ... everything else is under src/ new war (geronimo-dojo-0.4.3): just the contents of src from geronimo-dojo-legacy. So what do we actually use here? if its just dojo.js we can shrink it by leaving out the uncompressed.js and all the little files. If its just the little files under src we can use the new war and change the references to leave out the src/ bit. Maybe I can come up with an alternate profile to build a war with just dojo.js in it?? wishing I understood javascript delivery even a little bit... david jencks HTH Rex. 2009/7/15 Rex Wang rwo...@gmail.com I'd like to try it :-) -Rex 2009/7/15 David Jencks david_jen...@yahoo.com Jay -- many thanks for trying out the patch and committing it. I think the last artifact in our svn repo is the dojo 0.4.3. I can't find it released anywhere but the source code is in a handy svn repo. I cooked up a modification of our war-packaging for it that uses the maven scm plugin to check out the source so it can be packaged easily. I wonder if someone could try this out and see if it works? -- check out new war project and build it svn co https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3 cd geronimo-dojo-0.4.3 mvn clean install -- modify the plugins/dojo-legacy stuff so that geronimo-dojo-legacy is not built the dojo-legacy-jetty and dojo-legacy-tomcat plugins use the geronimo-dojo-0.4.3-1.0-SNAPSHOT war file instead of the geronimo- dojo-legacy war. -- build the server and see if the parts that use the legacy dojo still work (debug views??? I'm not sure) many thanks david jencks On Jul 10, 2009, at 6:58 AM, Kevan Miller wrote: On Jul 9, 2009, at 5:59 PM, David Jencks wrote: On Jul 9, 2009, at 2:44 PM, Jay D. McHugh wrote: Hey David, I'm starting to take a look at it today. They have a 1.3.1 version out - any objections to me switching the patch to use it? Not at all -- I just thought I'd start small since usually I change 18 things at once and then can't tell what change broke what feature :-) I think kevan mentioned offline he might take a look also. I think I've been running locally with this patch for a couple weeks and haven't seen any admin console problems, but that doesn't mean much one way or another. I built with the patch and ran testsuite on Jetty. Everything looked good to me (except for a corba-testsuite test that hung). Jay, If you can test with the latest Dojo version and things look good to you, I'd say go ahead and apply the updates. --kevan dojo-legacy.patch
Re: Which dojo?
On Jul 15, 2009, at 12:43 PM, David Jencks wrote: Of course this would be much much better but I thought that we'd investigated this and Joe Leong said it would be a lot of work and no one volunteered to do it? Right. I don't really know how much work is involved. And nobody volunteered. Was just giving somebody another chance to volunteer. I recommend we precede with creating 0.4.3. If a JavaScript coder can help with a re-write, then can discuss if it can be done in time for 2.2... I thought easier to start over and use a good web framework and portlet 2.0 was the conclusion. It was my impression that was a broader admin console discussion/ conclusion, not specific to the debug views... --kevan
branches/2.1 update
All, I started thinking about updating branches/2.1 to use the new 6.0.20 Tomcat that we're building. This would include updating genesis version, and probably a few additional changes. I'd like to keep changes to a minimum. However, think it would be good to use the new Tomcat generation technique. Anybody have problems with this? --kevan
[BUILD] trunk: Failed for Revision: 794340
Geronimo Revision: 794340 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 41 minutes 53 seconds
[INFO] Finished at: Wed Jul 15 15:46:38 EDT 2009
[INFO] Final Memory: 403M/1015M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/logs-1500-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/logs-1500-jetty/
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:48.784
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/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:15.244)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:36.387)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:41.147)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.623)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:23.586)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:21.808) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:12.342)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:50.906)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:57.631)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.027)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:35.350)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:33.905)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:35.733)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.791)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:01.880)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:45.619)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.764)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:55.213)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:50.797)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.897)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.990)
[INFO] web-testsuite/test-jetty RUNNING
[INFO] web-testsuite/test-jetty SUCCESS (0:00:25.369)
[INFO] web
Re: branches/2.1 update
+1 to a 2.1.5 release with Tomcat 6.0.20, which contains several security fixes. 0 for moving to Genesis 2.0, since we have yet to publish a server release with it -Donald Kevan Miller wrote: All, I started thinking about updating branches/2.1 to use the new 6.0.20 Tomcat that we're building. This would include updating genesis version, and probably a few additional changes. I'd like to keep changes to a minimum. However, think it would be good to use the new Tomcat generation technique. Anybody have problems with this? --kevan
Re: branches/2.1 update
On Jul 15, 2009, at 4:59 PM, Donald Woods wrote: +1 to a 2.1.5 release with Tomcat 6.0.20, which contains several security fixes. 0 for moving to Genesis 2.0, since we have yet to publish a server release with it Ya. I was thinking that we might want it for new Nexus repository setup. I might not have been thinking too clearly... --kevan
Re: Which dojo?
On Jul 15, 2009, at 11:12 AM, David Jencks wrote: On Jul 15, 2009, at 6:27 AM, Rex Wang wrote: tried it. 1. svn co https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3 mvn clean install success! 2. modify the plugins/dojo-legacy stuff the patch in attachment shows the modification. build successfully 3. I did not build the entire server, but just remove the old one, and install the new one. I believe only the debug-views portlets use this legacy dojo, because when I stop the dojo-legacy-tomcat plugin, only the debugviews-console-tomcat web project stopped autoly. and I also searched all the jsps underneath plugins folder in the server build tree, only show the ones from debugviews holding reference to / dojo/0.4/dojo.js results: Unfortunately, the debugviews portlet don't display corretly... I make some screen shot. Shall we open a jira for this so that I can upload them, which apparently shows dojo not work correctly? Or we could try to fix them :-) I looked at the two war files and they are different and I wonder what we actually use. old war (geronimo-dojo-legacy): -rw-r--r--151841 15-May-2007 02:11:02 dojo.js -rw-r--r--326567 15-May-2007 02:11:04 dojo.js.uncompressed.js -rw-r--r-- 1170 15-May-2007 02:06:02 flash6_gateway.swf -rw-r--r-- 2364 15-May-2007 02:06:02 iframe_history.html -rw-r--r-- 11346 15-May-2007 02:06:02 LICENSE -rw-r--r-- 13133 14-Jul-2009 15:01:02 META-INF/LICENSE -rw-r--r-- 587 14-Jul-2009 15:01:02 META-INF/NOTICE -rw-r--r-- 1609 15-May-2007 02:11:32 src/a11y.js .. everything else is under src/ new war (geronimo-dojo-0.4.3): just the contents of src from geronimo-dojo-legacy. So what do we actually use here? if its just dojo.js we can shrink it by leaving out the uncompressed.js and all the little files. If its just the little files under src we can use the new war and change the references to leave out the src/ bit. Maybe I can come up with an alternate profile to build a war with just dojo.js in it?? My latest theory is that the only file we use is dojo.js. My other theory here is that if we can legally have the dojo zip file in an svn repo then we can just as well have the dojo.js text file in our svn repo as a source file. So I modified the externals project to just include this file, from src/main/webapp. I also fixed the groupId. Could you try out this revised version? thanks david jencks wishing I understood javascript delivery even a little bit... david jencks HTH Rex. 2009/7/15 Rex Wang rwo...@gmail.com I'd like to try it :-) -Rex 2009/7/15 David Jencks david_jen...@yahoo.com Jay -- many thanks for trying out the patch and committing it. I think the last artifact in our svn repo is the dojo 0.4.3. I can't find it released anywhere but the source code is in a handy svn repo. I cooked up a modification of our war-packaging for it that uses the maven scm plugin to check out the source so it can be packaged easily. I wonder if someone could try this out and see if it works? -- check out new war project and build it svn co https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3 cd geronimo-dojo-0.4.3 mvn clean install -- modify the plugins/dojo-legacy stuff so that geronimo-dojo-legacy is not built the dojo-legacy-jetty and dojo-legacy-tomcat plugins use the geronimo-dojo-0.4.3-1.0-SNAPSHOT war file instead of the geronimo- dojo-legacy war. -- build the server and see if the parts that use the legacy dojo still work (debug views??? I'm not sure) many thanks david jencks On Jul 10, 2009, at 6:58 AM, Kevan Miller wrote: On Jul 9, 2009, at 5:59 PM, David Jencks wrote: On Jul 9, 2009, at 2:44 PM, Jay D. McHugh wrote: Hey David, I'm starting to take a look at it today. They have a 1.3.1 version out - any objections to me switching the patch to use it? Not at all -- I just thought I'd start small since usually I change 18 things at once and then can't tell what change broke what feature :-) I think kevan mentioned offline he might take a look also. I think I've been running locally with this patch for a couple weeks and haven't seen any admin console problems, but that doesn't mean much one way or another. I built with the patch and ran testsuite on Jetty. Everything looked good to me (except for a corba-testsuite test that hung). Jay, If you can test with the latest Dojo version and things look good to you, I'd say go ahead and apply the updates. --kevan dojo-legacy.patch
Re: Apache Con US '09 Geronimo Track
I think the ease of use character of Geronimo is better to be worded in the general description. The convenient admin console is definitely a bright spot compared to other open source java application servers. -- View this message in context: http://www.nabble.com/Apache-Con-US-%2709-Geronimo-Track-tp24470102s134p24509217.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: Which dojo?
I don't think only including the dojo.js is OK.. I might make you confusing on the reference to dojo/0.4/dojo.js stated above, and that ref can be saw as a sign which represents the project(debug-view) depends on the dojo-legacy project, which is not saying the jsps only need the dojo.js. eg: script type=text/javascript dojo.require(dojo.lang.*); dojo.require(dojo.widget.*); // Pane includes dojo.require(dojo.widget.ContentPane); dojo.require(dojo.widget.LayoutContainer); // Before: LayoutPane dojo.require(dojo.widget.SplitContainer); // Before: SplitPane // Tree includes dojo.require(dojo.widget.Tree); dojo.require(dojo.widget.TreeBasicController); dojo.require(dojo.widget.TreeContextMenu); dojo.require(dojo.widget.TreeSelector); // Tab includes dojo.require(dojo.widget.TabContainer); // Etc includes dojo.require(dojo.widget.SortableTable); dojo.require(dojo.widget.ComboBox); dojo.require(dojo.widget.Tooltip); dojo.require(dojo.widget.validate); // Includes Dojo source for debugging // dojo.hostenv.writeIncludes(); /script that says it needs the files in src folder. -Rex 2009/7/16 David Jencks david_jen...@yahoo.com On Jul 15, 2009, at 11:12 AM, David Jencks wrote: On Jul 15, 2009, at 6:27 AM, Rex Wang wrote: tried it. 1. svn co https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3 mvn clean install success! 2. modify the plugins/dojo-legacy stuff the patch in attachment shows the modification. build successfully 3. I did not build the entire server, but just remove the old one, and install the new one. I believe only the debug-views portlets use this legacy dojo, because when I stop the dojo-legacy-tomcat plugin, only the debugviews-console-tomcat web project stopped autoly. and I also searched all the jsps underneath plugins folder in the server build tree, only show the ones from debugviews holding reference to /dojo/0.4/dojo.js results: Unfortunately, the debugviews portlet don't display corretly... I make some screen shot. Shall we open a jira for this so that I can upload them, which apparently shows dojo not work correctly? Or we could try to fix them :-) I looked at the two war files and they are different and I wonder what we actually use. old war (geronimo-dojo-legacy): -rw-r--r--151841 15-May-2007 02:11:02 dojo.js -rw-r--r--326567 15-May-2007 02:11:04 dojo.js.uncompressed.js -rw-r--r-- 1170 15-May-2007 02:06:02 flash6_gateway.swf -rw-r--r-- 2364 15-May-2007 02:06:02 iframe_history.html -rw-r--r-- 11346 15-May-2007 02:06:02 LICENSE -rw-r--r-- 13133 14-Jul-2009 15:01:02 META-INF/LICENSE -rw-r--r-- 587 14-Jul-2009 15:01:02 META-INF/NOTICE -rw-r--r-- 1609 15-May-2007 02:11:32 src/a11y.js .. everything else is under src/ new war (geronimo-dojo-0.4.3): just the contents of src from geronimo-dojo-legacy. So what do we actually use here? if its just dojo.js we can shrink it by leaving out the uncompressed.js and all the little files. If its just the little files under src we can use the new war and change the references to leave out the src/ bit. Maybe I can come up with an alternate profile to build a war with just dojo.js in it?? My latest theory is that the only file we use is dojo.js. My other theory here is that if we can legally have the dojo zip file in an svn repo then we can just as well have the dojo.js text file in our svn repo as a source file. So I modified the externals project to just include this file, from src/main/webapp. I also fixed the groupId. Could you try out this revised version? thanks david jencks wishing I understood javascript delivery even a little bit... david jencks HTH Rex. 2009/7/15 Rex Wang rwo...@gmail.com I'd like to try it :-) -Rex 2009/7/15 David Jencks david_jen...@yahoo.com Jay -- many thanks for trying out the patch and committing it. I think the last artifact in our svn repo is the dojo 0.4.3. I can't find it released anywhere but the source code is in a handy svn repo. I cooked up a modification of our war-packaging for it that uses the maven scm plugin to check out the source so it can be packaged easily. I wonder if someone could try this out and see if it works? -- check out new war project and build it svn co https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3 cd geronimo-dojo-0.4.3 mvn clean install -- modify the plugins/dojo-legacy stuff so that geronimo-dojo-legacy is not built the dojo-legacy-jetty and dojo-legacy-tomcat plugins use the geronimo-dojo-0.4.3-1.0-SNAPSHOT war file instead of the geronimo-dojo-legacy war. -- build the server and see if the parts that use the legacy dojo still work (debug views??? I'm not sure) many
Re: Which dojo?
I think the main reason why the new war has the different structure with the
old one is:
in the pom.xml of ext\trunk\geronimo-dojo-0.4.3, only check out the files in
src to target/resource
execution
idcheckout/id
phasegenerate-resources/phase
goals
goalcheckout/goal
/goals
configuration
checkoutDirectory${project.basedir}/target/resources/checkoutDirectory
connectionUrlscm:svn:
http://svn.dojotoolkit.org/src/tags/release-0.4.3/*src/*/connectionUrl
/configuration
/execution
I just tried scm:svn:http://svn.dojotoolkit.org/src/tags/release-0.4.3/;,
and the JMX and LDAP portlet seems working correctly, but the other three
still have some problems to show the tree.
-Rex
2009/7/16 David Jencks david_jen...@yahoo.com
On Jul 15, 2009, at 6:27 AM, Rex Wang wrote:
tried it.
1.
svn co
https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3
mvn clean install
success!
2.
modify the plugins/dojo-legacy stuff
the patch in attachment shows the modification.
build successfully
3.
I did not build the entire server, but just remove the old one, and install
the new one.
I believe only the debug-views portlets use this legacy dojo, because when
I stop the dojo-legacy-tomcat plugin, only the debugviews-console-tomcat web
project stopped autoly. and I also searched all the jsps underneath plugins
folder in the server build tree, only show the ones from debugviews holding
reference to /dojo/0.4/dojo.js
results:
Unfortunately, the debugviews portlet don't display corretly...
I make some screen shot. Shall we open a jira for this so that I can upload
them, which apparently shows dojo not work correctly?
Or we could try to fix them :-)
I looked at the two war files and they are different and I wonder what we
actually use.
old war (geronimo-dojo-legacy):
-rw-r--r--151841 15-May-2007 02:11:02 dojo.js
-rw-r--r--326567 15-May-2007 02:11:04 dojo.js.uncompressed.js
-rw-r--r-- 1170 15-May-2007 02:06:02 flash6_gateway.swf
-rw-r--r-- 2364 15-May-2007 02:06:02 iframe_history.html
-rw-r--r-- 11346 15-May-2007 02:06:02 LICENSE
-rw-r--r-- 13133 14-Jul-2009 15:01:02 META-INF/LICENSE
-rw-r--r-- 587 14-Jul-2009 15:01:02 META-INF/NOTICE
-rw-r--r-- 1609 15-May-2007 02:11:32 src/a11y.js
..
everything else is under src/
new war (geronimo-dojo-0.4.3):
just the contents of src from geronimo-dojo-legacy.
So what do we actually use here? if its just dojo.js we can shrink it by
leaving out the uncompressed.js and all the little files. If its just the
little files under src we can use the new war and change the references to
leave out the src/ bit. Maybe I can come up with an alternate profile to
build a war with just dojo.js in it??
wishing I understood javascript delivery even a little bit...
david jencks
HTH
Rex.
2009/7/15 Rex Wang rwo...@gmail.com
I'd like to try it :-)
-Rex
2009/7/15 David Jencks david_jen...@yahoo.com
Jay -- many thanks for trying out the patch and committing it.
I think the last artifact in our svn repo is the dojo 0.4.3. I can't
find it released anywhere but the source code is in a handy svn repo. I
cooked up a modification of our war-packaging for it that uses the maven scm
plugin to check out the source so it can be packaged easily. I wonder if
someone could try this out and see if it works?
-- check out new war project and build it
svn co
https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3
cd geronimo-dojo-0.4.3
mvn clean install
-- modify the plugins/dojo-legacy stuff so that
geronimo-dojo-legacy is not built
the dojo-legacy-jetty and dojo-legacy-tomcat plugins use the
geronimo-dojo-0.4.3-1.0-SNAPSHOT war file instead of the
geronimo-dojo-legacy war.
-- build the server and see if the parts that use the legacy dojo still
work (debug views??? I'm not sure)
many thanks
david jencks
On Jul 10, 2009, at 6:58 AM, Kevan Miller wrote:
On Jul 9, 2009, at 5:59 PM, David Jencks wrote:
On Jul 9, 2009, at 2:44 PM, Jay D. McHugh wrote:
Hey David,
I'm starting to take a look at it today.
They have a 1.3.1 version out - any objections to me switching the
patch
to use it?
Not at all -- I just thought I'd start small since usually I change 18
things at once and then can't tell what change broke what feature :-)
I think kevan mentioned offline he might take a look also. I think
I've been running locally with this patch for a couple weeks and haven't
seen any admin console problems, but that doesn't mean much one way or
another.
I built with the patch and ran testsuite on Jetty. Everything looked
good to me (except for a corba-testsuite test that
[jira] Resolved: (GERONIMO-4589) Does not echo the command after expection occur in command line deploy.sh
[ https://issues.apache.org/jira/browse/GERONIMO-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-4589. Resolution: Fixed Commit to trunk At revision: 794506, and 2.1.5-SNAPSHOT At revision: 794507. Thanks for the patch, Han Hong Fang ! Does not echo the command after expection occur in command line deploy.sh - Key: GERONIMO-4589 URL: https://issues.apache.org/jira/browse/GERONIMO-4589 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.4 Environment: This problem is reproduced on following platforms: - Redhat 5.2 - AIX 6.1 - Susu Linux Enterprise Server 10 - Ubuntu 8 Reporter: Han Hong Fang Assignee: Han Hong Fang Attachments: GERONIMO-4589.patch Steps to reproduce this problem: 1. start Geronimo server 2. deploy a sample web app from command line using: ./deploy.sh deploy $sample_home/cviewer-2.1.1.2.war, and it can be installed and started successfully, and its module id is com.ibm.wasce.samples/cviewer/2.1.1.2/car; 3. Try to stop the module from command line with wrong module id: ./deploy.sh stop com.ibm.wasce.samples/cviewer, then the following exception occurs Using GERONIMO_HOME: /home/jeff/IBM/Framework-1.0_online_J2EE_deployer Using GERONIMO_TMPDIR: var/temp Using JRE_HOME:/opt/ibm/java-i386-60/jre Exception in thread main java.lang.IllegalArgumentException: id must be in the form [groupId]/[artifactId]/[version]/[type] : com.ibm.wasce.samples/cviewer/2.1.1.2 at java.lang.Throwable.init(Throwable.java:67) at org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:59) at org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:51) at org.apache.geronimo.deployment.plugin.ConfigIDExtractor.identifyTargetModuleIDs(ConfigIDExtractor.java:193) at org.apache.geronimo.deployment.cli.CommandStart.execute(CommandStart.java:57) at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:164) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45) at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67) at org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31) The problem is after this exception, the terminal will no echo any command you type. e.g,. if you type ls, you can not see ls being ehcoed in terminal, but if you click enter, you can see the command still works. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4718) Keystores portlet: Once unlocked for availability, keystore can not be locked
[ https://issues.apache.org/jira/browse/GERONIMO-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731784#action_12731784 ] Han Hong Fang commented on GERONIMO-4718: - Hi, I tried with G2.2 build 20090714, and can not reproduce this problem. The following scenarioes are tried with a new created keystore. Scenario 1 step1. unlock keystore availability - successfully step2. lock keystore availability - successfully Scenario 2 step1. unlock keystore availability - successfully step2. lock/unlock keystore editable - successfully Could you let us know the detail steps to reproduce this problem? Thanks! Janet Keystores portlet: Once unlocked for availability, keystore can not be locked - Key: GERONIMO-4718 URL: https://issues.apache.org/jira/browse/GERONIMO-4718 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.4 Reporter: Vamsavardhana Reddy Fix For: 2.1.5 Attempting to lock the keystore for availability is displaying the following message in the server console. 2009-06-29 08:23:07,265 ERROR [MultiPagePortlet] Unrecognized portlet action 'lockKeystore' -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4747) a {0} did not get replaced in the last portlet of console --- Apache HTTP
a {0} did not get replaced in the last portlet of console --- Apache HTTP
--
Key: GERONIMO-4747
URL: https://issues.apache.org/jira/browse/GERONIMO-4747
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: console
Affects Versions: 2.1.5, 2.2
Environment: Windows XP + Sun JDK 1.6
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor
After resolving https://issues.apache.org/jira/browse/GERONIMO-4733
You could recreate this JIRA by :
1, launch server console
2, click Server-- Apache HTTP
3, Click get started button, click next button in next page.
4, click finish button to the last page.
You can see:
Step 3: Create a workers.properties file
Youve decided to save this file at {0} . Please save the following content to
that file.
{0} was supposed to be replaced with the path to workers.properties file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4747) a {0} did not get replaced in the last portlet of console --- Apache HTTP
[
https://issues.apache.org/jira/browse/GERONIMO-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-4747:
--
Attachment: G4747_B21.patch
G4747_trunk.patch
Seems like current resource bundle does not like apostrophe in the message.
a {0} did not get replaced in the last portlet of console --- Apache HTTP
--
Key: GERONIMO-4747
URL: https://issues.apache.org/jira/browse/GERONIMO-4747
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.1.5, 2.2
Environment: Windows XP + Sun JDK 1.6
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor
Attachments: G4747_B21.patch, G4747_trunk.patch
After resolving https://issues.apache.org/jira/browse/GERONIMO-4733
You could recreate this JIRA by :
1, launch server console
2, click Server-- Apache HTTP
3, Click get started button, click next button in next page.
4, click finish button to the last page.
You can see:
Step 3: Create a workers.properties file
Youve decided to save this file at {0} . Please save the following content to
that file.
{0} was supposed to be replaced with the path to workers.properties file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Do we want to apply genesis 2.0 resource filtering best practice ?
I noticed there's a maven resource best practice defined in
genesis-default-flava-2.0.pom.
1, Put normal resource under : ${project.basedir}/ src/main/resources
2, Put the resource that needs filtering under: ${project.basedir}/
src/main/filtered-resources
At the same time, many projects in Geronimo does not follow this practice.
A JIRA was opened for this :
https://issues.apache.org/jira/browse/GERONIMO-4737
If no objection, I'm going to use GERONIMO-4737 to fix this kind of problems
in current code base. Any comments ?
--
Shawn
[jira] Updated: (GERONIMO-4747) a {0} did not get replaced in the last portlet of console --- Apache HTTP
[
https://issues.apache.org/jira/browse/GERONIMO-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-4747:
--
Patch Info: [Patch Available]
a {0} did not get replaced in the last portlet of console --- Apache HTTP
--
Key: GERONIMO-4747
URL: https://issues.apache.org/jira/browse/GERONIMO-4747
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.1.5, 2.2
Environment: Windows XP + Sun JDK 1.6
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor
Attachments: G4747_B21.patch, G4747_trunk.patch
After resolving https://issues.apache.org/jira/browse/GERONIMO-4733
You could recreate this JIRA by :
1, launch server console
2, click Server-- Apache HTTP
3, Click get started button, click next button in next page.
4, click finish button to the last page.
You can see:
Step 3: Create a workers.properties file
Youve decided to save this file at {0} . Please save the following content to
that file.
{0} was supposed to be replaced with the path to workers.properties file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
