[jira] Commented: (GERONIMO-4189) Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server
[ https://issues.apache.org/jira/browse/GERONIMO-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614243#action_12614243 ] Shiva Kumar H R commented on GERONIMO-4189: --- GERONIMODEVTOOLS-434 shows how GEP can get the required dynamic information from Server using JMX (neat approach), instead of the earlier approach of having a dedicated Servlet deployed on the system. Hence the changes that were earlier made in revision: 675220 have been reverted at revision: 677509. Thanks to Jarek for capturing this, and to Sainath for figuring out how to use JMX to get the required dynamic info. Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server Key: GERONIMO-4189 URL: https://issues.apache.org/jira/browse/GERONIMO-4189 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: PlanCreator Affects Versions: 2.2 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.2 For intuitive creation/editing of Geronimo Deployment Plans inside GEP Deployment Plan Editors, GEP must be able to query the server for deployed resources (GERONIMODEVTOOLS-425). One of the ways of accomplishing this (thanks to Vamsi for the idea!) is as below: 1. Have a Servlet deployed running on the server, that can issue GBean queries to fetch the required dynamic info from the server (like deployed EJBs, JDBC Connection Pools, JMS Connection Factories Destinations, Java Mail Sessions, Credential Stores, Common Libs Security Realms) and pass this info to the caller may be as a binary object. 2. Inside GEP, invoke the above Servlet with required arguments to get the dynamic info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4189) Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server
[ https://issues.apache.org/jira/browse/GERONIMO-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMO-4189. - Resolution: Invalid Enable Geronimo Eclipse Plug-in (GEP) to get dynamic information from server Key: GERONIMO-4189 URL: https://issues.apache.org/jira/browse/GERONIMO-4189 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: PlanCreator Affects Versions: 2.2 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.2 For intuitive creation/editing of Geronimo Deployment Plans inside GEP Deployment Plan Editors, GEP must be able to query the server for deployed resources (GERONIMODEVTOOLS-425). One of the ways of accomplishing this (thanks to Vamsi for the idea!) is as below: 1. Have a Servlet deployed running on the server, that can issue GBean queries to fetch the required dynamic info from the server (like deployed EJBs, JDBC Connection Pools, JMS Connection Factories Destinations, Java Mail Sessions, Credential Stores, Common Libs Security Realms) and pass this info to the caller may be as a binary object. 2. Inside GEP, invoke the above Servlet with required arguments to get the dynamic info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r675220 - in /geronimo/server/trunk/plugins: console/console-core/src/main/java/org/apache/geronimo/console/util/ plancreator/plancreator-portlets/src/main/java/org/apache/geronimo/con
Changes that were earlier made in this revision: 675220 have been reverted at revision: 677509. Please see GERONIMO-4189. and sorry for not doing this yesterday itself - I was caught up with some thing else On Wed, Jul 16, 2008 at 12:33 PM, Shiva Kumar H R [EMAIL PROTECTED] wrote: I had earlier replied to Kevan's mail. Looks like some problem with my mailbox and it didn't get through. I will be reverting these changes and committing Sainath's patch today. And thanks very much Sainath for your awesome work on GERONIMODEVTOOLS-434. On Wed, Jul 16, 2008 at 11:53 AM, Sainath Chowdary [EMAIL PROTECTED] wrote: Hi Kevan, Now we can pretty much delete the servlet added to plan creator for providing dynamic information to GEP. The following JIRA solves the problem using JMX to query the server directly. https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434 On Tue, Jul 15, 2008 at 11:03 PM, Kevan Miller [EMAIL PROTECTED] wrote: On Jul 9, 2008, at 12:00 PM, Shiva Kumar H R wrote: Thanks Jarek, I will explore JMX to see if I can get all the dynamic info I am looking for. If JMX does provide such info, I will revert back all these and use JMX instead. Shiva, How do things stand with your investigations? IMO, this change is not appropriate. --kevan -- Thanks, Sainath Chowdary B.Tech III yr, Spring Semester Electronics Communication Engg Indian Institute of Technology Roorkee -- Thanks, Shiva -- Thanks, Shiva
[jira] Commented: (GERONIMODEVTOOLS-425) Query Dynamic Information from Server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614265#action_12614265 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-425: -- Thanks to Sainath's work on GERONIMODEVTOOLS-434, we have figured out how to use JMX to get the required dynamic info. Hence, the changes that were earlier made in revision: 675230 have been reverted at revision: 677519. Query Dynamic Information from Server - Key: GERONIMODEVTOOLS-425 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-425 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.x Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.x Plan Creator allows intuitive mapping of references declared in a Web application to specific resources available in the server environment. On the References page of Plan Creator, references declared in a web-app (like EJB, EJB Local, JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS Destination references), and the resources available in the server environment to which they can be linked are both shown, and users are asked to just link them up. To enable this feature in GEP Deployment Plan Editor, GEP must be able to query the server for deployed resources. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-434) Query Dynamic Information from Server using JMX
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R resolved GERONIMODEVTOOLS-434. -- Resolution: Fixed Committed in trunk at revision: 677535. Many thanks Sainath for this critical work. Query Dynamic Information from Server using JMX --- Key: GERONIMODEVTOOLS-434 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.2, 2.1.x Reporter: Sainath Chowdary Assignee: Shiva Kumar H R Fix For: 2.1.2, 2.1.x Attachments: jmx-dynamicquery-modified.patch, jmx-dynamicserverinfo.patch, jmxquery-sampleoutput.txt Enabling GEP to query server for dynamic information on the lines of Plancreator using a JMXConnectionFactory. Querying dynamic information has already been done but having a Servlet on server side that sends data to GEP. This has severe exceptions when a old server is added or custom server assemblies are added to GEP which wont have the particular servlet added. Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local, JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS Destination references) from Server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-434) Query Dynamic Information from Server using JMX
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-434: Assignee: Sainath Chowdary (was: Shiva Kumar H R) Query Dynamic Information from Server using JMX --- Key: GERONIMODEVTOOLS-434 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-434 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.2, 2.1.x Reporter: Sainath Chowdary Assignee: Sainath Chowdary Fix For: 2.1.2, 2.1.x Attachments: jmx-dynamicquery-modified.patch, jmx-dynamicserverinfo.patch, jmxquery-sampleoutput.txt Enabling GEP to query server for dynamic information on the lines of Plancreator using a JMXConnectionFactory. Querying dynamic information has already been done but having a Servlet on server side that sends data to GEP. This has severe exceptions when a old server is added or custom server assemblies are added to GEP which wont have the particular servlet added. Instead use JMX from GEP to retrieve the dynamic information (EJB, EJB Local, JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS Destination references) from Server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-425) Query Dynamic Information from Server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R resolved GERONIMODEVTOOLS-425. -- Resolution: Duplicate Fix Version/s: 2.1.2 Assignee: Sainath Chowdary (was: Shiva Kumar H R) GERONIMODEVTOOLS-434 solved this problem. Query Dynamic Information from Server - Key: GERONIMODEVTOOLS-425 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-425 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.x Reporter: Shiva Kumar H R Assignee: Sainath Chowdary Fix For: 2.1.2, 2.1.x Plan Creator allows intuitive mapping of references declared in a Web application to specific resources available in the server environment. On the References page of Plan Creator, references declared in a web-app (like EJB, EJB Local, JDBC Connection Pool, JavaMail Session, JMS Connection Factory and JMS Destination references), and the resources available in the server environment to which they can be linked are both shown, and users are asked to just link them up. To enable this feature in GEP Deployment Plan Editor, GEP must be able to query the server for deployed resources. -- 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: 677515
Geronimo Revision: 677515 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080717/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080717
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 45 minutes 50 seconds
[INFO] Finished at: Thu Jul 17 03:53:02 EDT 2008
[INFO] Final Memory: 398M/972M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080717/logs-0300-tomcat/test.log
Assembly: jetty
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080717/logs-0300-jetty/test.log
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: jetty
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty6-javaee5/2.2-SNAPSHOT/geronimo-jetty6-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:41.082
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 31 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deploySUCCESS (0:01:03.071)
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:29.943)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:18.820)
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:07.931)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:01:19.798) Java
returned: 1
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:48.335)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:43.752)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:00:57.684)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:43.758)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:31.888)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:29.163)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:29.754)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb
[jira] Commented: (GERONIMO-3599) Unable to create new JMS Resource group through console in IE7
[ https://issues.apache.org/jira/browse/GERONIMO-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614388#action_12614388 ] Joseph Leong commented on GERONIMO-3599: Continually working on this hoping to contribute for release. Have been trying to convert everything over to sessions. A little frustrating, taking some time converting to storing in session as well as recalling data from a session. Also, trying to figure out and figuring out where the lose ends are. -Joseph Leong Unable to create new JMS Resource group through console in IE7 -- Key: GERONIMO-3599 URL: https://issues.apache.org/jira/browse/GERONIMO-3599 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.0.1 Environment: WIN XP Reporter: Anish Pathadan Assignee: Joseph Leong Fix For: 2.1.2, 2.1.x, 2.2 I am not able to create a new JMS Resouce group through console. I am getting cannot display the page error after entering the Q name and physical name and then pressing next. The following is the url http://localhost:8080/console/portal/services/services_jms/_ps_services_jms_row1_col1_p1/normal/_pm_services_jms_row1_col1_p1/view/_ac_services_jms_row1_col1_p1/AC/_st_services_jms_row1_col1_p1/normal/_md_services_jms_row1_col1_p1/view/_pid/services_jms_row1_col1_p1 The problem only comes with Internet Explorer 7. Best Regards, Anish Pathadan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
unable to build trunk on windows machine
Hi, I have been having probs building trunk on my winxp machine. It failed at building geronimo-jetty6-javaee5, at the jaxws GShellCommandRegistration ant task. Looks like it is related to some sorta of classpath too long prob on windows... note that the last character (C:\Documents and Settings\Administrator\.m 2\repository\org\slf4ö) is corrupted. [copy] Copying 331 files to C:\trunk\assemblies\geronimo-jetty6-javaee5\tar get\assembly [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: java.io.IOException: CreateProcess: C:\Progra~1\Java\jdk1.5.0_14 \jre\bin\java.exe -classpath C:\trunk\assemblies\geronimo-jetty6-javaee5\target \classes;C:\Documents and Settings\Administrator\.m2\repository\org\codehaus\ple xus\plexus-classworlds\1.2-alpha-10\plexus-classworlds-1.2-alpha-10.jar;C:\Docum ents and Settings\Administrator\.m2\repository\asm\asm\2.2.3\asm-2.2.3.jar;C:\Do cuments and Settings\Administrator\.m2\repository\asm\asm-commons\2.2.3\asm-comm ons-2.2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\asm\asm-tre e\2.2.3\asm-tree-2.2.3.jar;C:\Documents and Settings\Administrator\.m2\repositor y\cglib\cglib-nodep\2.1_3\cglib-nodep-2.1_3.jar;C:\Documents and Settings\Admini strator\.m2\repository\commons-cli\commons-cli\1.0\commons-cli-1.0.jar;C:\Docume nts and Settings\Administrator\.m2\repository\commons-lang\commons-lang\2.3\comm ons-lang-2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\org\slf4 j\slf4j-api\1.5.0\slf4j-api-1.5.0.jar;C:\Documents and Settings\Administrator\.m 2\repository\org\slf4ö [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant task s at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing ant t asks at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractA ntMojo.java:114) at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:558) ... 16 more Caused by: java.io.IOException: CreateProcess: C:\Progra~1\Java\jdk1.5.0_14\jre\ bin\java.exe -classpath C:\trunk\assemblies\geronimo-jetty6-javaee5\target\clas ses;C:\Documents and Settings\Administrator\.m2\repository\org\codehaus\plexus\p lexus-classworlds\1.2-alpha-10\plexus-classworlds-1.2-alpha-10.jar;C:\Documents and Settings\Administrator\.m2\repository\asm\asm\2.2.3\asm-2.2.3.jar;C:\Documen ts and Settings\Administrator\.m2\repository\asm\asm-commons\2.2.3\asm-commons-2 .2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\asm\asm-tree\2.2 .3\asm-tree-2.2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\cgl ib\cglib-nodep\2.1_3\cglib-nodep-2.1_3.jar;C:\Documents and Settings\Administrat or\.m2\repository\commons-cli\commons-cli\1.0\commons-cli-1.0.jar;C:\Documents a nd Settings\Administrator\.m2\repository\commons-lang\commons-lang\2.3\commons-l ang-2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\org\slf4j\slf 4j-api\1.5.0\slf4j-api-1.5.0.jar;C:\Documents and Settings\Administrator\.m2\rep
Re: unable to build trunk on windows machine
You might want to try moving your m2 repository to someplace other than the default location. I have mine at c:/.m2, and don't have any problems building. Rick Lin Sun wrote: Hi, I have been having probs building trunk on my winxp machine. It failed at building geronimo-jetty6-javaee5, at the jaxws GShellCommandRegistration ant task. Looks like it is related to some sorta of classpath too long prob on windows... note that the last character (C:\Documents and Settings\Administrator\.m 2\repository\org\slf4ö) is corrupted. [copy] Copying 331 files to C:\trunk\assemblies\geronimo-jetty6-javaee5\tar get\assembly [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: java.io.IOException: CreateProcess: C:\Progra~1\Java\jdk1.5.0_14 \jre\bin\java.exe -classpath C:\trunk\assemblies\geronimo-jetty6-javaee5\target \classes;C:\Documents and Settings\Administrator\.m2\repository\org\codehaus\ple xus\plexus-classworlds\1.2-alpha-10\plexus-classworlds-1.2-alpha-10.jar;C:\Docum ents and Settings\Administrator\.m2\repository\asm\asm\2.2.3\asm-2.2.3.jar;C:\Do cuments and Settings\Administrator\.m2\repository\asm\asm-commons\2.2.3\asm-comm ons-2.2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\asm\asm-tre e\2.2.3\asm-tree-2.2.3.jar;C:\Documents and Settings\Administrator\.m2\repositor y\cglib\cglib-nodep\2.1_3\cglib-nodep-2.1_3.jar;C:\Documents and Settings\Admini strator\.m2\repository\commons-cli\commons-cli\1.0\commons-cli-1.0.jar;C:\Docume nts and Settings\Administrator\.m2\repository\commons-lang\commons-lang\2.3\comm ons-lang-2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\org\slf4 j\slf4j-api\1.5.0\slf4j-api-1.5.0.jar;C:\Documents and Settings\Administrator\.m 2\repository\org\slf4ö [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant task s at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing ant t asks at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractA ntMojo.java:114) at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:558) ... 16 more Caused by: java.io.IOException: CreateProcess: C:\Progra~1\Java\jdk1.5.0_14\jre\ bin\java.exe -classpath C:\trunk\assemblies\geronimo-jetty6-javaee5\target\clas ses;C:\Documents and Settings\Administrator\.m2\repository\org\codehaus\plexus\p lexus-classworlds\1.2-alpha-10\plexus-classworlds-1.2-alpha-10.jar;C:\Documents and Settings\Administrator\.m2\repository\asm\asm\2.2.3\asm-2.2.3.jar;C:\Documen ts and Settings\Administrator\.m2\repository\asm\asm-commons\2.2.3\asm-commons-2 .2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\asm\asm-tree\2.2 .3\asm-tree-2.2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\cgl ib\cglib-nodep\2.1_3\cglib-nodep-2.1_3.jar;C:\Documents and Settings\Administrat or\.m2\repository\commons-cli\commons-cli\1.0\commons-cli-1.0.jar;C:\Documents a nd
[jira] Assigned: (GERONIMODEVTOOLS-441) Retrieving Metadata complete Deployment Descriptor for Web Projects
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-441: Assignee: Shiva Kumar H R (was: Tim McConnell) Retrieving Metadata complete Deployment Descriptor for Web Projects --- Key: GERONIMODEVTOOLS-441 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-441 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.2, 2.1.x Reporter: Sainath Chowdary Assignee: Shiva Kumar H R Fix For: 2.1.2, 2.1.x Attachments: DeploymentDescriptor.patch Another critical aspect for porting plan creator work in GEP is to retrieve the metadata complete deployment descriptor. This also links the deployment descriptor and deployment plan effectively. This should emphasize at creating an architecture so that it can be easily extended for other type of projects like EJBs, EARs etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
tomcat 6.0.14 jars in testsuite
I'm not very familiar with how the testsuite works but it seems that it uses a 2.2 snapshot of jetty based on what's unpacked into my testsuite directory. Where does this snapshot come from? It's using 6.0.14 versions of tomcat jars when the rest of trunk is using 6.0.16. It's possible I missed an entry when updating the tomcat version but I can't seem to find where it would have been missed. I'm sure I got everything in the root geronimo pom. Anyone know what could cause this version discrepancy? I assume that this snapshot version is what the testsuite is run against and I think we should be using the same versions of jars on both. Any insight would be greatly appreciated. Thanks, -- ~Jason Warner
Re: tomcat 6.0.14 jars in testsuite
I forgot to add an example of what I'm referring to. I ran find -E ./ -name jasper-6.0.14-G614585.jar -print from geronimo home and got the following results; .//testsuite/console-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/corba-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/deployment-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/enterprise-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/security-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/web-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/webservices-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar On Thu, Jul 17, 2008 at 12:45 PM, Jason Warner [EMAIL PROTECTED] wrote: I'm not very familiar with how the testsuite works but it seems that it uses a 2.2 snapshot of jetty based on what's unpacked into my testsuite directory. Where does this snapshot come from? It's using 6.0.14 versions of tomcat jars when the rest of trunk is using 6.0.16. It's possible I missed an entry when updating the tomcat version but I can't seem to find where it would have been missed. I'm sure I got everything in the root geronimo pom. Anyone know what could cause this version discrepancy? I assume that this snapshot version is what the testsuite is run against and I think we should be using the same versions of jars on both. Any insight would be greatly appreciated. Thanks, -- ~Jason Warner -- ~Jason Warner
Re: tomcat 6.0.14 jars in testsuite
Is this caused by the following in trunk\pom.xml? !-- Tomcat web container -- dependency groupIdorg.apache.tomcat/groupId artifactIdjasper/artifactId version6.0.16-G652117/version /dependency I don't remember the details - I thought we need a private copy of the jasper jar for a fix. Lin On Thu, Jul 17, 2008 at 12:51 PM, Jason Warner [EMAIL PROTECTED] wrote: I forgot to add an example of what I'm referring to. I ran find -E ./ -name jasper-6.0.14-G614585.jar -print from geronimo home and got the following results; .//testsuite/console-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/corba-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/deployment-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/enterprise-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/security-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/web-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/webservices-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar On Thu, Jul 17, 2008 at 12:45 PM, Jason Warner [EMAIL PROTECTED] wrote: I'm not very familiar with how the testsuite works but it seems that it uses a 2.2 snapshot of jetty based on what's unpacked into my testsuite directory. Where does this snapshot come from? It's using 6.0.14 versions of tomcat jars when the rest of trunk is using 6.0.16. It's possible I missed an entry when updating the tomcat version but I can't seem to find where it would have been missed. I'm sure I got everything in the root geronimo pom. Anyone know what could cause this version discrepancy? I assume that this snapshot version is what the testsuite is run against and I think we should be using the same versions of jars on both. Any insight would be greatly appreciated. Thanks, -- ~Jason Warner -- ~Jason Warner
Re: unable to build trunk on windows machine
Thanks I'll try that to work around the prob. Lin On Thu, Jul 17, 2008 at 12:06 PM, Rick McGuire [EMAIL PROTECTED] wrote: You might want to try moving your m2 repository to someplace other than the default location. I have mine at c:/.m2, and don't have any problems building. Rick Lin Sun wrote: Hi, I have been having probs building trunk on my winxp machine. It failed at building geronimo-jetty6-javaee5, at the jaxws GShellCommandRegistration ant task. Looks like it is related to some sorta of classpath too long prob on windows... note that the last character (C:\Documents and Settings\Administrator\.m 2\repository\org\slf4ö) is corrupted. [copy] Copying 331 files to C:\trunk\assemblies\geronimo-jetty6-javaee5\tar get\assembly [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: java.io.IOException: CreateProcess: C:\Progra~1\Java\jdk1.5.0_14 \jre\bin\java.exe -classpath C:\trunk\assemblies\geronimo-jetty6-javaee5\target \classes;C:\Documents and Settings\Administrator\.m2\repository\org\codehaus\ple xus\plexus-classworlds\1.2-alpha-10\plexus-classworlds-1.2-alpha-10.jar;C:\Docum ents and Settings\Administrator\.m2\repository\asm\asm\2.2.3\asm-2.2.3.jar;C:\Do cuments and Settings\Administrator\.m2\repository\asm\asm-commons\2.2.3\asm-comm ons-2.2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\asm\asm-tre e\2.2.3\asm-tree-2.2.3.jar;C:\Documents and Settings\Administrator\.m2\repositor y\cglib\cglib-nodep\2.1_3\cglib-nodep-2.1_3.jar;C:\Documents and Settings\Admini strator\.m2\repository\commons-cli\commons-cli\1.0\commons-cli-1.0.jar;C:\Docume nts and Settings\Administrator\.m2\repository\commons-lang\commons-lang\2.3\comm ons-lang-2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\org\slf4 j\slf4j-api\1.5.0\slf4j-api-1.5.0.jar;C:\Documents and Settings\Administrator\.m 2\repository\org\slf4ö [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant task s at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing ant t asks at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractA ntMojo.java:114) at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:558) ... 16 more Caused by: java.io.IOException: CreateProcess: C:\Progra~1\Java\jdk1.5.0_14\jre\ bin\java.exe -classpath C:\trunk\assemblies\geronimo-jetty6-javaee5\target\clas ses;C:\Documents and Settings\Administrator\.m2\repository\org\codehaus\plexus\p lexus-classworlds\1.2-alpha-10\plexus-classworlds-1.2-alpha-10.jar;C:\Documents and Settings\Administrator\.m2\repository\asm\asm\2.2.3\asm-2.2.3.jar;C:\Documen ts and Settings\Administrator\.m2\repository\asm\asm-commons\2.2.3\asm-commons-2 .2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\asm\asm-tree\2.2 .3\asm-tree-2.2.3.jar;C:\Documents and Settings\Administrator\.m2\repository\cgl
[jira] Commented: (GERONIMO-4201) Accessing admin console portlets that use DWR after restart giving error
[ https://issues.apache.org/jira/browse/GERONIMO-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614434#action_12614434 ] Manu T George commented on GERONIMO-4201: - Sorry forgot to test with jetty. Need to remember that G has 2 web containers. Accessing admin console portlets that use DWR after restart giving error Key: GERONIMO-4201 URL: https://issues.apache.org/jira/browse/GERONIMO-4201 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1 Environment: All Reporter: Manu T George Assignee: Jarek Gawor Fix For: 2.1.2, 2.2 Attachments: G4201_r673785.patch Restart one of the debug views portlet from the admin console and all dwr calls fail The exception is 02:28:42,399 ERROR [[dwr-forward2]] Servlet.service() for servlet dwr-forward2 threw exception java.lang.NullPointerException at org.apache.geronimo.console.servlet.ContextForwardServlet.doPost(ContextForwardServlet.java:74) at org.apache.geronimo.console.servlet.ContextForwardServlet.doGet(ContextForwardServlet.java:60) 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.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: tomcat 6.0.14 jars in testsuite
We do have a private copy of the jasper jar (and the catalina one too), but they're both based off of the 6.0.16 release of tomcat now. Based on what you've posted, and what i saw when I checked earlier, they're declared properly. It's the older jars that I'm finding in use in the snapshot in the testsuite that I'm confused about. On Thu, Jul 17, 2008 at 12:57 PM, Lin Sun [EMAIL PROTECTED] wrote: Is this caused by the following in trunk\pom.xml? !-- Tomcat web container -- dependency groupIdorg.apache.tomcat/groupId artifactIdjasper/artifactId version6.0.16-G652117/version /dependency I don't remember the details - I thought we need a private copy of the jasper jar for a fix. Lin On Thu, Jul 17, 2008 at 12:51 PM, Jason Warner [EMAIL PROTECTED] wrote: I forgot to add an example of what I'm referring to. I ran find -E ./ -name jasper-6.0.14-G614585.jar -print from geronimo home and got the following results; .//testsuite/console-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/corba-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/deployment-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/enterprise-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/security-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/web-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/webservices-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar On Thu, Jul 17, 2008 at 12:45 PM, Jason Warner [EMAIL PROTECTED] wrote: I'm not very familiar with how the testsuite works but it seems that it uses a 2.2 snapshot of jetty based on what's unpacked into my testsuite directory. Where does this snapshot come from? It's using 6.0.14 versions of tomcat jars when the rest of trunk is using 6.0.16. It's possible I missed an entry when updating the tomcat version but I can't seem to find where it would have been missed. I'm sure I got everything in the root geronimo pom. Anyone know what could cause this version discrepancy? I assume that this snapshot version is what the testsuite is run against and I think we should be using the same versions of jars on both. Any insight would be greatly appreciated. Thanks, -- ~Jason Warner -- ~Jason Warner -- ~Jason Warner
Re: tomcat 6.0.14 jars in testsuite
Sorry I read the version number wrong :-( ignore my note below. Lin On Thu, Jul 17, 2008 at 12:57 PM, Lin Sun [EMAIL PROTECTED] wrote: Is this caused by the following in trunk\pom.xml? !-- Tomcat web container -- dependency groupIdorg.apache.tomcat/groupId artifactIdjasper/artifactId version6.0.16-G652117/version /dependency I don't remember the details - I thought we need a private copy of the jasper jar for a fix. Lin On Thu, Jul 17, 2008 at 12:51 PM, Jason Warner [EMAIL PROTECTED] wrote: I forgot to add an example of what I'm referring to. I ran find -E ./ -name jasper-6.0.14-G614585.jar -print from geronimo home and got the following results; .//testsuite/console-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/corba-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/deployment-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/enterprise-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/security-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/web-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/webservices-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar On Thu, Jul 17, 2008 at 12:45 PM, Jason Warner [EMAIL PROTECTED] wrote: I'm not very familiar with how the testsuite works but it seems that it uses a 2.2 snapshot of jetty based on what's unpacked into my testsuite directory. Where does this snapshot come from? It's using 6.0.14 versions of tomcat jars when the rest of trunk is using 6.0.16. It's possible I missed an entry when updating the tomcat version but I can't seem to find where it would have been missed. I'm sure I got everything in the root geronimo pom. Anyone know what could cause this version discrepancy? I assume that this snapshot version is what the testsuite is run against and I think we should be using the same versions of jars on both. Any insight would be greatly appreciated. Thanks, -- ~Jason Warner -- ~Jason Warner
Re: tomcat 6.0.14 jars in testsuite
It looks like it ended up just being staled jars lying around in my directory. Doesn't seem to be a problem. Nothing to see here... Thanks! On Thu, Jul 17, 2008 at 1:06 PM, Lin Sun [EMAIL PROTECTED] wrote: Sorry I read the version number wrong :-( ignore my note below. Lin On Thu, Jul 17, 2008 at 12:57 PM, Lin Sun [EMAIL PROTECTED] wrote: Is this caused by the following in trunk\pom.xml? !-- Tomcat web container -- dependency groupIdorg.apache.tomcat/groupId artifactIdjasper/artifactId version6.0.16-G652117/version /dependency I don't remember the details - I thought we need a private copy of the jasper jar for a fix. Lin On Thu, Jul 17, 2008 at 12:51 PM, Jason Warner [EMAIL PROTECTED] wrote: I forgot to add an example of what I'm referring to. I ran find -E ./ -name jasper-6.0.14-G614585.jar -print from geronimo home and got the following results; .//testsuite/console-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/corba-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/deployment-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/enterprise-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/security-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/web-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar .//testsuite/webservices-testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT/repository/org/apache/tomcat/jasper/6.0.14-G614585/jasper-6.0.14-G614585.jar On Thu, Jul 17, 2008 at 12:45 PM, Jason Warner [EMAIL PROTECTED] wrote: I'm not very familiar with how the testsuite works but it seems that it uses a 2.2 snapshot of jetty based on what's unpacked into my testsuite directory. Where does this snapshot come from? It's using 6.0.14 versions of tomcat jars when the rest of trunk is using 6.0.16. It's possible I missed an entry when updating the tomcat version but I can't seem to find where it would have been missed. I'm sure I got everything in the root geronimo pom. Anyone know what could cause this version discrepancy? I assume that this snapshot version is what the testsuite is run against and I think we should be using the same versions of jars on both. Any insight would be greatly appreciated. Thanks, -- ~Jason Warner -- ~Jason Warner -- ~Jason Warner
[BUILD] trunk: Failed for Revision: 677574
Geronimo Revision: 677574 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080717/build-0900.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080717/unit-test-reports
[INFO] Building Geronimo Plugins, Concurrency Utilities :: Management API
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 4 source files to
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-management/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-management/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-management/target/geronimo-concurrent-management-2.2-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-concurrent-management-2.2-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-management/target/geronimo-concurrent-management-2.2-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-concurrent-management/2.2-SNAPSHOT/geronimo-concurrent-management-2.2-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, Concurrency Utilities :: Core
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 31 source files to
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-core/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 17 source files to
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-core/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-core/target/surefire-reports
---
T E S T S
---
Running
org.apache.geronimo.concurrent.executor.ServerManagedScheduledExecutorServiceTest
Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 96.205 sec
Running
org.apache.geronimo.concurrent.executor.ComponentManagedExecutorServiceTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.056 sec
Running org.apache.geronimo.concurrent.executor.ServerManagedExecutorServiceTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.044 sec
Running org.apache.geronimo.concurrent.context.ContextServiceTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.03 sec
Running org.apache.geronimo.concurrent.harmony.FutureTaskTest
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There are test failures.
Please refer to
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-core/target/surefire-reports
for the individual test results.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.
Please refer to
/home/geronimo/geronimo/trunk/plugins/concurrent/geronimo-concurrent-core/target/surefire-reports
for the individual test results.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330
[jira] Resolved: (GERONIMO-4205) unable to build samples on windows platoform due to Filename too long
[ https://issues.apache.org/jira/browse/GERONIMO-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun resolved GERONIMO-4205. --- Resolution: Fixed Fix Version/s: 2.2 2.1 branch rev 677340 trunk rev 677701 (also see subversion tab) unable to build samples on windows platoform due to Filename too long - Key: GERONIMO-4205 URL: https://issues.apache.org/jira/browse/GERONIMO-4205 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.1, 2.1.2 Environment: winxp Reporter: Lin Sun Assignee: Lin Sun Fix For: 2.1.2, 2.2 Attachments: G4205new.zip Steps- 1. check out branch 2.1 samples https://svn.apache.org/repos/asf/geronimo/samples/branches/2.1/ to a very short dir c:\21sam 2. install G2.1 private repo 3. use maven 2.0.7 to build samples at c:\21sam dir. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Could not scan module for TLD files: customer-service-war-2.1-SNAPSHOT.wa r Filename too long [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Could not scan module fo r TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Could not scan module for TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long at org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java: 137) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.geronimo.common.DeploymentException: Could not scan module for TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.scanM odule(JspModuleBuilderExtension.java:297) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.getTl dFiles(JspModuleBuilderExtension.java:238) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.creat eJspClassFinder(JspModuleBuilderExtension.java:179) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.addGB eans(JspModuleBuilderExtension.java:149) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans(Je ttyModuleBuilder.java:518) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans( SwitchingModuleBuilder.java:165) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfigurati on(EARConfigBuilder.java:647) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at
[jira] Closed: (GERONIMO-4205) unable to build samples on windows platoform due to Filename too long
[ https://issues.apache.org/jira/browse/GERONIMO-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun closed GERONIMO-4205. - close issue, tested on a dir that has 14 characters such as c:\geronimosample. unable to build samples on windows platoform due to Filename too long - Key: GERONIMO-4205 URL: https://issues.apache.org/jira/browse/GERONIMO-4205 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.1, 2.1.2 Environment: winxp Reporter: Lin Sun Assignee: Lin Sun Fix For: 2.1.2, 2.2 Attachments: G4205new.zip Steps- 1. check out branch 2.1 samples https://svn.apache.org/repos/asf/geronimo/samples/branches/2.1/ to a very short dir c:\21sam 2. install G2.1 private repo 3. use maven 2.0.7 to build samples at c:\21sam dir. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Could not scan module for TLD files: customer-service-war-2.1-SNAPSHOT.wa r Filename too long [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Could not scan module fo r TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Could not scan module for TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long at org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java: 137) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.geronimo.common.DeploymentException: Could not scan module for TLD files: customer-service-war-2.1-SNAPSHOT.war Filename too long at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.scanM odule(JspModuleBuilderExtension.java:297) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.getTl dFiles(JspModuleBuilderExtension.java:238) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.creat eJspClassFinder(JspModuleBuilderExtension.java:179) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.addGB eans(JspModuleBuilderExtension.java:149) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans(Je ttyModuleBuilder.java:518) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans( SwitchingModuleBuilder.java:165) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfigurati on(EARConfigBuilder.java:647) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at
[jira] Resolved: (GERONIMO-4194) jsp sample view source links are broken
[ https://issues.apache.org/jira/browse/GERONIMO-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun resolved GERONIMO-4194. --- Resolution: Fixed see subversion tab for revisions. The view source htmls for jsp-examples are auto-generated during build. I didn't update the build to auto generate the servlet examples' view source htmls as there are only 4 files and they already exist and provided by tomcat. jsp sample view source links are broken --- Key: GERONIMO-4194 URL: https://issues.apache.org/jira/browse/GERONIMO-4194 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.2, 2.1.x, 2.2 Reporter: Lin Sun Assignee: Lin Sun Priority: Minor Fix For: 2.1.2, 2.1.x, 2.2 All the view source links are broken in the jsp examples. They are pointing to the corresponding jsp.html or java.html files which we don't have in our repo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4194) jsp sample view source links are broken
[ https://issues.apache.org/jira/browse/GERONIMO-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun closed GERONIMO-4194. - Tested with both tomcat and jetty assembly jsp sample view source links are broken --- Key: GERONIMO-4194 URL: https://issues.apache.org/jira/browse/GERONIMO-4194 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.2, 2.1.x, 2.2 Reporter: Lin Sun Assignee: Lin Sun Priority: Minor Fix For: 2.1.2, 2.1.x, 2.2 All the view source links are broken in the jsp examples. They are pointing to the corresponding jsp.html or java.html files which we don't have in our repo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4131) Problems with WebSphere MQ RA deployment
[ https://issues.apache.org/jira/browse/GERONIMO-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated GERONIMO-4131: -- Attachment: (was: GERONIMO-4131.patch) Problems with WebSphere MQ RA deployment Key: GERONIMO-4131 URL: https://issues.apache.org/jira/browse/GERONIMO-4131 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector Affects Versions: 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2 Reporter: Kevan Miller Assignee: Jarek Gawor Fix For: 2.1.2 Attachments: GERONIMO-4131.patch A user reported problems deploying an MQ RA on Geronimo. Looks like there are several problems. 1) we don't like config-property-name values in ra.xml to start with a lower case letter 2) our mechanism for introspecting the implementation classes (e.g. managedconnectionfactory-class) is not working properly. there can be multiple set methods taking different parameter types. This is leading to type-mismatches as we try to set attributes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4131) Problems with WebSphere MQ RA deployment
[ https://issues.apache.org/jira/browse/GERONIMO-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated GERONIMO-4131: -- Attachment: GERONIMO-4131.patch Latest patch. Deals with property name cases. Problems with WebSphere MQ RA deployment Key: GERONIMO-4131 URL: https://issues.apache.org/jira/browse/GERONIMO-4131 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector Affects Versions: 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2 Reporter: Kevan Miller Assignee: Jarek Gawor Fix For: 2.1.2 Attachments: GERONIMO-4131.patch A user reported problems deploying an MQ RA on Geronimo. Looks like there are several problems. 1) we don't like config-property-name values in ra.xml to start with a lower case letter 2) our mechanism for introspecting the implementation classes (e.g. managedconnectionfactory-class) is not working properly. there can be multiple set methods taking different parameter types. This is leading to type-mismatches as we try to set attributes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4131) Problems with WebSphere MQ RA deployment
[ https://issues.apache.org/jira/browse/GERONIMO-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614648#action_12614648 ] Jarek Gawor commented on GERONIMO-4131: --- I committed the latest patch to trunk (revision 677814) and branches/2.1 (revision 677816). The latest patch enables the mq connector to be deployed ok, however, there are still questions how the connector builder should be setting up the dynamic gbean attributes and so I'm leaving the bug open. Problems with WebSphere MQ RA deployment Key: GERONIMO-4131 URL: https://issues.apache.org/jira/browse/GERONIMO-4131 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector Affects Versions: 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2 Reporter: Kevan Miller Assignee: Jarek Gawor Fix For: 2.1.2 Attachments: GERONIMO-4131.patch A user reported problems deploying an MQ RA on Geronimo. Looks like there are several problems. 1) we don't like config-property-name values in ra.xml to start with a lower case letter 2) our mechanism for introspecting the implementation classes (e.g. managedconnectionfactory-class) is not working properly. there can be multiple set methods taking different parameter types. This is leading to type-mismatches as we try to set attributes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
