Re: Apache Roller v4.0 plugin
Peter Petersson wrote: David Jencks wrote: On Jul 21, 2007, at 8:11 AM, Peter Petersson wrote: Considering the tight schedule and the work that needs to be done i G to add functionality to the plugin system for smooth and automatic artifact alias switching and my latest findings surrounding this regarding the roller plugin ( see https://issues.apache.org/jira/browse/GERONIMO-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514407 ) i propose the following changes and arrangement of the roller plugin modules * roller-jetty-derby (in new branch for Gv2.0 release) * roller-tomcat-derby (in new branch) * roller-jetty-mysql (in new branch) * roller-tomcat-mysql (in new branch) * roller-jetty (in trunk for future release) * roller-tomcat (in trunk) * roller-derby-database (in branch and trunk) * roller-derby-resources (in branch and trunk) * roller-mysql-database (in branch and trunk) * roller-mysql-resources (in branch and trunk) * roller-war (in branch and trunk) Additional files 2 separate geronimo-plugin.xml files in branch an trunk respectively. By setting up the new modules listed above to depend on there respective database modules and jpa settings they will not be far away from ready for plugin usage (without aliasing) not long after G v2.0 and Roller v4.0 release and we will be able to continue working on the artifact aliasing switch for plugins on the roller-jetty and roller-tomcat modules. This implies changing the geronimo-plugin.xml file to include only the for new modules for the first incarnation of the roller G plugins until things are ready for aliasing switch usage. We could also branch the roller-plugin repository as shown above to make the intention and usage of the modules clearer. This is just a suggestion (and me being a bit eager to get something out). This is a minor change (that I am naturally willing to participate in) but once again ;) it may have implications I haven't thought of, so it may still not be the best way to go ahead, thoughts ? In future releases of the roller plugin we should look in to including the roller planet subsystem and other enhancements like contributed themes and adding more roller supported databases. I appear to have planet working, I updated the ROL-1482 jira for this, and the derby resources jar. I'm not sure how to tell if planet is actually working, but administering it doesn't generate any errors :-) This is great news. I think we should look at removing the resources jars, putting the override properties files perhaps in our war (?), and using the built-in roller schema creation (installation.type=auto). It would also be great to get the roller files into the g. var directory and expose some of the properties file configuration somehow in a gbean or the admin console. Yes it would be nice to have the properties files easy accessible by users as we no longer have any useful information in the override properties file it could as well reside in the war. Is there any gbeans that exposes properties to web apps. from these locations, or something similar, available that I can take a look at ? I was a bit unclear here. When we get things into g:s var directory I think the only properties file we need to expose is the override properties file. There will also be roller account specific indexing, cashing and other files that are best contained here, most of (if not all) which are path configurable from the override properties file and should if possible be defaulting to g:s var directory. As I noted in the geronimo jira I think we can sidestep the DBDictionary problem by leaving out the property in web.xml and letting openjpa figure out for itself what db is being used. I will test this tomorrow after updating to your new roler jira :) by removing the db ref in web.xml and downgrading the schema version to 2.4 and test the artifact aliasing switch without any specific DBDictionary property set. The concern I have with the roller-jetty and roller-tomcat modules is not just the jpa dictionary settings but also the database dependency settings. I don't think I understand your proposal above. Maybe we have different assumptions about how the roller plugin will be released. I've been wanting since the plugins were invented to distribute a lot of geronimo as plugins, each on its own release cycle. So I was thinking that the roller plugin(s) would get released separately from geronimo after g. 2.0 was out, and that the maven projects for them would remain under plugins/roller. We might need trunk + tags + branches :-). Is this what you were thinking? Yes this is what I am thinking. The intention of my proposal was to not depend on aliasing on the first releases of the roller plugin (when ever it is ready) as I have the impression it would require changes to Greonimo system modules for smooth usage, hence the short time table, but maybe it could be
[jira] Commented: (GERONIMO-2994) Apache Roller plugin
[ https://issues.apache.org/jira/browse/GERONIMO-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514478 ] Peter Petersson commented on GERONIMO-2994: --- Roller using the wrong database dictionary after aliasing After installing roller-tomcat, roller-mysql and manually setting the org.apache.geronimo.plugins/roller-derby-database//car=org.apache.geronimo.plugins/roller-mysql-database/2.0-SNAPSHOT/car line in artifact_aliases.properties and restarting the G server to make it read the aliasing line to use mysql, roller is using the wrong database dictionary settings _15:37:22,368 INFO [JDBC] Using dictionary class org.apache.openjpa.jdbc.sql.DerbyDictionary_ resulting in the wrong database schema tables being created in the mysql database using rollers installation.type=auto property. The persistence setting used (in roller-tomcat) is as follows: persistence-unit name=RollerPU providerorg.apache.openjpa.persistence.PersistenceProviderImpl/provider jta-data-sourcejdbc/rollerdb/jta-data-source non-jta-data-sourcejdbc/NoTxrollerdb/non-jta-data-source properties !-- property name=openjpa.jdbc.DBDictionary value=org.apache.openjpa.jdbc.sql.DerbyDictionary/-- !-- property name=openjpa.jdbc.SynchronizeMappings value=buildSchema(ForeignKeys=true)/-- property name=openjpa.jdbc.SynchronizeMappings value=/ property name=openjpa.Sequence value=table(Table=OPENJPASEQ, Increment=100)/ /properties /persistence-unit One potiential reason for this error may indirectly be the dependancy on the roller-derby-database in the roller-tomcat module I am not sure of this but the same settings and db creation strategy works for configuration not requiring a aliasing switch (test module roller-tomcat-mysql) that have a dependency on the roller-mysql-database, except for the incompatible entity and schema definitions (field size differences) previously noted by David Jenks. Also tried override settings by adding a mysql specific persistence.xml file in roller-mysql-resources but I still get the same errors so I may not have got it to overriding stuff correctly. 15:37:14,565 INFO [DatabaseInstaller] Creating Roller Weblogger database tables. 15:37:22,221 INFO [WebloggerFactory] Bootstrapping Roller Weblogger business tier 15:37:22,221 INFO [WebloggerFactory] Weblogger Provider = org.apache.roller.weblogger.business.GuiceWebloggerProvider 15:37:22,228 INFO [DatabaseProvider] SUCCESS: Got parameters. Using configuration type JNDI_NAME 15:37:22,228 INFO [DatabaseProvider] -- Using JNDI datasource name: java:comp/env/jdbc/rollerdb 15:37:22,231 INFO [DatabaseProvider] SUCCESS: located JNDI DataSource [java:comp/env/jdbc/rollerdb] 15:37:22,245 INFO [IndexManagerImpl] search enabled: true 15:37:22,246 INFO [IndexManagerImpl] index dir: /root/roller_data/search-index 15:37:22,273 INFO [ReferrerQueueManagerImpl] Instantiating Referrer Queue Manager 15:37:22,273 INFO [ReferrerQueueManagerImpl] Asynchronous referrer processing = false 15:37:22,274 INFO [ThreadManagerImpl] Instantiating Thread Manager 15:37:22,285 INFO [WebloggerFactory] Roller Weblogger business tier successfully bootstrapped 15:37:22,285 INFO [WebloggerFactory]Version: 4.0-dev 15:37:22,285 INFO [WebloggerFactory]Revision: 557441 15:37:22,285 INFO [WebloggerImpl] Initializing Roller Weblogger business tier 15:37:22,292 INFO [Runtime] Starting OpenJPA 1.0.0-SNAPSHOT 15:37:22,368 INFO [JDBC] Using dictionary class org.apache.openjpa.jdbc.sql.DerbyDictionary. 15:37:25,278 INFO [JPAPropertiesManagerImpl] Found uninitialized property site.name ... setting value to [Roller Site] 15:37:25,278 INFO [JPAPropertiesManagerImpl] Found uninitialized property site.shortName ... setting value to [Front Page] 15:37:25,278 INFO [JPAPropertiesManagerImpl] Found uninitialized property site.description ... setting value to [A default install of the Roller Weblogger open source blog server] 15:37:25,278 INFO [JPAPropertiesManagerImpl] Found uninitialized property site.frontpage.weblog.handle ... setting value to [] 15:37:25,278 INFO [JPAPropertiesManagerImpl] Found uninitialized property site.frontpage.weblog.aggregated ... setting value to [false] 15:37:25,278 INFO [JPAPropertiesManagerImpl] Found uninitialized property site.adminemail ... setting value to [] 15:37:25,279 INFO [JPAPropertiesManagerImpl] Found uninitialized property site.absoluteurl ... setting value to [] 15:37:25,279 INFO [JPAPropertiesManagerImpl] Found uninitialized property pings.suspendPingProcessing ... setting value to [false] 15:37:25,279 INFO [JPAPropertiesManagerImpl] Found uninitialized property site.debugMode ... setting value to [false] 15:37:25,279 INFO [JPAPropertiesManagerImpl] Found uninitialized property
[jira] Commented: (GERONIMO-2994) Apache Roller plugin
[ https://issues.apache.org/jira/browse/GERONIMO-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514483 ] David Jencks commented on GERONIMO-2994: OK, so if you remove the DBDictionary property from all the persistence.xmls then the default value of Derby set in the persistence deployer plan gets used. I'm going to put the default property settings in config.xml. We could extract the default database into config.substitutions.properties but I don't want to bloat the properties file. Apache Roller plugin - Key: GERONIMO-2994 URL: https://issues.apache.org/jira/browse/GERONIMO-2994 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.2 Reporter: Peter Petersson Assignee: David Jencks Priority: Minor Attachments: geronimo-plugins.xml, geronimo-plugins.xml, geronimo-plugins_070602.xml, geronimo-web.xml, geronimo-web.xml, plan.xml, PluginInstallerGBean.patch, pom.xml, pom.xml, roller-custom.properties, roller-custom.properties, roller-custom.properties, roller-derbydb-plan-g1_2.xml, roller-mysql-db-plan-1-2.xml, roller070409.patch, roller12_070602.zip, roller_g20_svn_070602.patch, roller_plugin.patch, roller_plugin_070717.patch Have been working on getting Apache Roller running under Geronimo I finally got to the point where the roller application seems to be running smoothly in Geronimo v1.2 (current snapshot). It would be great to eventually see this application as a plugin in G so here are pointers to resources and attached plans. Apache Roller v3.1 Resources (soon to be released) Apache roller home: http://rollerweblogger.org/project/ The bundle: http://people.apache.org/~snoopdave/apache-roller-3.1/ (until it will be available directly via roller home) Required jars: https://roller.dev.java.net/servlets/ProjectDocumentList?expandFolder=6959folderID=0 Path to database create scripts can be found in the bundle above under: apache-roller-3.1/webapp/roller/WEB-INF/dbscripts/ I have tested with the derby database and mysql 5. There is currently a issue with G v1.2 and hibernates v3.1 (used by roller 3.1) property loader that gets a FATAL [HibernateRollerImpl] Error initializing Hibernate java.lang.ClassCastException: java.util.HashSet at org.hibernate.util.PropertiesHelper.resolvePlaceHolders(PropertiesHelper.java:88) Hibernate is expecting a String value (This issue is fixed in hibernate 3.2 with a instanceOf check) Fortunately David Jencks hit this problem in trunk and suggested turning off the activemq and activemq-broker modules in config.xml, to test things out, and after that everything was running smothly :). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Simpler config-substitutions.properties keys?
I noticed all the keys (except portOffset) in config- substitions.properties start with Plan which seems redundant obvious and confusing. Anyone object if I remove this prefix? e.g. instead of PlanServerHostname=0.0.0.0 PlanNamingPort=1099 PlanOpenEJBPort=4201 PlanClientAddresses=127.0.0.1 ServerHostname=0.0.0.0 NamingPort=1099 OpenEJBPort=4201 ClientAddresses=127.0.0.1 thanks david jencks
Re: Simpler config-substitutions.properties keys?
No objection. Vamsi On 7/22/07, David Jencks [EMAIL PROTECTED] wrote: I noticed all the keys (except portOffset) in config- substitions.properties start with Plan which seems redundant obvious and confusing. Anyone object if I remove this prefix? e.g. instead of PlanServerHostname=0.0.0.0 PlanNamingPort=1099 PlanOpenEJBPort=4201 PlanClientAddresses=127.0.0.1 ServerHostname=0.0.0.0 NamingPort=1099 OpenEJBPort=4201 ClientAddresses=127.0.0.1 thanks david jencks
Shouldn't list of integrated projects in console be updated?
I don't think openejb is even in the list nor cxf nor axis2... anything else? thanks david jencks
Re: Shouldn't list of integrated projects in console be updated?
Maybe it should be generated so its always current? --jason -Original Message- From: David Jencks [EMAIL PROTECTED] Date: Sun, 22 Jul 2007 10:57:26 To:Geronimo Dev List (JIRA) dev@geronimo.apache.org Subject: Shouldn't list of integrated projects in console be updated? I don't think openejb is even in the list nor cxf nor axis2... anything else? thanks david jencks
[BUILD] TRUNK: Failed for Revision: 558521
OpenEJB trunk at 0 Geronimo Revision: 558521 built with tests skipped See the full build-1400.log file at http://people.apache.org/~prasad/binaries/20070722/build-1400.log [WARNING] POM for 'org.apache.openejb:openejb-core:pom:3.0.0-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM [INFO] snapshot org.apache.xbean:xbean-finder:3.0-SNAPSHOT: checking for updates from apache-snapshots [INFO] snapshot org.apache.xbean:xbean-finder:3.0-SNAPSHOT: checking for updates from codehaus-snapshots [INFO] snapshot org.apache.xbean:xbean-finder:3.0-SNAPSHOT: checking for updates from apache.snapshots Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/xbean/xbean-finder/3.0-SNAPSHOT/xbean-finder-3.0-20070417.194037-22.pom 2K downloaded [WARNING] POM for 'org.apache.openejb:openejb-core:pom:3.0.0-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/openejb/openejb-core/3.0.0-SNAPSHOT/openejb-core-3.0.0-20070711.214947-4.jar 993K downloaded Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/javamail/geronimo-javamail_1.4_mail/1.1-SNAPSHOT/geronimo-javamail_1.4_mail-1.1-20070302.012714-1.jar 298K downloaded Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/javamail/geronimo-javamail_1.4_provider/1.1-SNAPSHOT/geronimo-javamail_1.4_provider-1.1-20070302.012714-1.jar 109K downloaded Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/specs/geronimo-javamail_1.4_spec/1.0-SNAPSHOT/geronimo-javamail_1.4_spec-1.0-20070301.095721-5.jar 189K downloaded Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/openejb/openejb-ejbd/3.0.0-SNAPSHOT/openejb-ejbd-3.0.0-20070711.214947-4.jar 26K downloaded Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/openejb/openejb-client/3.0.0-SNAPSHOT/openejb-client-3.0.0-20070711.214947-4.jar 110K downloaded Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/openejb/openejb-server/3.0.0-SNAPSHOT/openejb-server-3.0.0-20070711.214947-4.jar 37K downloaded Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/xbean/xbean-finder/3.0-SNAPSHOT/xbean-finder-3.0-20070417.194037-22.jar 33K downloaded Downloading: http://download.java.net/maven/1//org.apache.geronimo.specs/jars/geronimo-activation_1.1_spec-1.0-M1.jar [WARNING] Unable to get resource 'org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0-M1' from repository java.net (http://download.java.net/maven/1/) Downloading: http://people.apache.org/repo/m2-incubating-repository//org/apache/geronimo/specs/geronimo-activation_1.1_spec/1.0-M1/geronimo-activation_1.1_spec-1.0-M1.jar [WARNING] Unable to get resource 'org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0-M1' from repository apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) Downloading: http://repository.codehaus.org/org/apache/geronimo/specs/geronimo-activation_1.1_spec/1.0-M1/geronimo-activation_1.1_spec-1.0-M1.jar [WARNING] Unable to get resource 'org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0-M1' from repository codehaus (http://repository.codehaus.org) Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-activation_1.1_spec/1.0-M1/geronimo-activation_1.1_spec-1.0-M1.jar 33K downloaded [INFO] [compiler:compile] [INFO] Compiling 21 source files to /home/prasad/geronimo/trunk/modules/geronimo-openejb/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/prasad/geronimo/trunk/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[71,33] package org.apache.openejb.loader does not exist /home/prasad/geronimo/trunk/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/MEJBGBean.java:[27,30] package org.apache.openejb.jee does not exist /home/prasad/geronimo/trunk/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/MEJBGBean.java:[28,30] package org.apache.openejb.jee does not exist /home/prasad/geronimo/trunk/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/EntityManagerRegistryImpl.java:[33,33] package org.apache.openejb.loader does not exist /home/prasad/geronimo/trunk/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/EjbDaemonGBean.java:[27,33] package org.apache.openejb.loader does not exist /home/prasad/geronimo/trunk/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java:[107,8] cannot find symbol symbol : class SystemInstance location: class
Re: Simpler config-substitutions.properties keys?
+1 Jacek On 7/22/07, David Jencks [EMAIL PROTECTED] wrote: I noticed all the keys (except portOffset) in config- substitions.properties start with Plan which seems redundant obvious and confusing. Anyone object if I remove this prefix? e.g. instead of PlanServerHostname=0.0.0.0 PlanNamingPort=1099 PlanOpenEJBPort=4201 PlanClientAddresses=127.0.0.1 ServerHostname=0.0.0.0 NamingPort=1099 OpenEJBPort=4201 ClientAddresses=127.0.0.1 thanks david jencks -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Fixing javamail (again)
Something that worked for me: I have a Liferay war, 4.3.1-trunk, running inside Geronimo-Tomcat 1.1.1. In order to get the smtp mailer working, it was necessary to add the following dependency to geronimo-web.xml: dependency groupIdgeronimo/groupId artifactIdjavamail/artifactId version1.1.1/version typecar/type /dependency The following bug report was key to getting things working: http://issues.apache.org/jira/browse/GERONIMO-2498 based on debug diags I was evaluating that showed: Unable to locate provider for protocol: smtp when invoking session instance of: javax.mail.Transport.send(...) The war declares a gbean in geronimo-web.xml as: resource-ref ref-namemail/MailSession/ref-name resource-linkLiferayMailSession/resource-link /resource-ref gbean name=LiferayMailSession class=org.apache.geronimo.mail.MailGBean attribute name=transportProtocolsmtp/attribute attribute name=hostmy-mail-server/attribute /gbean with the following dependencies: dependency groupIdgeronimo/groupId artifactIdgeronimo-mail/artifactId typejar/type importclasses/import /dependency dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-javamail_1.3.1_spec/artifactId typejar/type importclasses/import /dependency and referenced in web.xml as: resource-ref res-ref-namemail/MailSession/res-ref-name res-typejavax.mail.Session/res-type res-authContainer/res-auth /resource-ref - bvj Christopher M. Cardona wrote: I would like to do the same change for trunk. Anybody got issues/concerns/objections to this? There's an open JIRA for doing this that's marked as a wish item. http://issues.apache.org/jira/browse/GERONIMO-2498 I'd say go for it. Rick -- View this message in context: http://www.nabble.com/Fixing-javamail-%28again%29-tf2431708s134.html#a11734805 Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Commented: (GERONIMO-3339) Schema jars have sun copyright notices in them. Xmlbeans is not up to date.
[ https://issues.apache.org/jira/browse/GERONIMO-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514521 ] Kevan Miller commented on GERONIMO-3339: Missed a dependency in configs/axis2-deployer/src/plan/plan.xml. I've updated to the org.apache.xmlbeans/xmlbeans in revision 558555. Schema jars have sun copyright notices in them. Xmlbeans is not up to date. Key: GERONIMO-3339 URL: https://issues.apache.org/jira/browse/GERONIMO-3339 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0-M6 Reporter: David Jencks Assignee: David Jencks Fix For: 2.0-M7 It turns out that the xmlbeans compiler is copying the annotations including the non-license statement from the sun schemas into the binary xsb files that explain the structure of the schema. Xmlbeans has a flag to keep this from happening. I'll update to xmlbeans 2.3.0 I've fixed the maven-xmlbeans-plugin to expose this flag and deployed a snapshot I'll update the schema jar builds and our geronimo builds to use all this new stuff. I'm also moving the schemas into the expected locations (src/main/xsd and src/main/xsdconfig) so we need less maven configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Simpler config-substitutions.properties keys?
go for it On Jul 22, 2007, at 1:48 PM, David Jencks wrote: I noticed all the keys (except portOffset) in config- substitions.properties start with Plan which seems redundant obvious and confusing. Anyone object if I remove this prefix? e.g. instead of PlanServerHostname=0.0.0.0 PlanNamingPort=1099 PlanOpenEJBPort=4201 PlanClientAddresses=127.0.0.1 ServerHostname=0.0.0.0 NamingPort=1099 OpenEJBPort=4201 ClientAddresses=127.0.0.1 thanks david jencks
[jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514522 ] Kevan Miller commented on GERONIMO-3309: J2G is not building completely for me, at the moment. I can build enough to see that there's additional licensing work required. For instance, there are a number of jar files being included in j2g jar files. For instance, org.apache.geronimo.j2g.util-1.0.0-SNAPSHOT.jar includes pull-parser-2.1.10.jar. We need to know the license(s) that apply to this jar file. pull-parser comes out of Extreme Labs, it looks like. It's not clear to me what license(s) apply to this jar. We need to pin this down precisely. This process needs to occur for all such dependencies. As apropriate, these licenses need to be reflected in the J2G license and notice files. I also noted that the J2G jar files are missing license and notice files. They must have them. These files should reflect the license and notice information for each jar file. For general guidance on apache license and notice file handling, see -- http://www.apache.org/legal/src-headers.html For guidance on what licenses are acceptable to Apache, see -- http://people.apache.org/~cliffs/3party.html Jason, if you're interested in doing this investigation, that would be great. However, a Geronimo committer is going to need to carefully review all of this... Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool --- Key: GERONIMO-3309 URL: https://issues.apache.org/jira/browse/GERONIMO-3309 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: J2G Reporter: Jason Warner Assignee: Kevan Miller Attachments: Geronimo-3309.patch The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- 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: 558562
OpenEJB trunk at 558558 Geronimo Revision: 558562 built with tests skipped See the full build-1800.log file at http://people.apache.org/~prasad/binaries/20070722/build-1800.log Building Geronimo trunk at Revision: 558562 Building OpenEJB trunk at 558558 [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] You must specify at least one goal. Try 'install' [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Sun Jul 22 20:36:18 EDT 2007 [INFO] Final Memory: 2M/504M [INFO]
[jira] Assigned: (GERONIMO-3264) Results of WebKing Accessibility Testing of Geronimo 2.0 M3
[ https://issues.apache.org/jira/browse/GERONIMO-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-3264: -- Assignee: (was: Donald Woods) ALT tags in the JSPs have been fixed. There are several INPUT flagged violations, but I don't have time to look at them right now, so unassigning it from me in case anyone else has time to look at the remaining issues Results of WebKing Accessibility Testing of Geronimo 2.0 M3 --- Key: GERONIMO-3264 URL: https://issues.apache.org/jira/browse/GERONIMO-3264 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 2.0-M3 Environment: all Reporter: Bill Stoddard Priority: Minor Fix For: Wish List Attachments: GeronimoConsoleAccessibilityTesting.zip What is accessibility? All your questions are answered here: http://www.w3.org/WAI/intro/accessibility.php A colleague did some accessibility testing of the G 2.0 admin console with WebKing. The results of that testing are attached. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1637) Add support for version ranges
[ https://issues.apache.org/jira/browse/GERONIMO-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods closed GERONIMO-1637. -- Resolution: Won't Fix New plugin schema provides a way to list multiple Geronimo versions that a plugin is valid on, so closing this issue for now. Add support for version ranges -- Key: GERONIMO-1637 URL: https://issues.apache.org/jira/browse/GERONIMO-1637 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.1 Reporter: Dain Sundstrom Assignee: Donald Woods Fix For: 2.0-M7 Add support for the version ranges on dependencies. Should support the full syntax of maven version ranges. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3208) In-place deployment fails when renaming file
[
https://issues.apache.org/jira/browse/GERONIMO-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3208:
---
Priority: Blocker (was: Major)
Fix Version/s: (was: 2.0-M6)
2.0-M7
I believe this is also causing some Plugin installs to fail, like when you try
to add the webconsole onto the minimal Tomcat assembly, it complains about
framework.war is not a war
In-place deployment fails when renaming file
Key: GERONIMO-3208
URL: https://issues.apache.org/jira/browse/GERONIMO-3208
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 2.0-M6
Environment: Windows XP SP2
Reporter: Aman Nanner
Priority: Blocker
Fix For: 2.0-M7
Attachments: inplace-deployment-fails.ear.zip
I am using the latest SNAPSHOT of Geronimo.
I was trying to deploy my custom application with Geronimo using in-place
deployment, but it would fail with a ZipException and an Access denied
message at the following line:
{code}
System Thread [RMI TCP Connection(189)-192.168.12.66] (Suspended (breakpoint
at line 127 in InPlaceResourceContext))
InPlaceResourceContext.flush() line: 127
EARContext(DeploymentContext).flush() line: 428
TomcatModuleBuilder(AbstractWebModuleBuilder).installModule(JarFile,
EARContext, Module, Collection, ConfigurationStore, Collection) line: 312
AbstractWebModuleBuilder$$FastClassByCGLIB$$8523248f.invoke(int,
Object, Object[]) line: not available
{code}
So I tried creating a small EAR file for testing purposes, and deployment of
it also failed but at a different point:
{code}
[java] Error: Unable to distribute testing.ear: Problem closing war
context
[java] Cannot rename file
[java]
D:\Development\mx0706\build\geronimo\maintenix\testing.ear\testing.war
[java] to
[java]
D:\Development\mx0706\build\geronimo\maintenix\testing.ear\testing.war.saved
{code}
This failed at line 121 in the {{InPlaceResourceContext}} class. I've
attached the sample EAR file that was causing me this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1716) Add usage of SimpleEncryption to PropertiesFileLoginModule and Admin Console
[
https://issues.apache.org/jira/browse/GERONIMO-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods closed GERONIMO-1716.
--
Resolution: Fixed
Committed revision 558586
Add usage of SimpleEncryption to PropertiesFileLoginModule and Admin Console
Key: GERONIMO-1716
URL: https://issues.apache.org/jira/browse/GERONIMO-1716
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: security
Affects Versions: 1.0, 1.1, 1.1.1, 1.2, 2.0-M5
Environment: Any
Reporter: Donald Woods
Assignee: Donald Woods
Priority: Minor
Fix For: 2.0-M7
Attachments: G1716.patch
Enhancement to the default PropertiesFileLoginModule and Console to encrypt
user passwords in users.properties.
To do this, PropertiesFileLoginModule and Console will be updated to use the
SimpleEncryption utility class, just like the deployer, to read/write
passwords that have the {Simple} key in front of encrypted passwords.
The loadProperties() method in PropertiesFileLoginModule will also be updated
to rewrite the users.properties file if it detects unencrypted passwords,
which will allow users to manually edit the file to update a password and
then have it automatically encrypted when the next login event occurs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Anyone else seing J2EE Schema unit test failures?
I'm seeing a unit test failure on Linux in J2EE Schema on the latest trunk - --- Test set: org.apache.geronimo.schema.SchemaConversionUtilsTest --- Tests run: 9, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.7 sec FAILURE! testGetNestedObjectAsType(org.apache.geronimo.schema.SchemaConversionUtilsTest) Time elapsed: 0.013 sec ERROR! java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.xbeans.javaee.EjbJarType.clinit(Unknown Source) at org.apache.geronimo.schema.SchemaConversionUtilsTest.testGetNestedObjectAsType(SchemaConversionUtilsTest.java:150) testcase time=0.32 name=testOrderDescriptionGroup/ testcase time=0.033 name=testOrderJNDIEnvironmentRefsGroup/ testcase time=0.249 name=testGeronimoNamingNamespaceChange/ testcase time=0.011 name=testGetNestedObjectAsType error type=java.lang.NoSuchMethodError message=org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem;java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.xbeans.javaee.EjbJarType.amp;clinitamp;(Unknown Source) at org.apache.geronimo.schema.SchemaConversionUtilsTest.testGetNestedObjectAsType(SchemaConversionUtilsTest.java:150) /error /testcase testcase time=0.009 name=testSecurityElementConverter/ testcase time=0.022 name=testGBeanElementConverter/ testcase time=0.016 name=testQNameConverter1/ testcase time=0.002 name=testQNameConverter2/ testcase time=0.008 name=testWebMessageDestination1/ -Donald [EMAIL PROTECTED] wrote: OpenEJB trunk at 558558 Geronimo Revision: 558562 built with tests skipped See the full build-1800.log file at http://people.apache.org/~prasad/binaries/20070722/build-1800.log Building Geronimo trunk at Revision: 558562 Building OpenEJB trunk at 558558 [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] You must specify at least one goal. Try 'install' [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Sun Jul 22 20:36:18 EDT 2007 [INFO] Final Memory: 2M/504M [INFO] smime.p7s Description: S/MIME Cryptographic Signature
