[jira] Created: (GERONIMO-4732) click monitoring and delete the server localhost and there is an Error rendering portlet.

2009-07-09 Thread liangkun (JIRA)
click monitoring and delete the server localhost and there is an Error 
rendering portlet.
-

 Key: GERONIMO-4732
 URL: https://issues.apache.org/jira/browse/GERONIMO-4732
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: monitoring
Affects Versions: 2.2
 Environment: windows xp sp2 32bit
JRE 1.6
Reporter: liangkun
Priority: Minor
 Fix For: 1.1.2


steps:
1.click the porlet and add a server localhost.
2.Add two Graphs:one is JVM Heap Size current,another is JVM Heap Size max.
3.view the graphs and they run well.
4 Delete the server and there is an error:rendering portlet.
Error rendering portlet.
java.lang.NullPointerException
at 
jsp.WEB_002dINF.view.monitoringNormal_jsp._jspService(monitoringNormal_jsp.java:900)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at 
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
at 
org.apache.geronimo.monitoring.console.MonitoringPortlet.normalView(MonitoringPortlet.java:455)
at 
org.apache.geronimo.monitoring.console.MonitoringPortlet.doView(MonitoringPortlet.java:341)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
at 
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at 
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
at 
org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
at 
org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:172)
at 
org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
at 
jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at 
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
at 
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
at 
jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at 

[jira] Updated: (GERONIMO-4560) Run the activemq web console on geronimo

2009-07-09 Thread Forrest Xia (JIRA)

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

Forrest Xia updated GERONIMO-4560:
--

Attachment: GERONIMO-4560-typo.patch

Typo errors in activemq-webconsole-jetty and activemq-webconsole-tomcat:
1. webconsole.type=inVM -- webconsole.type=invm
2. context-root/ 
/Users/david/geronimo/svn/geronimo/server/trunk/plugins/activemq/activemq-webconsole-tomcat/src/main/history/dependencies.xml-console/context-root
-- context-root/activemq-console/context-root

Otherwise, the two plugins won't work.

 Run the activemq web console on geronimo
 

 Key: GERONIMO-4560
 URL: https://issues.apache.org/jira/browse/GERONIMO-4560
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: ActiveMQ
Affects Versions: 2.2
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 2.2

 Attachments: GERONIMO-4560-typo.patch


 Activemq has a nice little web console that lets you browse queues and topics 
 and try sending messages.  We should package this as a geronimo plugin.

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



[jira] Commented: (GERONIMO-4678) Initial Japanese translation

2009-07-09 Thread Kan Ogawa (JIRA)

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

Kan Ogawa commented on GERONIMO-4678:
-

Thank you so much, Jarek!

Both V2.1 and V2.2 translation patches are *NOT* fully same.
Now I'm writing the different patch for V2.2.

 Initial Japanese translation
 

 Key: GERONIMO-4678
 URL: https://issues.apache.org/jira/browse/GERONIMO-4678
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: console
Reporter: Kan Ogawa
Assignee: Jarek Gawor
Priority: Minor
 Fix For: 2.1.5, 2.2

 Attachments: geronimo-v21_i18n-ja_G4485-G4532_v1.patch




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



[jira] Reopened: (GERONIMO-4560) Run the activemq web console on geronimo

2009-07-09 Thread Forrest Xia (JIRA)

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

Forrest Xia reopened GERONIMO-4560:
---


Small typo errors there, so reopen it. Attached the patch, please check and 
apply.

 Run the activemq web console on geronimo
 

 Key: GERONIMO-4560
 URL: https://issues.apache.org/jira/browse/GERONIMO-4560
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: ActiveMQ
Affects Versions: 2.2
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 2.2

 Attachments: GERONIMO-4560-typo.patch


 Activemq has a nice little web console that lets you browse queues and topics 
 and try sending messages.  We should package this as a geronimo plugin.

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

2009-07-09 Thread gawor
Geronimo Revision: 792407 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/build-0300.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 42 minutes 58 seconds
[INFO] Finished at: Thu Jul 09 03:47:20 EDT 2009
[INFO] Final Memory: 432M/972M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/logs-0300-tomcat/
 
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/logs-0300-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.620
[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.294) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:36.637) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:40.391) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.361) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:25.599) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:21.795) Java 
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:13.755) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:55.559) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:04.100) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:48.335) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:33.923) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.254) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:36.927) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.950) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:01.123) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.139) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:32.286) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:50.234) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:51.003) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.196) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.879) 
[INFO] web-testsuite/test-jetty   RUNNING
[INFO] web-testsuite/test-jetty   SUCCESS (0:00:24.450

[jira] Assigned: (GERONIMO-4732) click monitoring and delete the server localhost and there is an Error rendering portlet.

2009-07-09 Thread viola.lu (JIRA)

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

viola.lu reassigned GERONIMO-4732:
--

Assignee: viola.lu

 click monitoring and delete the server localhost and there is an Error 
 rendering portlet.
 -

 Key: GERONIMO-4732
 URL: https://issues.apache.org/jira/browse/GERONIMO-4732
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.2
 Environment: windows xp sp2 32bit
 JRE 1.6
Reporter: liangkun
Assignee: viola.lu
Priority: Minor
 Fix For: 1.1.2


 steps:
 1.click the porlet and add a server localhost.
 2.Add two Graphs:one is JVM Heap Size current,another is JVM Heap Size max.
 3.view the graphs and they run well.
 4 Delete the server and there is an error:rendering portlet.
 Error rendering portlet.
 java.lang.NullPointerException
   at 
 jsp.WEB_002dINF.view.monitoringNormal_jsp._jspService(monitoringNormal_jsp.java:900)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.normalView(MonitoringPortlet.java:455)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.doView(MonitoringPortlet.java:341)
   at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
   at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
   at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
   at 
 org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
   at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
   at 
 org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
   at 
 org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:172)
   at 
 org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
   at 
 jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
   at 
 jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
   at 
 jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

[jira] Created: (GERONIMO-4733) Unable to starting to configure Apache mod_jk

2009-07-09 Thread Shiny Cheng (JIRA)
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)
Affects Versions: 2.2
 Environment: Windows XP SP2, IE6.0
Reporter: Shiny Cheng


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-4732) click monitoring and delete the server localhost and there is an Error rendering portlet.

2009-07-09 Thread Rex Wang (JIRA)

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

Rex Wang updated GERONIMO-4732:
---

 Priority: Major  (was: Minor)
Fix Version/s: (was: 1.1.2)
   2.2

 click monitoring and delete the server localhost and there is an Error 
 rendering portlet.
 -

 Key: GERONIMO-4732
 URL: https://issues.apache.org/jira/browse/GERONIMO-4732
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.2
 Environment: windows xp sp2 32bit
 JRE 1.6
Reporter: liangkun
Assignee: viola.lu
 Fix For: 2.2


 steps:
 1.click the porlet and add a server localhost.
 2.Add two Graphs:one is JVM Heap Size current,another is JVM Heap Size max.
 3.view the graphs and they run well.
 4 Delete the server and there is an error:rendering portlet.
 Error rendering portlet.
 java.lang.NullPointerException
   at 
 jsp.WEB_002dINF.view.monitoringNormal_jsp._jspService(monitoringNormal_jsp.java:900)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.normalView(MonitoringPortlet.java:455)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.doView(MonitoringPortlet.java:341)
   at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
   at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
   at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
   at 
 org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
   at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
   at 
 org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
   at 
 org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:172)
   at 
 org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
   at 
 jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
   at 
 jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
   at 
 jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 

Re: Duplicate clustername value sets in config-subsititions file

2009-07-09 Thread Gianny Damour

I would say the other way around. A cluster is a type of farm.

I see a farm as a set of independent instances. I see a cluster as a  
set of collaborating instances. You can deploy a non clustered  
application to a farm whereby you do not have resilience in case of  
service failure. And you can deploy a clustered application to a farm  
to increase service resiliency if necessary.


Thanks,
Gianny

On 09/07/2009, at 12:49 PM, Rex Wang wrote:


well, Gianny, is a server farm not a type of cluster?

-Rex

2009/7/8 Gianny Damour gianny.dam...@optusnet.com.au
Hi,

It seems to me that farmName would be better than  
farmingClusterName as there is a clear distinction between a farm  
and a cluster.


Thanks,
Gianny


On 06/07/2009, at 7:47 PM, chi runhua wrote:

Hi all,

I just noticed there are 2 pairs of clusterName=CLUSTER_NAME in  
config-substitions.properties.  My understanding of them is one for  
WADI clustering and another for farming.


Can we using different keywords to identify them? ie.   
farmingClusterName and WADIClusterName or sth. like that.



Jeff  C






Re: Problem when deploy CXF WebService (Service resource injection failed)

2009-07-09 Thread chi runhua
I notified CXF community about doc problem, see if they can find someone to
update the tutorial.

http://www.nabble.com/Problem-in-writing-a-service-with-spring-tutorial-td24387574.html

Jeff C

On Tue, Jul 7, 2009 at 2:50 AM, Westhveg westhstud...@gmail.com wrote:


 Jarek,

 Finally, it works. I've followed the second way.

 I have to do this:

  · Remove the spring listener from web.xml
  · Keep the spring contextConfigLocation in web.xml
  · Keep CXF Servlet but calling my interface insted of
 'org.apache.cxf.transport.servlet.CXFServlet'.

 Thanks a lot for your patience Jarek. You are my savior!

 And about this tutorial:

 http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html

 Is out of date. It follows the first way and neither speak nothing about
 filters in geronimo-web.xml nor
 '-Dorg.apache.geronimo.jaxws.builder.useSimpleFinder=true' system property.


 Where can I post my eclipse project with the working example?


 See u!

 Westhveg


 Jarek Gawor-2 wrote:
 
  Westhveg,
 
  Let's back up a little. You have two options for deploying your web
  service:
 
  1) Deploy your web application WITH all cxf and spring jars but you
  MUST: a) start the server with
  -Dorg.apache.geronimo.jaxws.builder.useSimpleFinder=true AND b)
  specify a bunch of filters in geronimo-web.xml.
 
  or
 
  2) Deploy your web application WITHOUT any cxf AND spring jars and
  without CXFServlet in the web.xml. In this case your web application
  should only contain the web service class and any other jars/classes
  that the web service needs. The war file should be much smaller. Don't
  set org.apache.geronimo.jaxws.builder.useSimpleFinder property or any
  filters in geronimo-web.xml.
 
  With option 2) you are relying on the app server to deploy your web
  service. The app server will use its own web service engine to deploy
  and manage your web service. That's why you don't need all these
  spring or cxf jars or the cxf servlet or cxf configuration files. With
  option 1) you are not relying on the app server to deploy and manage
  your web service. The web application you are deploying has it own web
  services engine which will deploy and manage the web service. And to
  prevent conflicts between the web app web service engine and the app
  server web service engine you need to set those filters and that
  property.
 
  Jarek
 
  On Mon, Jul 6, 2009 at 5:13 AM, Westhvegwesthstud...@gmail.com wrote:
 
  Can anyone help me, please?
 
 
  Thanks,
 
  Westhveg
 
 
  Westhveg wrote:
 
  And if I try to test the webservice developing this spring client:
 
  ?xml version=1.0 encoding=UTF-8?
  beans xmlns=http://www.springframework.org/schema/beans;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xmlns:jaxws=http://cxf.apache.org/jaxws;
 xsi:schemaLocation=http://www.springframework.org/schema/beans
 
  http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
 http://cxf.apache.org/jaxws
 http://cxf.apache.org/schemas/jaxws.xsd;
   !--
  If I uncomment this, I get the same exception. But if I leave it
  commented, I must import FastInfoset.jar library.
 
  import resource=classpath:META-INF/cxf/cxf.xml /
  import resource=classpath:META-INF/cxf/cxf-extension-soap.xml /
  import resource=classpath:META-INF/cxf/cxf-servlet.xml /
  --
jaxws:client id=helloWordClient
  serviceClass=com.test.HelloWorld
  address=http://localhost:8080/helloWorld; /
  /beans
 
 
 
  30-jun-2009 23:52:33 org.apache.cxf.bus.spring.BusApplicationContext
  getConfigResources
  INFO: No cxf.xml configuration file detected, relying on defaults.
  30-jun-2009 23:52:34
  org.apache.cxf.service.factory.ReflectionServiceFactoryBean
  buildServiceFromClass
  INFO: Creating Service 
  {http://test.com/}HelloWorldServicehttp://test.com/%7DHelloWorldServicefrom
   class
  com.test.HelloWorld
  30-jun-2009 23:52:34 org.apache.cxf.phase.PhaseInterceptorChain
  doIntercept
  INFO: Interceptor has thrown exception, unwinding now
  org.apache.cxf.interceptor.Fault: Could not send Message.
at
 
 org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
at
 
 org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:471)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:301)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:253)
at
  org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
  org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:121)
at $Proxy44.postMessage(Unknown Source)
at com.test.TestWsClient.main(TestWsClient.java:15)
  Caused by: java.io.IOException: Not Found
at
 
 

[jira] Assigned: (GERONIMO-4025) Accessibility issues: No caption tag or summary property, no column and row scope property for data tables in admin console

2009-07-09 Thread Donald Woods (JIRA)

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

Donald Woods reassigned GERONIMO-4025:
--

Assignee: Forrest Xia  (was: Donald Woods)

 Accessibility issues: No caption tag or summary property, no column and row 
 scope property for data tables in admin console
 ---

 Key: GERONIMO-4025
 URL: https://issues.apache.org/jira/browse/GERONIMO-4025
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.1.1, 2.1.2, 2.1.x, 2.2
 Environment: Windows XP SP2, IE 6.0
 JAWS 8.0
Reporter: Forrest Xia
Assignee: Forrest Xia
 Fix For: 2.2

 Attachments: GERONIMO-4025-activemq-and-monitoring.patch, 
 GERONIMO-4025-configmanager-and-infomanager.patch, 
 GERONIMO-4025-console.patch, GERONIMO-4025-DB-Properties_zh.patch, 
 GERONIMO-4025-DB-style.patch, GERONIMO-4025-DB.patch


 To enable accessibility feature for data tables in the admin console, these 
 techniques should be used:
 1. Add caption tag or summary property to data table, for example
 table border=1 
 captionServer information/caption
 OR
 table border=1 summary=Server information
 2. Add scope property to column and row headers, for example
 tr
 th scope=colProperty name/th
 th scope=colProperty value/th
 /tr
 tr
 tdGeronimo Version/td
 td2.1.1/td
 /tr
 The data tables on these pages shall be improved:
 Server-Information
 Server-Java System Info
 server-Web Server
 Server-Thread Pools
 Server-JMS Server
 Server-Monitoring
 Services-Database Pools
 Services-JMS Resources
 Applications-Web App WARs
 Applications-System modules
 Applications-Application EARs
 Applications-EJB JARs
 Applications-J2EE Connectors
 Applications-App Clients
 Security-Users and Groups
 Security-Keystores
 Security-Security Realms
 Embedded DB-DB Info
 Embedded DB-DB Manager

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

2009-07-09 Thread gawor
Geronimo Revision: 792521 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/build-0900.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 42 minutes 20 seconds
[INFO] Finished at: Thu Jul 09 09:46:48 EDT 2009
[INFO] Final Memory: 403M/1014M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/logs-0900-tomcat/
 
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/logs-0900-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:49.508
[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.706) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:35.180) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:40.269) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.698) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:23.855) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:21.522) Java 
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:13.898) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:54.284) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:05.683) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:46.807) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:34.729) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:35.364) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:36.253) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.261) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.215) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:45.640) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.008) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:49.728) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:50.492) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.851) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.996) 
[INFO] web-testsuite/test-jetty   RUNNING
[INFO] web-testsuite/test-jetty   SUCCESS (0:00:25.498

[jira] Resolved: (GERONIMO-4560) Run the activemq web console on geronimo

2009-07-09 Thread Jarek Gawor (JIRA)

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

Jarek Gawor resolved GERONIMO-4560.
---

Resolution: Fixed

Committed the patch to trunk (revision 792566). Thanks for catching this  the 
patch!



 Run the activemq web console on geronimo
 

 Key: GERONIMO-4560
 URL: https://issues.apache.org/jira/browse/GERONIMO-4560
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: ActiveMQ
Affects Versions: 2.2
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 2.2

 Attachments: GERONIMO-4560-typo.patch


 Activemq has a nice little web console that lets you browse queues and topics 
 and try sending messages.  We should package this as a geronimo plugin.

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



[jira] Commented: (GERONIMODEVTOOLS-581) GEP 2.2 can't be installed on WTP 3.1 used by Eclipse 3.5 Galileo

2009-07-09 Thread Jose M. Ordax (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12729325#action_12729325
 ] 

Jose M. Ordax commented on GERONIMODEVTOOLS-581:


When is going 2.1.5 to be delivered? I have tested right now and I still seeing 
2.1.4 which still fails... Thanks.

 GEP 2.2 can't be installed on WTP 3.1 used by Eclipse 3.5 Galileo
 -

 Key: GERONIMODEVTOOLS-581
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-581
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.2.0
Reporter: Delos Dai
Assignee: Delos Dai
 Fix For: 2.1.5, 2.2.0

 Attachments: 581.patch, 581_missingfile.patch, 581new.patch, 
 gep-trunk-788843.wep22.patch


 GEP 2.2 can't be installed on WTP 3.1, which is used by Eclipse 3.5 ,Galileo. 

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



[jira] Resolved: (GERONIMO-4729) Duplicate clusterName value sets in config-subsitious.properties

2009-07-09 Thread Jarek Gawor (JIRA)

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

Jarek Gawor resolved GERONIMO-4729.
---

   Resolution: Fixed
Fix Version/s: 2.2
   2.1.5
 Assignee: Jarek Gawor  (was: Rex Wang)

Committed the patch to trunk (revision 792581) and branches/2.1 (revision 
792608). Thanks for the patch!


 Duplicate clusterName value sets in config-subsitious.properties
 

 Key: GERONIMO-4729
 URL: https://issues.apache.org/jira/browse/GERONIMO-4729
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: Clustering
Affects Versions: 2.1.4, 2.1.5, 2.2
 Environment: Any
Reporter: Chi Runhua
Assignee: Jarek Gawor
 Fix For: 2.1.5, 2.2

 Attachments: Geronimo-4729-b21.patch, Geronimo-4729-trunk.patch


 Look into *config-subsitions.properties* file, there are 2 places to set 
 clustername as following:
 {code}
 ClusterName=DEFAULT_CLUSTER
 ...
 clusterName=CLUSTER_NAME
 ...
 {code}
 which will confuse users when they are going to set up a clustering/farming 
 environment.
 Can we improve this?
 Jeff

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

2009-07-09 Thread gawor
Geronimo Revision: 792621 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 42 minutes 52 seconds
[INFO] Finished at: Thu Jul 09 15:47:41 EDT 2009
[INFO] Final Memory: 403M/1013M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/logs-1500-tomcat/
 
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/logs-1500-jetty/
 
 
[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.532
[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.379) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:35.414) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:39.365) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.966) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:25.236) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:35.633) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:08.188) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:54.120) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:58.984) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:47.832) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:34.041) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.063) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:36.720) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.059) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:58.995) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:45.825) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:31.757) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:48.138) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:51.561) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.480) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.624) 
[INFO] web-testsuite/test-jetty

Re: Which dojo?

2009-07-09 Thread Jay D. McHugh
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?

Jay

David Jencks wrote:
 
 On Jul 1, 2009, at 10:18 PM, Rex Wang wrote:
 
 Yep, the current portlet dev is really complicated, but there will be
 a huge work to do if we decide to switch pluto to other framework like
 JSF... not sure how much for Pluto2.
 And I think we don't have enough time for the migration before G2.2
 release..
 
 I agree.  But we need to fix the private repo issue now. is anyone
 looking at my patch or my patch updated to the latest dojo release?
  Since I don't see problems I'm tempted to apply it.  Then we can try to
 figure out something for the 0.4.3 legacy dojo.
 
 thanks
 david jencks
 

 -Rex

 2009/7/2 David Jencks david_jen...@yahoo.com
 mailto:david_jen...@yahoo.com

 If we're going to rewrite bits of the portal, we should consider
 moving to pluto 2.  IIUC there are a bunch of features in portlet
 2 spec that may make our portlets simpler.  I also think we should
 investigate frameworks such as jsf or even wicket or something
 because the current portlet code is ridiculously complicated for
 what it does.  There must be a more sensible way to write a web app.

 thanks
 david jencks

 On Jul 1, 2009, at 9:41 AM, Joseph Leong wrote:

 So unfortunately what happened between Dojo 0.4.3- Mostly
 anything newer especially 1.3.1 is that they had the idea to
 classify their libraries to Dijit (Widgets) and other
 subsections.  As such, the porting effort is not small. I believe
 the debug-views portlets and such still depend on 0.4.3. At this
 point in time, my opinion would be to not try and migrate any
 0.4.3 dependent code. There has been so much change between the
 dojo versions that it would be probably simpler and cleaner to
 just rewrite these portlets.  I think it'd be a good choice to
 get rid of the old Dojo libraries once and for all as they add a
 bit to the geronimo footprint size.. not to mention there are a
 lot more features in the latest Dojo release that can probably
 accomplish what you wanted to in the older versions.

 Thanks,
 Joseph Leong

 On Wed, Jul 1, 2009 at 12:10 PM, David Jencks
 david_jen...@yahoo.com mailto:david_jen...@yahoo.com wrote:


 On Jul 1, 2009, at 1:14 AM, Ivan wrote:

 I think the one is what need, no samples and testcases are
 included. But I found 1.3.1 is released, why not use the
 newest one ?

 Newer would be better if we can get it to work.  I set this
 up a few days ago and forgot the details... I think that I
 saw some problem and wasn't sure what was causing it and
 tried changing to an earlier dojo version.  I didn't actually
 have any reason to think the problem was caused by dojo so
 very likely the more recent release should work.

 And for the legacy dojo 0.4.3, how shall we handle it ? Like
 tomcat, maitaine a our own repo ?

 Ideally I think we would migrate our code to up-to-date dojo.
  Unfortunately I have no idea how hard that would be.  Does
 anyone? If we can't, I think there is some release of some
 0.4.3 dojo, perhaps we can investigate using or repackaging
 it.   

 There's also dwr  but I think working on one dependency
 at a time will be less confusing.

 thanks
 david jencks



 2009/7/1 David Jencks david_jen...@yahoo.com
 mailto:david_jen...@yahoo.com

 In my attempt to remove our svn repo I found that dojo
 releases a dojo-war that looks pretty similar to our
 repacked dojo war.  I can make the build work with the
 substitution but I don't know enough about dojo to know
 if/what it breaks.  Is there anyone who understands our
 use of dojo well enough to take a look and see if this
 replacement is plausible?

 I recall some discussion in the distant past about not
 including all of dojo... I'm not sure if this is still a
 concern, but if the released dojo-war works and is too
 big we can use maven to come up with a smaller war.

 See https://issues.apache.org/jira/browse/GERONIMO-4723
 for my patch.

 thanks
 david jencks




 -- 
 Ivan




 


Re: Which dojo?

2009-07-09 Thread David Jencks


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.


thanks
david jencks


Jay

David Jencks wrote:


On Jul 1, 2009, at 10:18 PM, Rex Wang wrote:

Yep, the current portlet dev is really complicated, but there will  
be
a huge work to do if we decide to switch pluto to other framework  
like

JSF... not sure how much for Pluto2.
And I think we don't have enough time for the migration before G2.2
release..


I agree.  But we need to fix the private repo issue now. is  
anyone

looking at my patch or my patch updated to the latest dojo release?
Since I don't see problems I'm tempted to apply it.  Then we can  
try to

figure out something for the 0.4.3 legacy dojo.

thanks
david jencks



-Rex

2009/7/2 David Jencks david_jen...@yahoo.com
mailto:david_jen...@yahoo.com

   If we're going to rewrite bits of the portal, we should consider
   moving to pluto 2.  IIUC there are a bunch of features in portlet
   2 spec that may make our portlets simpler.  I also think we  
should

   investigate frameworks such as jsf or even wicket or something
   because the current portlet code is ridiculously complicated for
   what it does.  There must be a more sensible way to write a web  
app.


   thanks
   david jencks

   On Jul 1, 2009, at 9:41 AM, Joseph Leong wrote:


   So unfortunately what happened between Dojo 0.4.3- Mostly
   anything newer especially 1.3.1 is that they had the idea to
   classify their libraries to Dijit (Widgets) and other
   subsections.  As such, the porting effort is not small. I  
believe

   the debug-views portlets and such still depend on 0.4.3. At this
   point in time, my opinion would be to not try and migrate any
   0.4.3 dependent code. There has been so much change between the
   dojo versions that it would be probably simpler and cleaner to
   just rewrite these portlets.  I think it'd be a good choice to
   get rid of the old Dojo libraries once and for all as they add a
   bit to the geronimo footprint size.. not to mention there are a
   lot more features in the latest Dojo release that can probably
   accomplish what you wanted to in the older versions.

   Thanks,
   Joseph Leong

   On Wed, Jul 1, 2009 at 12:10 PM, David Jencks
   david_jen...@yahoo.com mailto:david_jen...@yahoo.com wrote:


   On Jul 1, 2009, at 1:14 AM, Ivan wrote:


   I think the one is what need, no samples and testcases are
   included. But I found 1.3.1 is released, why not use the
   newest one ?


   Newer would be better if we can get it to work.  I set this
   up a few days ago and forgot the details... I think that I
   saw some problem and wasn't sure what was causing it and
   tried changing to an earlier dojo version.  I didn't  
actually

   have any reason to think the problem was caused by dojo so
   very likely the more recent release should work.

   And for the legacy dojo 0.4.3, how shall we handle it ?  
Like

   tomcat, maitaine a our own repo ?


   Ideally I think we would migrate our code to up-to-date  
dojo.

Unfortunately I have no idea how hard that would be.  Does
   anyone? If we can't, I think there is some release of some
   0.4.3 dojo, perhaps we can investigate using or repackaging
   it.

   There's also dwr  but I think working on one dependency
   at a time will be less confusing.

   thanks
   david jencks




   2009/7/1 David Jencks david_jen...@yahoo.com
   mailto:david_jen...@yahoo.com

   In my attempt to remove our svn repo I found that dojo
   releases a dojo-war that looks pretty similar to our
   repacked dojo war.  I can make the build work with the
   substitution but I don't know enough about dojo to know
   if/what it breaks.  Is there anyone who understands our
   use of dojo well enough to take a look and see if this
   replacement is plausible?

   I recall some discussion in the distant past about not
   including all of dojo... I'm not sure if this is  
still a

   concern, but if the released dojo-war works and is too
   big we can use maven to come up with a smaller war.

   See https://issues.apache.org/jira/browse/GERONIMO-4723
   for my patch.

   thanks
   david jencks




   --
   Ivan










[jira] Created: (GERONIMO-4734) JACC web permissions httpMethodSpec equals method wrong

2009-07-09 Thread David Jencks (JIRA)
JACC web permissions httpMethodSpec equals method wrong
---

 Key: GERONIMO-4734
 URL: https://issues.apache.org/jira/browse/GERONIMO-4734
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: specs
Affects Versions: 2.2
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 2.2


The HTTPMethodSpec equlas method ignores the isExcluded field.

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



[jira] Commented: (GERONIMO-4732) click monitoring and delete the server localhost and there is an Error rendering portlet.

2009-07-09 Thread viola.lu (JIRA)

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

viola.lu commented on GERONIMO-4732:


which build you are using, i tested it on latest build 
009.07.08-21:08:59.720-0400, seems no problem when adding both graphs.Pls 
recheck it, thanks.

 click monitoring and delete the server localhost and there is an Error 
 rendering portlet.
 -

 Key: GERONIMO-4732
 URL: https://issues.apache.org/jira/browse/GERONIMO-4732
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.2
 Environment: windows xp sp2 32bit
 JRE 1.6
Reporter: liangkun
Assignee: viola.lu
 Fix For: 2.2


 steps:
 1.click the porlet and add a server localhost.
 2.Add two Graphs:one is JVM Heap Size current,another is JVM Heap Size max.
 3.view the graphs and they run well.
 4 Delete the server and there is an error:rendering portlet.
 Error rendering portlet.
 java.lang.NullPointerException
   at 
 jsp.WEB_002dINF.view.monitoringNormal_jsp._jspService(monitoringNormal_jsp.java:900)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.normalView(MonitoringPortlet.java:455)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.doView(MonitoringPortlet.java:341)
   at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
   at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
   at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
   at 
 org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
   at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
   at 
 org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
   at 
 org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:172)
   at 
 org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
   at 
 jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
   at 
 jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
   at 
 jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at 

[jira] Created: (GERONIMO-4735) JACC EJBMethodPermission permission collection stores data twice and is hard to understand

2009-07-09 Thread David Jencks (JIRA)
JACC EJBMethodPermission permission collection stores data twice and is hard to 
understand
--

 Key: GERONIMO-4735
 URL: https://issues.apache.org/jira/browse/GERONIMO-4735
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: specs
Affects Versions: 2.2
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 2.2


We serialize the EJBMethodPermission permission collection.  It currently 
serializes both the list of permissions and the data structure that lets it 
look up stuff quickly.  Lets just save the permissions and reconstitute the 
data structure.  Lets add serialVersionID fields too.

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



[jira] Commented: (GERONIMO-4695) ERROR import mySQL datasource from JBOSS 4

2009-07-09 Thread viola.lu (JIRA)

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

viola.lu commented on GERONIMO-4695:


can somebody apply the patch, thanks.

 ERROR import  mySQL  datasource from JBOSS 4
 

 Key: GERONIMO-4695
 URL: https://issues.apache.org/jira/browse/GERONIMO-4695
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
 Environment: OS:windows xp sp3;
 jre 1.6
Reporter: liangkun
Priority: Minor
 Attachments: GERONIMO-4695.patch


 In Geronimo,import mysql datasource from JBOSS 4, I meet the problem: can not 
 deploy the datasource.
 steps:
  Steps:
 1.Open Geronimo administrative console:http://localhost:8080/console
 2.Extract JBOSS4 and locate the MySql-ds.xml which is located in 
 JBOSS_HOME\docs\examples\jca. Copy the file to the direction 
 JBOSS_HOME\server\default\deploy.
 3.From the Geronimo Administration Console click on the Database Pools link. 
 From the Database Pools portlet click Import from JBoss 4. Browse the file 
 MySql-ds.xml and the dlick deploy.
 Problem:
 The server encountered an internal error () that prevented it from fulfilling 
 this request.
 Exception:
 javax.servlet.ServletException: javax.portlet.PortletException: Don't 
 recognize database driver com.mysql.jdbc.Driver!

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



[jira] Commented: (GERONIMO-4732) click monitoring and delete the server localhost and there is an Error rendering portlet.

2009-07-09 Thread liangkun (JIRA)

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

liangkun commented on GERONIMO-4732:


My build is 2009.07.07 and the problem is not adding both graphs but deleting 
the server before you delete the two graphs the there is an error.

 click monitoring and delete the server localhost and there is an Error 
 rendering portlet.
 -

 Key: GERONIMO-4732
 URL: https://issues.apache.org/jira/browse/GERONIMO-4732
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: monitoring
Affects Versions: 2.2
 Environment: windows xp sp2 32bit
 JRE 1.6
Reporter: liangkun
Assignee: viola.lu
 Fix For: 2.2


 steps:
 1.click the porlet and add a server localhost.
 2.Add two Graphs:one is JVM Heap Size current,another is JVM Heap Size max.
 3.view the graphs and they run well.
 4 Delete the server and there is an error:rendering portlet.
 Error rendering portlet.
 java.lang.NullPointerException
   at 
 jsp.WEB_002dINF.view.monitoringNormal_jsp._jspService(monitoringNormal_jsp.java:900)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.normalView(MonitoringPortlet.java:455)
   at 
 org.apache.geronimo.monitoring.console.MonitoringPortlet.doView(MonitoringPortlet.java:341)
   at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
   at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
   at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
   at 
 org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
   at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
   at 
 org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
   at 
 org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:172)
   at 
 org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
   at 
 jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
   at 
 org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
   at 
 jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
   at 
 jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at 

[jira] Assigned: (GERONIMO-4695) ERROR import mySQL datasource from JBOSS 4

2009-07-09 Thread Ivan (JIRA)

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

Ivan reassigned GERONIMO-4695:
--

Assignee: Ivan

 ERROR import  mySQL  datasource from JBOSS 4
 

 Key: GERONIMO-4695
 URL: https://issues.apache.org/jira/browse/GERONIMO-4695
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
 Environment: OS:windows xp sp3;
 jre 1.6
Reporter: liangkun
Assignee: Ivan
Priority: Minor
 Attachments: GERONIMO-4695.patch


 In Geronimo,import mysql datasource from JBOSS 4, I meet the problem: can not 
 deploy the datasource.
 steps:
  Steps:
 1.Open Geronimo administrative console:http://localhost:8080/console
 2.Extract JBOSS4 and locate the MySql-ds.xml which is located in 
 JBOSS_HOME\docs\examples\jca. Copy the file to the direction 
 JBOSS_HOME\server\default\deploy.
 3.From the Geronimo Administration Console click on the Database Pools link. 
 From the Database Pools portlet click Import from JBoss 4. Browse the file 
 MySql-ds.xml and the dlick deploy.
 Problem:
 The server encountered an internal error () that prevented it from fulfilling 
 this request.
 Exception:
 javax.servlet.ServletException: javax.portlet.PortletException: Don't 
 recognize database driver com.mysql.jdbc.Driver!

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



[jira] Closed: (GERONIMO-4481) GShell command jaxws/java2ws error: Syntax error, annotations are only available if source level is 5.0

2009-07-09 Thread Forrest Xia (JIRA)

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

Forrest Xia closed GERONIMO-4481.
-


Verified on build 2009.07.07-21:09:29.719-0400, it's fixed. so close it.

 GShell command jaxws/java2ws error: Syntax error, annotations are only 
 available if source level is 5.0
 ---

 Key: GERONIMO-4481
 URL: https://issues.apache.org/jira/browse/GERONIMO-4481
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: webservices
Affects Versions: 2.2
 Environment: java version 1.6.0_10
 Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
 Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
 ubuntu 8.04.1 LTS
Reporter: Forrest Xia
Assignee: Forrest Xia
Priority: Minor
 Fix For: 2.2

 Attachments: G3665FeatureValidation.jar


 Steps to recurring:
 1. start 2.2 snapshot server
 2. enter gshell prompt
 3. execute command like this:
 code
 jaxws/java2ws -wsdl -client -server -wrapperbean -ant -o test.wsdl -s 
 /home/forrestxm/temp/gshell015 -d /home/forrestxm/temp/gshell015 -classdir 
 /home/forrestxm/temp/gshell015 -cp 
 /home/forrestxm/temp/gshell015/G3665FeatureValidation.jar 
 org.apache.geronimo.test.fixver.g3665.SayHelloWebService
 /code
 then the errors say Syntax error, annotations are only available if source 
 level is 5.0. Checked cxf 2.1.3 release, there are similar problems when 
 executing a similar command.
 However, use the generated ant project to compile those generated source 
 code, it's fine.

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



[jira] Updated: (GERONIMO-4733) Unable to starting to configure Apache mod_jk

2009-07-09 Thread Shiny Cheng (JIRA)

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

Shiny Cheng updated GERONIMO-4733:
--

Fix Version/s: 2.2

 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) 
Affects Versions: 2.2
 Environment: Windows XP SP2, IE6.0
Reporter: Shiny Cheng
 Fix For: 2.2


 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.



Re: Duplicate clustername value sets in config-subsititions file

2009-07-09 Thread Rex Wang
Thanks! So IIUC, farm provide system Load balancing, while Cluster add the
ability of failover, is that right?:-)

-Rex

2009/7/9 Gianny Damour gianny.dam...@optusnet.com.au

 I would say the other way around. A cluster is a type of farm.

 I see a farm as a set of independent instances. I see a cluster as a set of
 collaborating instances. You can deploy a non clustered application to a
 farm whereby you do not have resilience in case of service failure. And you
 can deploy a clustered application to a farm to increase service resiliency
 if necessary.

 Thanks,
 Gianny


 On 09/07/2009, at 12:49 PM, Rex Wang wrote:

  well, Gianny, is a server farm not a type of cluster?

 -Rex

 2009/7/8 Gianny Damour gianny.dam...@optusnet.com.au
 Hi,

 It seems to me that farmName would be better than farmingClusterName as
 there is a clear distinction between a farm and a cluster.

 Thanks,
 Gianny


 On 06/07/2009, at 7:47 PM, chi runhua wrote:

 Hi all,

 I just noticed there are 2 pairs of clusterName=CLUSTER_NAME in
 config-substitions.properties.  My understanding of them is one for WADI
 clustering and another for farming.

 Can we using different keywords to identify them? ie.  farmingClusterName
 and WADIClusterName or sth. like that.


 Jeff  C






[BUILD] trunk: Failed for Revision: 792757

2009-07-09 Thread gawor
Geronimo Revision: 792757 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 39 minutes 21 seconds
[INFO] Finished at: Thu Jul 09 21:43:42 EDT 2009
[INFO] Final Memory: 480M/983M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/logs-2100-tomcat/
 
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090709/logs-2100-jetty/
 
 
[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:44.322
[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:02.484) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:33.189) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:36.580) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.270) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:20.701) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:20.392) Java 
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:07.083) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:50.909) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:09.885) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:47.690) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:33.736) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:35.286) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:36.331) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:45.487) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.519) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:46.620) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:30.054) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:49.789) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:47.331) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.858) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:33.097) 
[INFO] web-testsuite/test-jetty   RUNNING
[INFO] web-testsuite/test-jetty   SUCCESS (0:00:25.576) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces

[jira] Updated: (GERONIMO-4540) Improve windows startup batch scripts to redirect stdout and stderr messages to GERONIMO_HOME/var/log/geronimo.out

2009-07-09 Thread Forrest Xia (JIRA)

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

Forrest Xia updated GERONIMO-4540:
--

Priority: Minor  (was: Major)

 Improve windows startup batch scripts to redirect stdout and stderr messages 
 to GERONIMO_HOME/var/log/geronimo.out
 --

 Key: GERONIMO-4540
 URL: https://issues.apache.org/jira/browse/GERONIMO-4540
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: commands
Affects Versions: 2.1.4, 2.2
 Environment: Any windows platform
Reporter: Forrest Xia
Priority: Minor

 Now the windows startup batch scripts print the stdout and stderr in a 
 Command Prompt window, sometimes it is not user-friendly to check error or 
 stdout message for analysis purpose.
 Do we need to improve it, so that the stdout and stderr are redirected to a 
 file, as did on linux platform?
 Please comment. thanks!

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



[jira] Updated: (GERONIMO-4515) Cannot input other gshell commands after starting server in the background

2009-07-09 Thread Forrest Xia (JIRA)

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

Forrest Xia updated GERONIMO-4515:
--

Priority: Minor  (was: Major)

 Cannot input other gshell commands after starting server in the background
 --

 Key: GERONIMO-4515
 URL: https://issues.apache.org/jira/browse/GERONIMO-4515
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: commands
Affects Versions: 2.2
 Environment: JDK 1.6
 Ubuntu 8.04
Reporter: Forrest Xia
Assignee: Jason Dillon
Priority: Minor

 Tried new option -b for gshell command geronimo/start-server as follows:
 $ gshgeronimo/start-server -b
 Problem: finally, the gshell prompt appears, but no way to input other 
 commands.

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



[jira] Updated: (GERONIMO-4509) Two EJB server portlet issues

2009-07-09 Thread Forrest Xia (JIRA)

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

Forrest Xia updated GERONIMO-4509:
--

Priority: Minor  (was: Major)

 Two EJB server portlet issues
 -

 Key: GERONIMO-4509
 URL: https://issues.apache.org/jira/browse/GERONIMO-4509
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
 Environment: JDK 1.6
 Ubuntu 8.04
 AG 2.2 snapshot 20090110
Reporter: Forrest Xia
Assignee: Forrest Xia
Priority: Minor

 For the new EJB server portlet, there are these problems:
 1. Message prompt just restarting openejb module cause several console 
 exceptions and EJB server portlet disappear in admin console at next time 
 restart server.
 Steps:
 1.1 Change value of a EJB container parameter, then it prompts OpenEJB module 
 should be restarted for effectiveness. So I use expert mode to restart module 
 org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car, confirm restart, then 
 several exceptions are thrown out as following:
 2009-01-14 09:35:45,546 ERROR [ConfigManagerPortlet] Exception
 java.lang.IllegalStateException: Configuration 
 org.apache.geronimo.configs/axis2-ejb/2.2-SNAPSHOT/car still has children
 at 
 org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
   at 
 org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
 ...
 2009-01-14 09:35:45,965 ERROR [[SystemModules]] Servlet.service() for servlet 
 SystemModules threw exception
 java.lang.NullPointerException
   at 
 org.apache.geronimo.console.configmanager.ConfigManagerPortlet.getConfigurationState(ConfigManagerPortlet.java:325)
   at 
 org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:272)
   ...
 2009-01-14 09:37:08,300 ERROR [[SystemModules]] Servlet.service() for servlet 
 SystemModules threw exception
 java.lang.IllegalStateException: Configuration 
 org.apache.geronimo.configs/jaxws-ejb-deployer/2.2-SNAPSHOT/car still has 
 children
   at 
 org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
   at 
 org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
 ...
 2009-01-14 09:37:19,125 ERROR [[SystemModules]] Servlet.service() for servlet 
 SystemModules threw exception
 java.lang.IllegalStateException: Configuration 
 org.apache.geronimo.configs/openejb-deployer/2.2-SNAPSHOT/car still has 
 children
   at 
 org.apache.geronimo.kernel.config.ConfigurationStatus.destroy(ConfigurationStatus.java:69)
   at 
 org.apache.geronimo.kernel.config.ConfigurationModel.removeConfiguration(ConfigurationModel.java:65)
   ...
 Anyway, the openejb module finally restarted, but no children modules appear 
 anymore. Consequently the EJB server portlet disappears from the admin 
 console. No way to check if the changed parameter takes effect.
 2.2 Followed by step 1, restart geronimo by no change of config.xml, still 
 the EJB server portlet is not there. Then check the config.xml, the portlet 
 module module 
 name=org.apache.geronimo.plugins/openejb-console-tomcat/2.2-SNAPSHOT/car/ 
 is load=false
 Based on the symptom, I think it might be better to suggest user to restart 
 geronimo server as a whole, not just openejb module.
 2. Another issue is the parameter value seems be changed only once. For 
 example, if you changed strictpooling from default true to false, then you 
 want to change it back without restarting server, there is no way. This 
 behavior is better to be improved.

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



Re: Web app clustering with WADI in Geronimo Tomcat 2.1.4 broken?

2009-07-09 Thread chi runhua
Hi Ganny, please find my comment inline.

On Wed, Jul 8, 2009 at 6:46 PM, Gianny Damour gianny.dam...@optusnet.com.au
 wrote:

 Hi,

 In addition to this doc update, what about trying to uniformise the node
 name?


Not sure If I understand the idea. I assume you were suggesting to use
clustering-wadi/ element for both Tomcat and Jetty.  If yes, it would be
great.



 if the XSD was not extracted, then it was an oversight.


If both Tomcat and Jetty is using the same element for WADI clustering,  can
we port the element into geronimo-web.xsd instead of hiding it under
different plugins?  In that case,  we don't have to worry about this
problem.

just a piece of wild thought here. not sure if it's practical.

Jeff C


Re: [jira] Resolved: (GERONIMO-4560) Run the activemq web console on geronimo

2009-07-09 Thread chi runhua
Is there any place where user can browse all the plugins and their
description? like  www.geronimoplugins.com.


Jeff C

On Thu, Jul 9, 2009 at 10:48 PM, Jarek Gawor (JIRA) j...@apache.org wrote:


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

 Jarek Gawor resolved GERONIMO-4560.
 ---

Resolution: Fixed

 Committed the patch to trunk (revision 792566). Thanks for catching this 
 the patch!



  Run the activemq web console on geronimo
  
 
  Key: GERONIMO-4560
  URL: https://issues.apache.org/jira/browse/GERONIMO-4560
  Project: Geronimo
   Issue Type: New Feature
   Security Level: public(Regular issues)
   Components: ActiveMQ
 Affects Versions: 2.2
 Reporter: David Jencks
 Assignee: David Jencks
  Fix For: 2.2
 
  Attachments: GERONIMO-4560-typo.patch
 
 
  Activemq has a nice little web console that lets you browse queues and
 topics and try sending messages.  We should package this as a geronimo
 plugin.

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




[jira] Created: (GERONIMO-4736) All descriptions in Jetty connector settings page are displayed as undefined message.

2009-07-09 Thread Kan Ogawa (JIRA)
All descriptions in Jetty connector settings page are displayed as undefined 
message.
-

 Key: GERONIMO-4736
 URL: https://issues.apache.org/jira/browse/GERONIMO-4736
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.2
 Environment: Geronimo with Jetty 7
Reporter: Kan Ogawa




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



[jira] Updated: (GERONIMO-4736) All descriptions in Jetty connector settings page are displayed as undefined message.

2009-07-09 Thread Kan Ogawa (JIRA)

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

Kan Ogawa updated GERONIMO-4736:


Attachment: G-4736_ScreenShot.png

 All descriptions in Jetty connector settings page are displayed as undefined 
 message.
 -

 Key: GERONIMO-4736
 URL: https://issues.apache.org/jira/browse/GERONIMO-4736
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
 Environment: Geronimo with Jetty 7
Reporter: Kan Ogawa
 Attachments: G-4736_ScreenShot.png




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



[jira] Updated: (GERONIMO-4737) geronimo-commands module should inherit filter settings from genesis.

2009-07-09 Thread Shawn Jiang (JIRA)

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

Shawn Jiang updated GERONIMO-4737:
--

Attachment: G4737.patch

This is the patch for trunk. 

 geronimo-commands module should inherit filter settings from genesis.
 -

 Key: GERONIMO-4737
 URL: https://issues.apache.org/jira/browse/GERONIMO-4737
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: buildsystem
Affects Versions: 2.2
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor
 Fix For: 2.2

 Attachments: G4737.patch


 geronimo-commands  has is own filter setting in pom.xml.  The settings have 
 conflicts:
 {code}
 resources
 resource
 directory${pom.basedir}/src/main/resources/directory
 includes
 include**/*/include
 /includes
 /resource
 resource
 directory${pom.basedir}/src/main/resources/directory
 filteringtrue/filtering
 includes
 
 includeorg/apache/geronimo/commands/version.properties/include
 /includes
 /resource
 {code}
 One is filteringfalse/filtering, the other is 
 filteringtrue/filtering.   This will result in filter setting merge error 
 sometime.

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



[jira] Created: (GERONIMO-4737) geronimo-commands module should inherit filter settings from genesis.

2009-07-09 Thread Shawn Jiang (JIRA)
geronimo-commands module should inherit filter settings from genesis.
-

 Key: GERONIMO-4737
 URL: https://issues.apache.org/jira/browse/GERONIMO-4737
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: buildsystem
Affects Versions: 2.2
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor
 Fix For: 2.2
 Attachments: G4737.patch

geronimo-commands  has is own filter setting in pom.xml.  The settings have 
conflicts:

{code}
resources
resource
directory${pom.basedir}/src/main/resources/directory
includes
include**/*/include
/includes
/resource

resource
directory${pom.basedir}/src/main/resources/directory
filteringtrue/filtering
includes

includeorg/apache/geronimo/commands/version.properties/include
/includes
/resource
{code}

One is filteringfalse/filtering, the other is filteringtrue/filtering.  
 This will result in filter setting merge error sometime.



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



[jira] Commented: (GERONIMO-4737) geronimo-commands module should inherit filter settings from genesis.

2009-07-09 Thread Shawn Jiang (JIRA)

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

Shawn Jiang commented on GERONIMO-4737:
---

I also searched and found many duplicated filter setting that might be conflict 
with genesis filter settings:

E:\src\gt\plugins\cxf\geronimo-cxf-tools\pom.xml (1 hits)
Line 63: filteringtrue/filtering
\gt\plugins\tomcat\tomcat6\pom.xml (1 hits)
Line 117: filteringtrue/filtering
\gt\plugins\tomcat\tomcat6-deployer\pom.xml (1 hits)
Line 80: filteringtrue/filtering
\gt\plugins\welcome\welcome-tomcat\pom.xml (1 hits)
Line 87: filteringtrue/filtering
\gt\plugins\welcome\welcome-jetty\pom.xml (1 hits)
Line 87: filteringtrue/filtering
\gt\plugins\dojo-legacy\dojo-legacy-tomcat\pom.xml (1 hits)
Line 71: filteringtrue/filtering
\gt\plugins\dojo-legacy\dojo-legacy-jetty\pom.xml (1 hits)
Line 71: filteringtrue/filtering
\gt\plugins\debugviews\debugviews-console-jetty\pom.xml (1 hits)
Line 101: filteringtrue/filtering
\gt\plugins\debugviews\debugviews-console-tomcat\pom.xml (1 hits)
Line 95: filteringtrue/filtering
\gt\plugins\debugviews\debugviews-portlets\pom.xml (1 hits)
Line 116: filteringtrue/filtering
\gt\plugins\activemq\activemq-portlets\pom.xml (1 hits)
Line 108: filteringtrue/filtering
\gt\plugins\activemq\activemq-console-jetty\pom.xml (1 hits)
Line 157: filteringtrue/filtering
\gt\plugins\activemq\activemq-console-tomcat\pom.xml (1 hits)
Line 148: filteringtrue/filtering
\gt\plugins\plancreator\plancreator-console-tomcat\pom.xml (1 hits)
Line 99: filteringtrue/filtering
\gt\plugins\plancreator\plancreator-portlets\pom.xml (1 hits)
Line 152: filteringtrue/filtering
\gt\plugins\plancreator\plancreator-console-jetty\pom.xml (1 hits)
Line 107: filteringtrue/filtering
\gt\plugins\openejb\geronimo-openejb\pom.xml (1 hits)
Line 162: filteringtrue/filtering
\gt\plugins\openejb\openejb-console-jetty\pom.xml (1 hits)
Line 94: filteringtrue/filtering
\gt\plugins\openejb\openejb-console-tomcat\pom.xml (1 hits)
Line 94: filteringtrue/filtering
\gt\plugins\openejb\openejb-portlets\pom.xml (1 hits)
Line 144: filteringtrue/filtering
\gt\plugins\monitoring\mconsole-war\pom.xml (1 hits)
Line 109: filteringtrue/filtering
\gt\plugins\monitoring\agent-sql\pom.xml (1 hits)
Line 43: !-- filteringtrue/filtering --
\gt\plugins\monitoring\pom.xml (1 hits)
Line 81: filteringtrue/filtering
\gt\plugins\system-database\sysdb-console-jetty\pom.xml (1 hits)
Line 254: filteringtrue/filtering
\gt\plugins\system-database\system-database\pom.xml (1 hits)
Line 97: filteringtrue/filtering
\gt\plugins\system-database\sysdb-console-tomcat\pom.xml (1 hits)
Line 239: filteringtrue/filtering
\gt\plugins\system-database\sysdb-portlets\pom.xml (1 hits)
Line 143: filteringtrue/filtering
\gt\plugins\dojo\dojo-tomcat\pom.xml (1 hits)
Line 71: filteringtrue/filtering
\gt\plugins\dojo\dojo-jetty\pom.xml (1 hits)
Line 71: filteringtrue/filtering
\gt\plugins\openjpa\openjpa\pom.xml (1 hits)
Line 82: filteringtrue/filtering
\gt\plugins\jaxws\geronimo-jaxws-sun-tools\pom.xml (1 hits)
Line 53: filteringtrue/filtering
\gt\plugins\ca-helper\ca-helper-tomcat\pom.xml (1 hits)
Line 78: filteringtrue/filtering
\gt\plugins\ca-helper\ca-helper-jetty\pom.xml (1 hits)
Line 78: filteringtrue/filtering
\gt\plugins\console\console-jetty\pom.xml (1 hits)
Line 127: filteringtrue/filtering
\gt\plugins\console\plugin-console-tomcat\pom.xml (1 hits)
Line 96: filteringtrue/filtering
\gt\plugins\console\console-base-portlets\pom.xml (1 hits)
Line 108: filteringtrue/filtering
\gt\plugins\console\console-tomcat\pom.xml (1 hits)
Line 127: filteringtrue/filtering
\gt\plugins\console\plugin-portlets\pom.xml (1 hits)
Line 135: filteringtrue/filtering
\gt\plugins\console\console-portal-driver\pom.xml (1 hits)
Line 100: filteringtrue/filtering
\gt\plugins\console\plugin-console-jetty\pom.xml (1 hits)
Line 96: filteringtrue/filtering
\gt\plugins\mejb\geronimo-mejb\pom.xml (1 hits)