Re: ActiveMQ 4.1.2? 4.2? ActiveIO 3.1? releases
On Mar 25, 2008, at 10:50 PM, Jason Dillon wrote: When is G gonna upgrade to AMQ 5? Probably 2.2. The main obstacle is that we are still trying to use gbeans to assemble the activemq broker. This is pretty unsatisfactory. However using the spring xml assembly has 2 problems: - pulls in spring (not a biggie) - kill the jms console support. In fact AFAIK its pretty hard to write out a spring xml file after you've modified the components... So if we ditched the jms console we could probably do it in a day or two however I don't have a clear idea how to have a console that deals with a spring based config. Maybe some of dains jaxb magic will provide a solution soon. We might be able to have a console-free activemq 5 plugin for 2.1.1 if someone wants to take a few minutes and set it up. thanks david jencks --jason On Mar 26, 2008, at 12:28 PM, David Jencks wrote: On Mar 25, 2008, at 7:41 PM, Donald Woods wrote: Yep, I'd like to see those fixes in 2.1.1, but maybe an ActiveMQ 4.1.2 release that still supports Java 1.4 for existing stand- alone ActiveMQ users would be the best way to go for now. I didn't really consider moving to java 5 (which involves only replacing the backport-concurrent classes with the java.util.concurrent classes) until I picked up the activeio-3.1- SNAPSHOT fix which has already moved definitively to java 5. So I have no problem calling the activemq version 4.2 but keeping a java 1.4 compatibility for activemq won't let you use it on java 1.4 due to the activeio changes. I should have thought of and mentioned this in the original post... thanks david jencks -Donald Joe Bohn wrote: David Jencks wrote: Geronimo is still using ActiveMQ 4 and I've applied patches for or fixed a few bugs that are fairly important for getting MDBS working reliably and fixing other problems. So, I'd like to get a release out of the 4.x branch for the upcoming Geronimo 2.1.1 release. I agree ... it would be great to get those included in 2.1.1. I've looked through the jiras for 4.x and applied the patches for ones that I had a clue about. If anyone else wants something fixed in 4.x please speak up. ActiveIO trunk has a fix that we'd like (don't put non-strings in system properties) so I'd like to release ActiveIO 3.1 also. Since that requires java 5 I'd like to update activemq 4 to use java 5 also (I've tried and this is easy to do). What's the community feeling on this? Is this a real no-no? Would it be better to have the version 4.2 and preserve 4.1.x for java 1.4 work? I'm sure others have more informed opinions on this than I do. I personally can't think of a reason that we should need another java 1.4 release but it certainly is nice to have the option ... so I think it would make sense to do the java 5 work in a 4.2 branch. Although I have to admit that I'm getting a little nervous at all the moving parts for 2.1.1. I'd like to also update the poms to use more modern maven release procedures as well I haven't looked into this much yet and will post further when I do. thanks david jencks
[jira] Commented: (GERONIMO-3940) A easy way to create a new server instance via command/gsh/console
[ https://issues.apache.org/jira/browse/GERONIMO-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582148#action_12582148 ] David Jencks commented on GERONIMO-3940: Could you explain what you mean by new server instance? what do you want it to have in it and how will it relate to the old instance? I can think of several possibilities :-) A easy way to create a new server instance via command/gsh/console -- Key: GERONIMO-3940 URL: https://issues.apache.org/jira/browse/GERONIMO-3940 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: usability Affects Versions: 2.1.1 Reporter: YunFeng Ma Priority: Minor Fix For: 2.1.1 Provide a easy way to create a new server instance via command/gsh/console -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582150#action_12582150 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 641178. branches/1.0/migration-ejb-mdb Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582151#action_12582151 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 641179. branches/1.0/migration-ejb-session Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references
[ https://issues.apache.org/jira/browse/GERONIMO-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582152#action_12582152 ] Erik B. Craig commented on GERONIMO-3910: - Committed revision 641180. branches/1.0/migration-hibernate Rename classes, remove IBM references - Key: GERONIMO-3910 URL: https://issues.apache.org/jira/browse/GERONIMO-3910 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Critical In the migration sample apps from the 1.0 branch, there are classes named com.ibm.x. These need to be renamed to o.a.g -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3940) A easy way to create a new server instance via command/gsh/console
[ https://issues.apache.org/jira/browse/GERONIMO-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582156#action_12582156 ] YunFeng Ma commented on GERONIMO-3940: -- According to v2.1 doc (http://cwiki.apache.org/GMOxDOC21/running-multiple-instances-of-geronimo.html), users have to do the following steps to create a new server instance: 1. mkdir foo 2. Copy var to foo. 3. Edit foo/var/config/config.substitutions.properties and change the portOffset. These steps look like hacking, why shouldn't we provide a tool for these steps, compared with the efforts of implementing multiple instance function before, this tool is easy to implement, but will be more attractive to end users. Also there should be a easy way to start a server instance, instead of using org.apache.geronimo.server.name property. Any thoughts? A easy way to create a new server instance via command/gsh/console -- Key: GERONIMO-3940 URL: https://issues.apache.org/jira/browse/GERONIMO-3940 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: usability Affects Versions: 2.1.1 Reporter: YunFeng Ma Priority: Minor Fix For: 2.1.1 Provide a easy way to create a new server instance via command/gsh/console -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] Geronimo 2.1.1 release
GERONIMO-3843 (Plan creator fails to create plan and to deploy) GERONIMO-3850 (Plan Creator suppresses exceptions rather than showing it to user) are fixed. GERONIMO-3851 (Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib) involves lots of changes and I would like these to go into G2.2 instead. And I haven't been able to implement GERONIMO-3759 (tomcat clustering, no gbeans for adding static members) - still facing some problems. Can someone look into this? -- Thanks, Shiva On Fri, Mar 14, 2008 at 6:08 PM, Shiva Kumar H R [EMAIL PROTECTED] wrote: GERONIMO-3432 console wizard to generate openejb-jar.xml will only be ready by G2.2. Sorry about that. I will fix GERONIMO-3759 tomcat clustering, no gbeans for adding static members by next week. I would like the following additional ones to get into Required list of G2.1.1. I will fix them utmost by next Friday! (or will it be too late?) 1) GERONIMO-3843 Plan creator fails to create plan and to deploy 2) GERONIMO-3850 Plan Creator suppresses exceptions rather than showing it to user 3) GERONIMO-3851 Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib -- Thanks, Shiva On Fri, Mar 14, 2008 at 2:38 AM, Joe Bohn [EMAIL PROTECTED] wrote: Ok, so here is the list of things that I think were mentioned for inclusion in a 2.1.1 release (those that were not already complete when this discussion began). Am I missing anything from the required list or are there items that should move up from the Optional list (or down from required)? My take is that once we have everything under Required completed we can start the release process. Anything from the Optional list that can make it in is gravy. We need to decide when to start to lock things down, but in general I think we all know that we are getting close so please be careful what goes into the 2.1 branch now. Required: - GERONIMO-3781 PluginInstaller CRSF when installing a new plugin. - There are patches integrated for this. Is there more to be done? Joe Leong - GERONIMO-3871 archetypes for plugin and assembly. - David has already completed this. - GERONIMO-3898 log4j app config gbean. - David has already completed this. - GERONIMO-3902 start-server overrides. - Jason are you posting a patch for this? - GERONIMO-3833 monitoring hard coded gbean names. - Viet has integrated a fix - outstanding question by Jarek - GERONIMO-3837 configure allowLinking attribute - Vamsi has integrated this ... not sure if there is more work remaining. - GERONIMO-3858 start-server.bat fails if space in dir - no owner - GERONIMO-3875 Derby authentication breaks DB viewer portlet. - Vamsi assigned, still open - GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned. I'm not convinced this is a must-have. - GERONIMO-3887 bad config install for plugin causes new installs to fail. Joe Leong - are you planning to provide a patch? I'm not convinced this is a must-have - GERONIMO-3896 error processing HEAD method by default HttpServlet. David has fixed this in the servlet spec and it's up for a vote. We need to update 2.1.1 to use this spec when final. - GERONIMO-3906 start-server uses hard-coded credentials. This seems important. Is anybody working on this (nobody is assigned). - GERONIMO-3918 upgrade to WADI 2.0-M9. Donald has already completed this. Optional: - leverage genesis 1.4 - OpenEJB 3.0 - currently up for a vote - looks promising. I will give it a try with 2.1.1-SNAPSHOT. I think this should possibly move up to required (assuming no big issues are found). - GERONIMO-3432 console wizard to generate openejb-jar.xml - GERONIMO-3503 db pool wizard creates plans only for local-transactions - GERONIMO-3719 monitoring agent uses sun classes - GERONIMO-3759 tomcat clustering, no gbeans for adding static members - GERONIMO-3783 mdb delivery problem - this seems kinda important - should we move it up? - GERONIMO-3806 extraneous warning messages for ejb resource-env-def deploy - GERONIMO-3811 ejb server portlet - GERONIMO-3814 NPE in GBeanOverride - GERONIMO-3819 updates to JMS resource portlet - GERONIMO-3823 document the SystemPropertyGBean - GERONIMO-3879 webaccess log viewer with multiple server instances has issues. - GERONIMO-3900 runtime support for non-Sun JVMs. - GERONIMO-3901 security realms portlet missing encoding option Joe
[jira] Updated: (GERONIMO-3851) Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib
[ https://issues.apache.org/jira/browse/GERONIMO-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMO-3851: -- Fix Version/s: (was: 2.1.1) 2.2 Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib --- Key: GERONIMO-3851 URL: https://issues.apache.org/jira/browse/GERONIMO-3851 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.2 Attachments: jaxws-calculator-war-2.1-SNAPSHOT.war If a servlet class is packaged as a compressed JAR and put in WEB-INF/lib directory of a WAR, then plan creator will fail to recognize such class. Due to GERONIMO-3850, you may *not* notice any exceptions on console, rather Plan Creator would have simply failed to detect any references/security configurations required for the web-app. When you input such WARs to Plan Creator, you will see that after WAR - Environment page you will directly move to WAR - Dependencies page. i.e. *no* WAR-References or WAR-Security page will be shown even though the web-app requires certain references to be resolved or security roles to be defined. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (YOKO-424) Yoko default concurrency model different from other orb implementations.
Yoko default concurrency model different from other orb implementations. Key: YOKO-424 URL: https://issues.apache.org/jira/browse/YOKO-424 Project: Yoko - CORBA Server Issue Type: Bug Security Level: public (Regular issues) Components: orb core Affects Versions: v1.0.0 Reporter: Rick McGuire Assignee: Rick McGuire Fix For: v1.0.0 The yoko default concurrency model is thread_per_client, which uses a single thread for all requests coming from a client application. This can lead to deadlock situations with applications that have been ported from other ORBs because additional requests from a client get queued up behind the currently active request. This situation is EXTREMELY difficult to diagnose, since the application will just hang without any diagnostics on the situation. Neither the Sun ORB or the IBM ORB display this behavior, so the safer default concurrency model would be to use a thread pool to dispatch requests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (YOKO-424) Yoko default concurrency model different from other orb implementations.
[ https://issues.apache.org/jira/browse/YOKO-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed YOKO-424. - Resolution: Fixed Committed revision 641268. Yoko default concurrency model different from other orb implementations. Key: YOKO-424 URL: https://issues.apache.org/jira/browse/YOKO-424 Project: Yoko - CORBA Server Issue Type: Bug Security Level: public(Regular issues) Components: orb core Affects Versions: v1.0.0 Reporter: Rick McGuire Assignee: Rick McGuire Fix For: v1.0.0 The yoko default concurrency model is thread_per_client, which uses a single thread for all requests coming from a client application. This can lead to deadlock situations with applications that have been ported from other ORBs because additional requests from a client get queued up behind the currently active request. This situation is EXTREMELY difficult to diagnose, since the application will just hang without any diagnostics on the situation. Neither the Sun ORB or the IBM ORB display this behavior, so the safer default concurrency model would be to use a thread pool to dispatch requests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: DayTrader build error
Howdy,
I'm getting a somewhat similar error when building DT from trunk. Any advise?
[INFO]
[INFO] Building DayTrader :: Web Application
[INFO]task-segment: [install]
[INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Couldn't find a version in [1.0-M1] to match range [1.0,2.0)
org.apache.geronimo.specs:geronimo-jsp_2.1_spec:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 14 seconds
[INFO] Finished at: Wed Mar 26 09:40:35 EDT 2008
[INFO] Final Memory: 22M/508M
[INFO]
Cheers!
Hernan
seleshmaster wrote:
hello;
while trying to build DayTrader after getting the latest build, I am getting
the following error, anyone has any idea?
please help
thx
here is the error
seleshmaster-macbook:trunk seleshmaster$ mvn clean install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] DayTrader :: Performance Benchmark Sample
[INFO] DayTrader :: WS Application Client
[INFO] DayTrader :: EJBs
[INFO] DayTrader :: Web Application
[INFO] DayTrader :: Quote Streamer
[INFO] DayTrader :: Enterprise Application
[INFO] DayTrader :: JSON Proxy
[INFO] DayTrader :: Dojo User Interface
[INFO] DayTrader :: Dojo Interface and Proxy Ear
[INFO]
[INFO] Building DayTrader :: Performance Benchmark Sample
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory /Users/seleshmaster/workspace/trunk/target
[INFO] Deleting directory /Users/seleshmaster/workspace/trunk/target/classes
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/target/test-classes
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [site:attach-descriptor]
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] [install:install]
[INFO] Installing /Users/seleshmaster/workspace/trunk/pom.xml to
/Users/seleshmaster/.m2/repository/org/apache/geronimo/daytrader/daytrader/2.0-SNAPSHOT/daytrader-2.0-SNAPSHOT.pom
[INFO]
[INFO] Building DayTrader :: WS Application Client
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/modules/wsappclient/target
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/modules/wsappclient/target/classes
[INFO] Deleting directory
/Users/seleshmaster/workspace/trunk/modules/wsappclient/target/test-classes
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Couldn't find a version in [2.0.0] to match range [1.0,2.0)
org.apache.geronimo.specs:geronimo-jaxrpc_1.1_spec:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Mon Mar 10 22:04:36 EDT 2008
[INFO] Final Memory: 14M/26M
[INFO]
[jira] Commented: (GERONIMO-3887) After installing with wrong configuration unable to proceed with any new plugin installs
[ https://issues.apache.org/jira/browse/GERONIMO-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582296#action_12582296 ] Joseph Leong commented on GERONIMO-3887: I'll take a look at the setLoad. Right now i'm using the uninstallconfiguration(artifact) which is the procedure used to remove obsolete artifacts. I'll look further into the method to see what that entails. Thus far it seems to solve the starting issue, it seems to remove any remnants of the first failed install when starting the second plugin. I'll keep everyone updated. Joseph Leong After installing with wrong configuration unable to proceed with any new plugin installs Key: GERONIMO-3887 URL: https://issues.apache.org/jira/browse/GERONIMO-3887 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Joseph Leong Assignee: Joseph Leong Fix For: 2.1.1, 2.2 The plugin installer located in the administration console fails to install new plugins once it runs into an install that throws an exception for being the wrong configuration type. IE. trying to install a Jetty piece on Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.1: Failed for Revision: 641266
Geronimo Revision: 641266 built with tests included See the full build-0800.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080326/build-0800.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/2.1/20080326 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 31 minutes 42 seconds [INFO] Finished at: Wed Mar 26 09:02:34 EDT 2008 [INFO] Final Memory: 303M/983M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080326/logs-0800-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080326/logs-0800-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 75.675 sec FAILURE! Samples: branches/2.1 = Log: http://geronimo.apache.org/maven/server/binaries/2.1/20080326/samples-0800.log Build status: OK
[jira] Updated: (GERONIMODEVTOOLS-266) GEP automation testsuite
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated GERONIMODEVTOOLS-266: --- Attachment: GERONIMO-259a.patch This patch contains the testcases for org.apache.geronimo.st.v21.core.operations. These have to be run as a junit plugin test. I am looking at how to get maven to call these properly (since they are not regular junit tests) so that they can be run during builds. More patches to follow. GEP automation testsuite Key: GERONIMODEVTOOLS-266 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-266 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell Attachments: GERONIMO-259a.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-314) Fix warning messages in JAXB-generated classes
Fix warning messages in JAXB-generated classes -- Key: GERONIMODEVTOOLS-314 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-314 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-314) Fix warning messages in modified JAXB classes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMODEVTOOLS-314: --- Component/s: eclipse-plugin Summary: Fix warning messages in modified JAXB classes (was: Fix warning messages in JAXB-generated classes) Fix warning messages in modified JAXB classes - Key: GERONIMODEVTOOLS-314 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-314 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-315) Remove generation of JAXB classes for v21 plugins
Remove generation of JAXB classes for v21 plugins - Key: GERONIMODEVTOOLS-315 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-315 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3887) After installing with wrong configuration unable to proceed with any new plugin installs
[ https://issues.apache.org/jira/browse/GERONIMO-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Leong updated GERONIMO-3887: --- Attachment: GERONIMO-3887.patch Patch posted. This patch also resolves issue mentioned in GERONIMO-3939 After installing with wrong configuration unable to proceed with any new plugin installs Key: GERONIMO-3887 URL: https://issues.apache.org/jira/browse/GERONIMO-3887 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Joseph Leong Assignee: Joseph Leong Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3887.patch The plugin installer located in the administration console fails to install new plugins once it runs into an install that throws an exception for being the wrong configuration type. IE. trying to install a Jetty piece on Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3939) Failing to start plugin after install if previous plugin install failed.
[ https://issues.apache.org/jira/browse/GERONIMO-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582400#action_12582400 ] Joseph Leong commented on GERONIMO-3939: The resolution for this issue has been consolidated into the patch posted at GERONIMO-3887 ! Please refer to that JIRA for further updates regarding the two issues. -Joseph Leong Failing to start plugin after install if previous plugin install failed. Key: GERONIMO-3939 URL: https://issues.apache.org/jira/browse/GERONIMO-3939 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Environment: Ubuntu 7.10, Firefox Reporter: Joseph Leong Assignee: Joseph Leong Fix For: 2.1.1, 2.2 The admin console plugin installer fails to start a plugin after install under the condition that a previous plugin install failed. The plugin installer is hung on the cache of the previous failed install and won't start or show the progress of the new plugin install. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3887) After installing with wrong configuration unable to proceed with any new plugin installs
[ https://issues.apache.org/jira/browse/GERONIMO-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Leong updated GERONIMO-3887: --- Patch Info: [Patch Available] After installing with wrong configuration unable to proceed with any new plugin installs Key: GERONIMO-3887 URL: https://issues.apache.org/jira/browse/GERONIMO-3887 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Joseph Leong Assignee: Joseph Leong Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3887.patch The plugin installer located in the administration console fails to install new plugins once it runs into an install that throws an exception for being the wrong configuration type. IE. trying to install a Jetty piece on Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.1: Failed for Revision: 641434
Geronimo Revision: 641434 built with tests included See the full build-1400.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080326/build-1400.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/2.1/20080326/unit-test-reports Building Geronimo branches/2.1 at Revision: 641434 java version 1.5.0_08 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03) Java HotSpot(TM) Server VM (build 1.5.0_08-b03, mixed mode) + Error stacktraces are turned on. [INFO] Scanning for projects... Downloading: http://download.java.net/maven/1//org.apache.geronimo.genesis.config/poms/project-config-1.3.pom Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/genesis/config/project-config/1.3/project-config-1.3.pom [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.geronimo.genesis.config ArtifactId: project-config Version: 1.3 Reason: Unable to download the artifact from any repository org.apache.geronimo.genesis.config:project-config:pom:1.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache.geronimo.genesis.config:project-config for project: org.apache.geronimo:geronimo:pom:2.1.1-SNAPSHOT for project org.apache.geronimo:geronimo:pom:2.1.1-SNAPSHOT at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) 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(DelegatingMethodAccessorImpl.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.project.ProjectBuildingException: Cannot find parent: org.apache.geronimo.genesis.config:project-config for project: org.apache.geronimo:geronimo:pom:2.1.1-SNAPSHOT for project org.apache.geronimo:geronimo:pom:2.1.1-SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1261) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:747) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:553) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364) ... 11 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.geronimo.genesis.config:project-config' not found in repository: Unable to download the artifact from any repository org.apache.geronimo.genesis.config:project-config:pom:1.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository) for project org.apache.geronimo.genesis.config:project-config at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:573) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1257) ... 17 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.apache.geronimo.genesis.config:project-config:pom:1.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:197
[jira] Updated: (GERONIMO-3887) After installing with wrong configuration unable to proceed with any new plugin installs
[ https://issues.apache.org/jira/browse/GERONIMO-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Leong updated GERONIMO-3887: --- Attachment: GERONIMO-3887-2.patch My mistake, moved the try / catch inside the loop. Patch 2 posted. After installing with wrong configuration unable to proceed with any new plugin installs Key: GERONIMO-3887 URL: https://issues.apache.org/jira/browse/GERONIMO-3887 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Joseph Leong Assignee: Joseph Leong Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3887-2.patch, GERONIMO-3887.patch The plugin installer located in the administration console fails to install new plugins once it runs into an install that throws an exception for being the wrong configuration type. IE. trying to install a Jetty piece on Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Hibernate transaction manager lookup
Quoting David Jencks [EMAIL PROTECTED]: On Mar 25, 2008, at 3:39 PM, Jonas Andersen wrote: Hi, Having played around with Geronimo 2.0.2, Spring and Hibernate a bit for the last couple of days, I have attached a transaction manager lookup for Geronimo to the Hibernate JIRA HHH-1368 ( http:// opensource.atlassian.com/projects/hibernate/browse/HHH-1368 ). Considering how simple this class is, for how long that JIRA has been open, and how little information I have been able to find on using Hibernate with Geronimo, I'm curious as to whether I'm missing something critical? Anyone have any comments on using Hibernate with the java:comp/ UserTransaction and java:/TransactionManager? I should warn, that I have only been doing a bit of testing, doing simple select and insert (through a Hibernate Session of course) in an EBJ3 SLSB with CMT. I've been wondering for a while why this should be necessary are you using Hibernate as a jpa provider or using the non-standard interfaces? I would expect no such adapter should be necessary using Hibernate as a jpa provider. If you are using the non-standard interfaces I'm curious what they provide that isn't available through jpa. I'm using Hibernate Core (non-standard). Looking into using OpenJPA or an alternative such as Hibernate EntityManager, is on my to-do list. I just wanted to get the familiar Spring+Hibernate (Core) running first. As such, I can't say to what extend (if any) I need to use Hibernate Core instead of JPA. Is there any reason why Hibernate Core shouldn't be supported on Geronimo (implied it uses Geronimo managed DataSource and JTA/CMT transactions)? Seems to me that the Spring+Hibernate combination is pretty common. Best regards, Jonas Andersen
[jira] Created: (GERONIMODEVTOOLS-316) intermittent Geronimo Deployment 1.2 cannot be installed. error message from the Eclipse Project Facets wizard
intermittent Geronimo Deployment 1.2 cannot be installed. error message from the Eclipse Project Facets wizard Key: GERONIMODEVTOOLS-316 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-316 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Hibernate transaction manager lookup
On Mar 26, 2008, at 1:12 PM, Jonas Andersen wrote: Quoting David Jencks [EMAIL PROTECTED]: On Mar 25, 2008, at 3:39 PM, Jonas Andersen wrote: Hi, Having played around with Geronimo 2.0.2, Spring and Hibernate a bit for the last couple of days, I have attached a transaction manager lookup for Geronimo to the Hibernate JIRA HHH-1368 ( http:// opensource.atlassian.com/projects/hibernate/browse/ HHH-1368 ). Considering how simple this class is, for how long that JIRA has been open, and how little information I have been able to find on using Hibernate with Geronimo, I'm curious as to whether I'm missing something critical? Anyone have any comments on using Hibernate with the java:comp/ UserTransaction and java:/TransactionManager? I should warn, that I have only been doing a bit of testing, doing simple select and insert (through a Hibernate Session of course) in an EBJ3 SLSB with CMT. I've been wondering for a while why this should be necessary are you using Hibernate as a jpa provider or using the non-standard interfaces? I would expect no such adapter should be necessary using Hibernate as a jpa provider. If you are using the non-standard interfaces I'm curious what they provide that isn't available through jpa. I'm using Hibernate Core (non-standard). Looking into using OpenJPA or an alternative such as Hibernate EntityManager, is on my to-do list. I just wanted to get the familiar Spring+Hibernate (Core) running first. As such, I can't say to what extend (if any) I need to use Hibernate Core instead of JPA. Is there any reason why Hibernate Core shouldn't be supported on Geronimo (implied it uses Geronimo managed DataSource and JTA/CMT transactions)? Seems to me that the Spring+Hibernate combination is pretty common. I have no problem with supporting Hibernate Core on geronimo, I was curious about whether there was something in the hibernate JPA support that required a transaction manager jndi lookup as I think this is not expected by the jpa spec. IIUC you have not tested that yet :-) thanks david jencks Best regards, Jonas Andersen
Re: [DISCUSS] Geronimo 2.1 samples
Joe Bohn wrote: Jarek Gawor wrote: On Tue, Mar 11, 2008 at 1:20 PM, Joe Bohn [EMAIL PROTECTED] wrote: 5) Should we make all samples plugins? At the moment the jsp-examples, servlet-examples, and ldap-sample-app are plugins. The other 12 samples are not. I'd be in favor of creating a plugin for each and will work on doing this unless I hear objections. I created plugins for all the samples in trunk only. I tested most of them on jetty only so I would appreciate people trying them on Tomcat. The samples that require database you will still need to follow the directions in the sample wiki to create the database and the tables. I'm actaully still debating if I should add in the gbean to the ear descriptors to create the databases automatically or not (any thoughts on that?). I also published all the samples so you should be able to install the plugins remotely using http://geronimo.apache.org/plugins/geronimo-2.2/ repo. Once the plugins look good to everyone we can merge them into branches/2.1. Thanks Jarek ... I think it's great to have the plugin option for those installing samples. I'll see if I can give them a try with a tomcat server later today. Regarding the creation of the database and tables; I think it probably depends on the sample and what it is trying to convey. Perhaps I'll have a more informed opinion after I try the sample plugins out on a Tomcat server. However, if creating the database is central to the purpose of the sample it is probably best not to mask or confuse this via the gbean. Adding the gbean will impact not only those leveraging the plugin but also those that are following the detailed steps for the sample. Ok, I finally got around to trying out some of the samples on tomcat. The ones I tried worked just fine. I'll attempt to try them all just in case there is an issue with one. I personally don't see any value in keeping the definition of the database items manual and I think it would be great if we defined those via the gbean in the ears. I didn't walk through all of the samples but it doesn't appear to me that defining the db elements is of any value to the user of the samples. We can still describe what the gbean is doing for those that are curious. Joe
Re: [DISCUSS] Geronimo 2.1 samples
Joe Bohn wrote: Joe Bohn wrote: Jarek Gawor wrote: On Tue, Mar 11, 2008 at 1:20 PM, Joe Bohn [EMAIL PROTECTED] wrote: 5) Should we make all samples plugins? At the moment the jsp-examples, servlet-examples, and ldap-sample-app are plugins. The other 12 samples are not. I'd be in favor of creating a plugin for each and will work on doing this unless I hear objections. I created plugins for all the samples in trunk only. I tested most of them on jetty only so I would appreciate people trying them on Tomcat. The samples that require database you will still need to follow the directions in the sample wiki to create the database and the tables. I'm actaully still debating if I should add in the gbean to the ear descriptors to create the databases automatically or not (any thoughts on that?). I also published all the samples so you should be able to install the plugins remotely using http://geronimo.apache.org/plugins/geronimo-2.2/ repo. Once the plugins look good to everyone we can merge them into branches/2.1. Thanks Jarek ... I think it's great to have the plugin option for those installing samples. I'll see if I can give them a try with a tomcat server later today. Regarding the creation of the database and tables; I think it probably depends on the sample and what it is trying to convey. Perhaps I'll have a more informed opinion after I try the sample plugins out on a Tomcat server. However, if creating the database is central to the purpose of the sample it is probably best not to mask or confuse this via the gbean. Adding the gbean will impact not only those leveraging the plugin but also those that are following the detailed steps for the sample. Ok, I finally got around to trying out some of the samples on tomcat. The ones I tried worked just fine. I'll attempt to try them all just in case there is an issue with one. I personally don't see any value in keeping the definition of the database items manual and I think it would be great if we defined those via the gbean in the ears. I didn't walk through all of the samples but it doesn't appear to me that defining the db elements is of any value to the user of the samples. We can still describe what the gbean is doing for those that are curious. Just noticed one more thing ... not sure if it is related to the samples themselves or the plugins of the samples specifically ... but the links for javadoc and source code don't work. Joe
[jira] Updated: (GSHELL-101) Implement command context
[ https://issues.apache.org/jira/browse/GSHELL-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GSHELL-101: Attachment: GShell-101.patch Patch. Added new file ContextCommand.java. This implements the ability to change context. The command is not actually necessary to change the context. You can just type the new context you want and as long as it's a valid path, the context will be changed automatically. The command can also be used to make the change (i,e. context optional). I also added an option for the context command to display the current context (context -c). Implement command context - Key: GSHELL-101 URL: https://issues.apache.org/jira/browse/GSHELL-101 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Support - CLP Affects Versions: 1.0-alpha-2, 1.0-alpha-3 Reporter: Jason Warner Assignee: Jason Warner Fix For: 1.0-alpha-2, 1.0-alpha-3 Attachments: GShell-101.patch Gshell current lacks the ability to change the context from which a command is run. All commands default to running from a root directory. To be able to launch a command without fully qualifying (i.e; /bsf/script), the command search path must be used. It would be nice if we could also changed the context such that we can run any bsf command (or other command group commands) without having to modify the command search path. This will also allow us to use relative command paths (../ and ./). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-317) CoreException when creating Enterprise Application Project
CoreException when creating Enterprise Application Project -- Key: GERONIMODEVTOOLS-317 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-317 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-317) CoreException when creating Enterprise Application Project
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated GERONIMODEVTOOLS-317:
---
Description:
When creating an Enterprise Applicaiton Project, and not setting the Generate
Deployment Descriptor checkbox, a CoreException will result. The trace and
exception stacktrace is as below:
org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.55.531 --
ServerResourceChangeListener responding to resource change: 16 --
org.eclipse.wst.server.core FINEST26/03/08 19:12.55.531 Loading project
preferences: P/test3
org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.55.531 Not a server
project: test3
org.eclipse.wst.server.core FINEST26/03/08 19:12.55.531
publishHandleProjectChange P/test3
org.eclipse.wst.server.core FINEST26/03/08 19:12.55.531 -
publishHandleProjectChange
org.eclipse.wst.server.core FINEST26/03/08 19:12.55.531
publishHandleProjectChange
org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.55.531 -- Done
ServerResourceChangeListener responding to resource change --
org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.56.546 --
ServerResourceChangeListener responding to resource change: 16 --
org.eclipse.wst.server.core FINEST26/03/08 19:12.56.546 Loading project
preferences: P/test3
org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.56.546 Not a server
project: test3
org.eclipse.wst.server.core FINEST26/03/08 19:12.56.546
publishHandleProjectChange P/test3
org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.56.546 -- Done
ServerResourceChangeListener responding to resource change --
org.apache.geronimo.st.ui: ENTRY:
SharedDeploymentPlanEditor.loadDeploymentPlan(
parm1=[L/test3/EarContent/META-INF/geronimo-application.xml] )
org.apache.geronimo.st.ui: ENTRY: SharedDeploymentPlanEditor.getLoader()
org.apache.geronimo.st.ui: EXIT: SharedDeploymentPlanEditor.getLoader( [EMAIL
PROTECTED] )
org.apache.geronimo.st.core: ENTRY: GeronimoV21Utils.getDeploymentPlan(
parm1=[L/test3/EarContent/META-INF/geronimo-application.xml] )
org.apache.geronimo.st.core: ENTRY:
GeronimoV21Utils.getApplicationDeploymentPlan(
parm1=[L/test3/EarContent/META-INF/geronimo-application.xml] )
org.apache.geronimo.st.ui: EXIT:
SharedDeploymentPlanEditor.loadDeploymentPlan( [EMAIL PROTECTED] )
org.apache.geronimo.st.ui: ENTRY: SharedDeploymentPlanEditor.doAddPages()
org.apache.geronimo.st.ui: ENTRY: SharedDeploymentPlanEditor.getLoader()
org.apache.geronimo.st.ui: EXIT: SharedDeploymentPlanEditor.getLoader( [EMAIL
PROTECTED] )
org.apache.geronimo.st.ui: EXIT: SharedDeploymentPlanEditor.doAddPages()
org.apache.geronimo.st.v21.core: Entry/Exit:
DeploymentPlanInstallConfig.create()
org.apache.geronimo.st.v21.core: Entry/Exit:
DeploymentPlanInstallConfig.create()
org.apache.geronimo.st.v21.ui: Constructor Entry: FacetInstallPage()
org.apache.geronimo.st.v21.ui: Constructor Exit: FacetInstallPage()
org.apache.geronimo.st.v21.ui: Entry: FacetInstallPage.setConfig( [EMAIL
PROTECTED] )
org.apache.geronimo.st.v21.ui: Exit: FacetInstallPage.setConfig()
org.apache.geronimo.st.v21.ui: Entry: FacetInstallPage.createControl(
parm1=[Composite {}] )
org.apache.geronimo.st.v21.ui: Exit: FacetInstallPage.createControl()
org.apache.geronimo.st.v21.ui: Entry: FacetInstallPage.transferStateToConfig()
org.apache.geronimo.st.v21.ui: Exit: FacetInstallPage.transferStateToConfig()
org.apache.geronimo.st.v21.core: Entry:
GeronimoV21FacetInstallDelegate.createDeploymentPlanCreationOp(
parm1=[P/test34], [EMAIL PROTECTED] )
org.apache.geronimo.st.v21.core: Exit :
GeronimoV21FacetInstallDelegate.createDeploymentPlanCreationOp()
org.apache.geronimo.st.v21.core: Constructor Entry/Exit:
V21DeploymentPlanCreationOperation( parm1=[IDataModel, [EMAIL PROTECTED],
[EMAIL PROTECTED] )
org.apache.geronimo.st.v21.core: Entry:
V21DeploymentPlanCreationOperation.createGeronimoApplicationDeploymentPlan(
parm1=[L/test34/EarContent/META-INF/geronimo-application.xml] )
org.apache.geronimo.st.v21.core: Entry:
V21DeploymentPlanCreationOperation.getConfigEnvironment()
org.apache.geronimo.st.v21.core: Entry:
V21DeploymentPlanCreationOperation.hasValue( parm1=[default] )
org.apache.geronimo.st.v21.core: Exit :
V21DeploymentPlanCreationOperation.hasValue( parm1=[true] )
org.apache.geronimo.st.v21.core: Entry:
V21DeploymentPlanCreationOperation.hasValue( parm1=[] )
org.apache.geronimo.st.v21.core: Exit :
V21DeploymentPlanCreationOperation.hasValue( parm1=[false] )
org.apache.geronimo.st.v21.core: Entry:
V21DeploymentPlanCreationOperation.hasValue( parm1=[1.0] )
org.apache.geronimo.st.v21.core: Exit :
V21DeploymentPlanCreationOperation.hasValue( parm1=[true] )
org.apache.geronimo.st.v21.core: Entry:
V21DeploymentPlanCreationOperation.hasValue( parm1=[car] )
org.apache.geronimo.st.v21.core: Exit :
V21DeploymentPlanCreationOperation.hasValue(
[jira] Created: (GERONIMODEVTOOLS-318) Support for geronimo-application-client.xml
Support for geronimo-application-client.xml --- Key: GERONIMODEVTOOLS-318 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-318 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-318) Support for geronimo-application-client.xml missing in GEP UI (although supported in various plugin.xml files)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMODEVTOOLS-318: --- Summary: Support for geronimo-application-client.xml missing in GEP UI (although supported in various plugin.xml files) (was: Support for geronimo-application-client.xml) Support for geronimo-application-client.xml missing in GEP UI (although supported in various plugin.xml files) -- Key: GERONIMODEVTOOLS-318 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-318 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
