build failed with 4.0 trunk code
Hi All I've updated today's servicemix 4.0 branch code, and I ran mvn clean install -Dmaven.test.skip=true, I got below error.. Anyone else see this error? Missing: -- 1) org.apache.servicemix:servicemix-shared-compat:zip:installer:3.2.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.servicemix-DartifactId=servicemix-shared-compat \ -Dversion=3.2.1-SNAPSHOT -Dclassifier=installer -Dpackaging=zip -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deplo y-file -DgroupId=org.apache.servicemix -DartifactId=servicemix-shared-compat \ -Dversion=3.2.1-SNAPSHOT -Dclassifier=installer -Dpackaging=zip -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.servicemix.jbi:org.apache.servicemix.jbi.itests:jar:4.0-SNAPSHOT 2) org.apache.servicemix:servicemix-shared-compat:zip:installer:3.2.1-SNAPSHOT 2) org.apache.servicemix:servicemix-eip:zip:installer:3.2.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.servicemix-DartifactId=servicemix-eip \ -Dversion=3.2.1-SNAPSHOT -Dclassifier=installer -Dpackaging=zip -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deplo y-file -DgroupId=org.apache.servicemix -DartifactId=servicemix-eip \ -Dversion=3.2.1-SNAPSHOT -Dclassifier=installer -Dpackaging=zip -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.servicemix.jbi:org.apache.servicemix.jbi.itests:jar:4.0-SNAPSHOT 2) org.apache.servicemix:servicemix-eip:zip:installer:3.2.1-SNAPSHOT -- Best Regards Jeff
[jira] Created: (SM-1138) Unwrapped XAResource objects used by JMS JCA consumer classes cause problems with Howl logging
Unwrapped XAResource objects used by JMS JCA consumer classes cause problems with Howl logging -- Key: SM-1138 URL: https://issues.apache.org/activemq/browse/SM-1138 Project: ServiceMix Issue Type: Bug Components: servicemix-jms Affects Versions: 3.2 Reporter: Craig Muchinsky The org.apache.servicemix.jms.endpoints.JmsJcaConsumerEndpoint and org.apache.servicemix.jms.jca.JcaConsumerProcessor classes both leverage the org.jencks.SingletonEndpointFactory class, however they are not setting the name property, which leads to problems when using journaled JDBC persistence backed by Howl. This manifests itself with the following errors when trying to run the basic example with a Jencks connection factory: java.lang.IllegalStateException: Cannot log transactions unles XAResources are named! org.apache.activemq.ra.LocalAndXATransaction A quick and dirty fix that worked for me was to add: ((SingletonEndpointFactory)endpointFactory).setName(); immediately after the endpointFactory was created in the JmsJcaConsumerEndpoint and JcaConsumerProcessor classes. I'm not sure if setting the name to a blank string is valid, but it does seem to cause the SingletonEndpointFactory to wrap the XAResource objects with a org.apache.geronimo.transaction.manager.WrapperNamedXAResource. Another option might be to modify the Jencks SingletonEndpointFactory class to always default the name to internally, but I don't know if that would have negative side effects anywhere else. Related issues: https://issues.apache.org/activemq/browse/SM-622 https://issues.apache.org/activemq/browse/SM-778 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: WSIT Support
Yes, thank you for replying. Please confirm whether any of the WS-* specs below are not supported. We would need a true Enterprise solution for our financial systems. Thanks again for your kind attention. WS-Trust WS-Security WS-SecureConversation WS-Federation WS-ReliableMessaging WS-AtomicTransaction WS-Coordination WS-MetadataExchange WS-Policy WS-Addressing MTOM Freeman Fang-2 wrote: From my understanding, I think the question is What's the CXF version used in servicemix? :-) Regards Freeman Bozhong Lin wrote: Just to clarify, I think CXF is used in ServiceMix version 3.2, not version 2.0.2. Regards, Bo On Nov 13, 2007 1:10 PM, Freeman Fang wrote: Yes Freeman ArmenH wrote: Thanks, Is the CXF used in ServiceMix version 2.0.2? Freeman Fang wrote: Hi, We already have servicemix-cxf-bc to leverage ws-* feature from cxf. And I also know cxf team do lots of interoperability test between cxf and WCF(including ws-* feature), if you are interested in this issue, I guess you could post this thread on cxf mailling list, where more people can answer your question. Best Regards Freeman ArmenH wrote: It appears that CXF does support most of the WS-* Has anyone used Microsoft WCF based clients/services to show full interoperability? ArmenH wrote: Does ServiceMix fully support WSIT? If not, are there plans to support it? CXF is still not fully compliant with WSIT. -- View this message in context: http://www.nabble.com/WSIT-Support-tf4795567s12049.html#a13761127 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: WSIT Support
Thanks. Is there a technical reason why WSIT is not used in ServiceMix 3.2 instead? Freeman Fang-2 wrote: For servicemix cxf bc, we support ws-security, ws-ReliableMessage, ws-policy, ws-Addressing, MTOM now Regards Freeman ArmenH wrote: Yes, thank you for replying. Please confirm whether any of the WS-* specs below are not supported. We would need a true Enterprise solution for our financial systems. Thanks again for your kind attention. WS-Trust WS-Security WS-SecureConversation WS-Federation WS-ReliableMessaging WS-AtomicTransaction WS-Coordination WS-MetadataExchange WS-Policy WS-Addressing MTOM Freeman Fang-2 wrote: From my understanding, I think the question is What's the CXF version used in servicemix? :-) Regards Freeman Bozhong Lin wrote: Just to clarify, I think CXF is used in ServiceMix version 3.2, not version 2.0.2. Regards, Bo On Nov 13, 2007 1:10 PM, Freeman Fang wrote: Yes Freeman ArmenH wrote: Thanks, Is the CXF used in ServiceMix version 2.0.2? Freeman Fang wrote: Hi, We already have servicemix-cxf-bc to leverage ws-* feature from cxf. And I also know cxf team do lots of interoperability test between cxf and WCF(including ws-* feature), if you are interested in this issue, I guess you could post this thread on cxf mailling list, where more people can answer your question. Best Regards Freeman ArmenH wrote: It appears that CXF does support most of the WS-* Has anyone used Microsoft WCF based clients/services to show full interoperability? ArmenH wrote: Does ServiceMix fully support WSIT? If not, are there plans to support it? CXF is still not fully compliant with WSIT. -- View this message in context: http://www.nabble.com/WSIT-Support-tf4795567s12049.html#a13762633 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
use of resource?
src/main/resource/META-INF/service/org/apache/servicemix/jbi/* src/main/resource/META-INF/service/org/apache/servicemix/jdbc/* use of these file in the directory? thanks -- View this message in context: http://www.nabble.com/use-of-resource--tf4810215s12049.html#a13762819 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Resolved: (GERONIMO-3490) Missing Jetty Connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen resolved GERONIMO-3490. Resolution: Fixed Fix Version/s: 2.1 Missing Jetty Connector stats - Key: GERONIMO-3490 URL: https://issues.apache.org/jira/browse/GERONIMO-3490 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.1 Environment: windows xp Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Fix For: 2.1 Attachments: geronimo-3490.patch, geronimo-3490b.patch Jetty6 provides connector statistics, but they are not being surfaced in Geronimo's source code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] 2.1: Failed for Revision: 594887
OpenEJB trunk at 594733 Geronimo Revision: 594887 built with tests included See the full build-0900.log file at http://people.apache.org/~prasad/binaries/trunk/20071114/build-0900.log jtidy:jtidy:jar:8.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), jtidy.sourceforge (http://jtidy.sourceforge.net/snapshots), 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/) Path to dependency: 1) org.apache.geronimo.plugins:testsuite-maven-plugin:maven-plugin:2.1-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:362) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:284) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'jtidy:jtidy:jar': Error getting POM for 'jtidy:jtidy' from the repository: Error transferring file jtidy:jtidy:pom:8.0-20060801.131059-3 from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), jtidy.sourceforge (http://jtidy.sourceforge.net/snapshots), 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/) for project jtidy:jtidy at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:134) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:339) ... 22 more Caused by: org.apache.maven.project.ProjectBuildingException: Error getting POM for 'jtidy:jtidy' from the repository: Error transferring file jtidy:jtidy:pom:8.0-20060801.131059-3 from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), jtidy.sourceforge (http://jtidy.sourceforge.net/snapshots), 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/) for project jtidy:jtidy at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:560) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:234) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:105) ... 23 more Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Error transferring file jtidy:jtidy:pom:8.0-20060801.131059-3 from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), jtidy.sourceforge (http://jtidy.sourceforge.net/snapshots), 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/) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:201) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:526) ... 25 more Caused by: org.apache.maven.wagon.TransferFailedException: Error transferring file at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:104) at org.apache.maven.wagon.StreamWagon.get
[jira] Closed: (GERONIMO-1828) JSR-88 treats AbstractName like an ObjectName
[ https://issues.apache.org/jira/browse/GERONIMO-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-1828. -- JSR-88 treats AbstractName like an ObjectName - Key: GERONIMO-1828 URL: https://issues.apache.org/jira/browse/GERONIMO-1828 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 1.1 Reporter: Paul McMahan Assignee: Aaron Mulder Priority: Critical Fix For: 1.1 Attachments: dbplan.xml I get this stacktrace when trying to deploy a database plan: Deployer operation failed: Invalid value: 'geronimo.config:name=console/dbpool-test/1.0/rar' javax.management.MalformedObjectNameException: Invalid value: 'geronimo.config:name=console/dbpool-test/1.0/rar' at javax.management.ObjectName.parsePropertyValue(ObjectName.java:571) at javax.management.ObjectName.convertStringToProperties(ObjectName.java:462) at javax.management.ObjectName.parse(ObjectName.java:399) at javax.management.ObjectName.init(ObjectName.java:76) at org.apache.geronimo.deployment.plugin.local.CommandSupport.loadChildren(CommandSupport.java:326) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:70) at java.lang.Thread.run(Thread.java:534) I'll attach the db plan. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1666) Console issues resulting from configID changes
[ https://issues.apache.org/jira/browse/GERONIMO-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-1666. -- Console issues resulting from configID changes -- Key: GERONIMO-1666 URL: https://issues.apache.org/jira/browse/GERONIMO-1666 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: console Affects Versions: 1.2 Reporter: Paul McMahan Fix For: 1.1 This JIRA tracks what areas of the console need attention as a result of the configID changes. At Revision 382401: - Classloader for classes loaded from geronimo-console-core-1.1-SNAPSHOT.jar can't load classes from geronimo-jetty-1.1-SNAPSHOT.jar. This prevents BasicProxyManager from being able to create proxies needed by the Server Logs and Web Server portlets. - J2EEServerImpl.getRepositories() returns an empty String[]. This prevents the the Common Libraries portlet and the DB Pool Wizard from listing out the available jars in the repository. Also prevents the JMS Resource portlet from being able to create new JMS Resource groups for ActiveMQ. - Trying to delete a new activeio listener I created results in the following ST. BTW, it failed to start too but I see that problem in Geronimo-1.0 16:19:56,029 WARN [Util] No parents found for geronimo.server:J2EEApplication=null,J2EEModule=geronimo/activemq-broker/1.1-SNAPSHOT/car,J2EEServer=geronimo,broker=ActiveMQ,j2eeType=JMSConnector,name=ActiveMQ.activeio.0.0.0.0.9123-asdf 16:19:56,030 ERROR [ActiveMQManagerGBean] Unable to remove GBean java.lang.NullPointerException at org.apache.geronimo.kernel.basic.BasicKernel.createGBeanName(BasicKernel.java:427) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:177) at org.activemq.gbean.management.ActiveMQManagerGBean.removeConnector(ActiveMQManagerGBean.java:247) at org.activemq.gbean.management.ActiveMQManagerGBean$$FastClassByCGLIB$$a78b116e.invoke(generated) - ConfigurationManager.listStores() returns an empty list for the storeName: geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-system/1.1-SNAPSHOT/car,J2EEServer=geronimo,j2eeType=ConfigurationStore,name=Local This prevents the user from being able to start/stop/undeploy/etc their components from the EAR, WAR, EJB, Connector, App Client, and System Modules portlets - Deploying a simple WAR fails with an external plan fails with the error message: org.apache.geronimo.kernel.config.InvalidConfigException: Source is not readable /home/pmcmahan/src/geronimo/1.1/assemblies/j2ee-jetty-server/target/geronimo-1.1-SNAPSHOT/repository/test/test/1.1/test-1.1.war Source is not readable /home/pmcmahan/src/geronimo/1.1/assemblies/j2ee-jetty-server/target/geronimo-1.1-SNAPSHOT/repository/test/test/1.1/test-1.1.war I checked and the .../repository/test/test/1.1 directory is present but it is empty - Creating and then deploying a new security realm fails with the following ST: 17:20:06,704 ERROR [Deployer] Deployment failed due to java.lang.NullPointerException at org.apache.geronimo.kernel.repository.Version.parseVersion(Version.java:115) at org.apache.geronimo.kernel.repository.Version.init(Version.java:40) at org.apache.geronimo.kernel.repository.Artifact.init(Artifact.java:38) at org.apache.geronimo.deployment.service.EnvironmentBuilder.toArtifact(EnvironmentBuilder.java:229) at org.apache.geronimo.deployment.service.EnvironmentBuilder.buildEnvironment(EnvironmentBuilder.java:56) at org.apache.geronimo.deployment.service.EnvironmentBuilder.buildEnvironment(EnvironmentBuilder.java:125) at org.apache.geronimo.deployment.service.ServiceConfigBuilder.getConfigurationID(ServiceConfigBuilder.java:147) The relevant part of the plan (which was generated by the wizard) looks like: environment configId groupIdUnspecified/groupId artifactIdtest/artifactId /configId /environment -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2465) Relocate plugin repository list to a source controlled location
[ https://issues.apache.org/jira/browse/GERONIMO-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2465. -- Relocate plugin repository list to a source controlled location --- Key: GERONIMO-2465 URL: https://issues.apache.org/jira/browse/GERONIMO-2465 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.1, 1.1.1 Reporter: Paul McMahan Assignee: Paul McMahan Fix For: 1.2 The default list of plugin repositories that gets loaded into the admin console currently comes from a user directory at people.apache.org. The list should be relocated to SVN so that it can be version controlled and updated by project committers. See discussion at: http://mail-archives.apache.org/mod_mbox/geronimo-dev/200609.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2804) implement jsf 1.2 support
[ https://issues.apache.org/jira/browse/GERONIMO-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2804. -- implement jsf 1.2 support - Key: GERONIMO-2804 URL: https://issues.apache.org/jira/browse/GERONIMO-2804 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: web Affects Versions: 2.0-M3 Reporter: Paul McMahan Assignee: Paul McMahan Fix For: 2.0-M3 myfaces has not published the 1.2-SNAPSHOT binaries to a maven repo yet so Geronimo includes them in the jee5 assemblies by putting them in a local repo at modules/geronimo-web-2.5-builder/repository. Those binaries need to be updated to the latest snapshot. Also, the myfaces classes need to be added to all webapp's classloaders -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2805) add tribes clustering support for tomcat
[ https://issues.apache.org/jira/browse/GERONIMO-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2805. -- add tribes clustering support for tomcat Key: GERONIMO-2805 URL: https://issues.apache.org/jira/browse/GERONIMO-2805 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.0-M3 Reporter: Paul McMahan Assignee: Paul McMahan Fix For: 2.0-M3 Attachments: config.xml Tomcat6 has been redesigned to use tribes for clustering, so the o.a.g.tomcat.cluster package was temporarily disabled when tomcat6 was introduced into geronimo 2.0. Geronimo's tomcat cluster gbeans need to be updated to support tribes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2955) MyFaces Tag Library Descriptors are not found by the Jasper Compiler
[
https://issues.apache.org/jira/browse/GERONIMO-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul McMahan closed GERONIMO-2955.
--
MyFaces Tag Library Descriptors are not found by the Jasper Compiler
Key: GERONIMO-2955
URL: https://issues.apache.org/jira/browse/GERONIMO-2955
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: web
Affects Versions: 2.0-M3
Reporter: Paul McMahan
Assignee: Paul McMahan
Priority: Critical
Fix For: 2.0-M4
Jasper's technique for finding Tag Library Descriptors (TLDs) does not work
well with Geronimo's MultiParentClassLoader. The Jasper compiler tries to
find TLDs in jar files by getting the list of jars from the webapp's
classloader and scanning them for META-INF/\*\*.tld. Then it repeats this
process up the classloader hierarchy (at least what it *thinks* is the
classloader hierarchy) by calling ClassLoader.getParent(). That works OK
when then TLDs are in the webapp's WEB-INF/lib or in the JRE's system or
application classloader. But this technique doesn't work in Geronimo because
there are sometimes jars in the classloader hierarchy that are only
accessible by using Geronimo's special MultiParentClassLoader.getParents()
method.
The Jasper code referred to above can be viewed in the scanJars() method of
this class:
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_10/java/org/apache/jasper/compiler/TldLocationsCache.java
Because of this limitation the Jasper compiler does not find the TLDs in
myfaces-impl-2.0-SNAPSHOT.jar because it doesn't find the classloader
containing that jar when it looks up the direct lineage of classloaders.
This causes the following error message when a JSP refers to the JSF taglibs:
{quote}
javax.servlet.ServletException: The absolute uri:
http://java.sun.com/jsf/html cannot be resolved in either web.xml or the jar
files deployed with this application
{quote}
The MyFaces TLDs need to be made accessible to Jasper so that webapps can
reference the JSF taglibs in their JSPs without copying the TLDs into their
WARs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1887) Remove unneeded jars from console WEB-INF/lib directories
[ https://issues.apache.org/jira/browse/GERONIMO-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-1887. -- Remove unneeded jars from console WEB-INF/lib directories - Key: GERONIMO-1887 URL: https://issues.apache.org/jira/browse/GERONIMO-1887 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.x Reporter: Paul McMahan Assignee: Jason Dillon Priority: Minor Fix For: 1.2 Several of the jars in the console's WEB-INF/lib directories are unneeded - both copies of jasper-compiler-5.5.12.jar (400K each) - both copies of jasper-runtime-5.5.12.jar (80K each) - the copy of castor-0.9.5.3.jar in console-standard (1.7M) Removing these jars will decrease the server footprint and binary image download size. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2160) Can't install a J2EE connector plugin
[ https://issues.apache.org/jira/browse/GERONIMO-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2160. -- Can't install a J2EE connector plugin - Key: GERONIMO-2160 URL: https://issues.apache.org/jira/browse/GERONIMO-2160 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.1 Environment: windows xp, Reporter: Paul McMahan Assignee: Aaron Mulder Priority: Minor Fix For: 1.1.1 Attachments: test-1.0.rar Steps to recreate: - create a database pool using the wizard in the console - export the connector associated with the pool just created as a plugin using the plugins portlet (attached a copy fo this jira) - copy the connector plugin into a plugin repository - install the connector plugin using the pluigns portlet - start the plugin, which results in the following stacktrace: 15:36:16,187 INFO [DWRServlet] retrieved system configuration file: [EMAIL PROTECTED] 15:36:22,421 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=console.dbpool/test/1.0/rar?J2EEApplication=null,JCAConnectionFactory=test,JCAResource=console.dbpool/test/1.0/rar,ResourceAdapter=console.dbpool/test/1.0/rar,ResourceAdapterModule=console.dbpool/test/1.0/rar,j2eeType=JCAManagedConnectionFactory,name=test java.lang.ClassNotFoundException: org.tranql.connector.jdbc.JDBCDriverMCF in classloader console.dbpool/test/1.0/rar at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:249) at java.lang.ClassLoader.loadClass(Unknown Source) at org.apache.geronimo.connector.outbound.ManagedConnectionFactoryWrapper.init(ManagedConnectionFactoryWrapper.java:138) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:933) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:512) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:493) at org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at
[jira] Closed: (GERONIMO-3159) J2G documentation
[ https://issues.apache.org/jira/browse/GERONIMO-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-3159. -- J2G documentation - Key: GERONIMO-3159 URL: https://issues.apache.org/jira/browse/GERONIMO-3159 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: J2G Reporter: Paul McMahan Assignee: Paul McMahan Priority: Minor Attachments: geronimo-3159-2.patch, geronimo-3159.patch The J2G donation (GERONIMO-2743) contained some documentation. But that documentation had IBM Confidential footer. Need to secure new documentation from the contributor that does not contain the footer or get permission to remove the footer. Once the documentation has been secured it should be added to the J2G package and maybe also added to the wiki. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1876) backport console progress bar from 1.2 to 1.1
[ https://issues.apache.org/jira/browse/GERONIMO-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-1876. -- backport console progress bar from 1.2 to 1.1 - Key: GERONIMO-1876 URL: https://issues.apache.org/jira/browse/GERONIMO-1876 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: Paul McMahan Assignee: Aaron Mulder Fix For: 1.1 Attachments: progressbar.patch progress bar is needed for lengthy driver and plugin downloads -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2773) cannot create a new jetty http connector from console
[ https://issues.apache.org/jira/browse/GERONIMO-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2773. -- cannot create a new jetty http connector from console - Key: GERONIMO-2773 URL: https://issues.apache.org/jira/browse/GERONIMO-2773 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, Jetty Affects Versions: 2.0-M2 Environment: 2.0-SNAPSHOT jetty jee5 assembly, macosx Reporter: Paul McMahan Assignee: Anita Kulshreshtha Fix For: 2.0-M6 Attachments: geronimo-2773.patch, geronimo-2773.patch, geronimo-2773.patch trying to create a new jetty http connector from the admin console produces the following stack trace: 00:16:26,133 ERROR [JettyManagerImpl] Unable to add GBean org.apache.geronimo.kernel.config.InvalidConfigException: Cound not add GBean org.apache.geronimo.configs/jetty6/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/jetty6/2.0-SNAPSHOT/car,j2eeType=GBean,name=test to configuration org.apache.geronimo.configs/jetty6/2.0-SNAPSHOT/car at org.apache.geronimo.kernel.config.EditableKernelConfigurationManager.addGBeanToConfiguration(EditableKernelConfigurationManager.java:122) at org.apache.geronimo.kernel.config.EditableKernelConfigurationManager.addGBeanToConfiguration(EditableKernelConfigurationManager.java:61) at org.apache.geronimo.kernel.config.EditableKernelConfigurationManager$$FastClassByCGLIB$$daeffab3.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$de47e049.addGBeanToConfiguration(generated) at org.apache.geronimo.jetty6.JettyManagerImpl.addConnector(JettyManagerImpl.java:98) at org.apache.geronimo.jetty6.JettyManagerImpl$$FastClassByCGLIB$$f2d5e245.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.management.geronimo.WebManager$$EnhancerByCGLIB$$fb3a5d8f.addConnector(generated) at org.apache.geronimo.console.util.PortletManager.createWebConnector(PortletManager.java:247) at org.apache.geronimo.console.webmanager.ConnectorPortlet.processAction(ConnectorPortlet.java:107) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(JettySecurityHandler.java:133) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46) at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47) at
[jira] Closed: (GERONIMO-2007) Avoid Classloader warnings generated by BasicProxyManager
[ https://issues.apache.org/jira/browse/GERONIMO-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2007. -- Avoid Classloader warnings generated by BasicProxyManager - Key: GERONIMO-2007 URL: https://issues.apache.org/jira/browse/GERONIMO-2007 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: Paul McMahan Assignee: Joe Bohn Fix For: 1.1.1 Attachments: GERONIMO-2007.patch Several views in the console create proxies for objects that implement interfaces not available in the console's classloader. The warning messages look like: 08:56:26,315 WARN [BasicProxyManager] Could not load interface org.apache.geronimo.tomcat.TomcatWebContainer in provided ClassLoader for geronimo/tomcat/1.1-SNAPSHOT/car?ServiceModule=geronimo/tomcat/1.1-SNAPSHOT/car,j2eeType=GBean,name=TomcatWebContainer This warning message can be avoided by getting the classloader for the proxied object from the kernel and then using it to create the proxy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3157) unit test cases for J2G
[ https://issues.apache.org/jira/browse/GERONIMO-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-3157. -- unit test cases for J2G --- Key: GERONIMO-3157 URL: https://issues.apache.org/jira/browse/GERONIMO-3157 Project: Geronimo Issue Type: Test Security Level: public(Regular issues) Components: J2G Reporter: Paul McMahan Assignee: Jason Warner Priority: Minor Attachments: Geronimo-3157-LicenseHeaders.patch, Geronimo-3157.patch Create unit test cases for J2G tool to verify that its working correctly at build time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2784) Samples cleanup
[ https://issues.apache.org/jira/browse/GERONIMO-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2784. -- Samples cleanup --- Key: GERONIMO-2784 URL: https://issues.apache.org/jira/browse/GERONIMO-2784 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.0-M3 Reporter: Paul McMahan Assignee: Paul McMahan Priority: Minor Fix For: 2.1 As discussed on dev: http://mail-archives.apache.org/mod_mbox/geronimo-dev/200701.mbox/[EMAIL PROTECTED] # Move the following modules from server/trunk/applications to samples/trunk ** demo (security demo) ** geronimo-examples ** geronimo-ldap-demo ** magicGball # Move anything worth keeping from server/trunk/applications/daytrader to daytrader/trunk # Remove the configs for these modules from server/trunk/configs # Enable samples/trunk to build CARs so that the samples can be installed as plugins # Publish the CARs built in samples/trunk to a maven repo # Update the plugin catalog at site/trunk/plugins/ to reference the samples in maven 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-2521) add snapshot support to plugin installer gbean
[ https://issues.apache.org/jira/browse/GERONIMO-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2521. -- add snapshot support to plugin installer gbean -- Key: GERONIMO-2521 URL: https://issues.apache.org/jira/browse/GERONIMO-2521 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.x Reporter: Paul McMahan Assignee: Paul McMahan Fix For: 1.2 Attachments: GERONIMO-2521.patch When a snapshot artifact is published in an m2 repo the SNAPSHOT suffix of the artifact's filename is replaced with a timestamp and build number that come from a file named maven-metadata.xml in the artifacts directory. For example, the artifact org.apache.geronimo.configs/servlet-examples-tomcat/1.2-SNAPSHOT/car is published at: http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/configs/servlet-examples-tomcat/1.2-SNAPSHOT/servlet-examples-tomcat-1.2-20061026.113134-2.car When the plugin installer gbean is installing a SNAPSHOT version of a plugin it should create the download URL using the timestamp and build number obtained from maven-metadata.xml instead of the version number. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2442) update geronimo-plugin.xml files to use org.apache.geronimo group ids
[ https://issues.apache.org/jira/browse/GERONIMO-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2442. -- update geronimo-plugin.xml files to use org.apache.geronimo group ids - Key: GERONIMO-2442 URL: https://issues.apache.org/jira/browse/GERONIMO-2442 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 1.2 Reporter: Paul McMahan Assignee: Paul McMahan Fix For: 1.2 During the m2 conversion effort many of the maven group ids for geronimo modules changed from geronimo to org.apache.geronimo.modules or org.apache.geronimo.configs. prerequisite and dependency elements in several geronimo-plugin.xml files need to be updated to use the new group ids. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1392) update additional samples redirect in geronimo website
[ https://issues.apache.org/jira/browse/GERONIMO-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-1392. -- Assignee: Paul McMahan update additional samples redirect in geronimo website Key: GERONIMO-1392 URL: https://issues.apache.org/jira/browse/GERONIMO-1392 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 1.x Environment: all envs Reporter: Paul McMahan Assignee: Paul McMahan Priority: Minor Attachments: GERONIMO-1392.patch The location of the additional samples document in confluence changed from: http://opensource2.atlassian.com/confluence/oss/display/GERONIMO/Samples+for+Apache+Geronimo to: http://opensource2.atlassian.com/confluence/oss/display/GERONIMO/Sample+applications Need to update the corresponding redirect at the Geronimo website. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1137) The (JMX) RMI port number 1099 conflicts with Java Update
The (JMX) RMI port number 1099 conflicts with Java Update - Key: SM-1137 URL: https://issues.apache.org/activemq/browse/SM-1137 Project: ServiceMix Issue Type: Bug Affects Versions: 3.2 Environment: Windows XP and ServiceMix 3.2 Reporter: Will Franco Attachments: servicemix.properties The (JMX) RMI port number 1099 conflicts with Java Update. This problem is manifested when you first have Java Update running and then you start ServiceMix. ServiceMix crashes because it cannot open port 1099. The solution is to change the port number that is specified in servicemix.properties file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Moving to TranQL 1.4 ?
Hi Vasiliy, I put a draft out about two weeks ago and need to publish the final. I'd expect with Thanksgiving and some other stuff I'd be able to get going in early December. On Nov 13, 2007, at 10:40 PM, Zakharov, Vasily M wrote: Matt, Are there any news on that? :) Thanks! Vasily -Original Message- From: Matt Hogstrom [mailto:[EMAIL PROTECTED] Sent: Friday, October 05, 2007 8:48 AM To: dev@geronimo.apache.org Subject: Re: Moving to TranQL 1.4 ? Excellent ... I'm finishing some other performance work. When I get that completed I'd like to get this tested. It will be nice to finally run the monster ;-P On Oct 4, 2007, at 11:29 PM, Zakharov, Vasily M wrote: Hi, Matt, Great to hear from you, and great to hear the news! I've tried to update the deployment plans to G2.0.1 as best as I could, here's what I have now: http://cwiki.apache.org/confluence/download/attachments/64828/sjas- app.x ml http://cwiki.apache.org/confluence/download/attachments/64828/sjas- db.xm l http://cwiki.apache.org/confluence/download/attachments/64828/sjas- jms.x ml http://cwiki.apache.org/confluence/display/GMOxDOC20/ SPECjAppServer2004 It has issues working (e. g. for now I can't lookup the beans through JNDI externally), but at least it deploys with no errors. I assume some things there are anyway obsolete and have to be replaced. Please also note issues OPENEJB-700 and OPENEJB-701 filed while trying to make the things above work, adjustments were made to workaround OPENEJB-701. Thanks alot for your help! Vasily -Original Message- From: Matt Hogstrom [mailto:[EMAIL PROTECTED] Sent: Friday, October 05, 2007 6:56 AM To: dev@geronimo.apache.org Subject: Re: Moving to TranQL 1.4 ? Vasily, We've moved from TranQL for the support of CMP to OpenJPA. Dain provided a neat bridge so we can use the same technology for EJB 3 and EJB 2.x. At this point you can achieve the desired results using the orm.xml and OpenJPA configuration. I'd be interested in helping you out on this. Do you have a current set of DDs your working from or are these the same ones as we had back in http://svn.apache.org/ repos/asf/geronimo/sandbox/specjappserver2004/ On Oct 4, 2007, at 8:57 PM, Zakharov, Vasily M wrote: Hi, Are there any plans of moving to the next version of TranQL, 1.3.1 or maybe 1.4-SNAPSHOT? Both seem to be available at http://dist.codehaus.org/tranql/jars/ When I was working with G1.x last year, it was found that a critical flaw exists in TranQL 1.3, that prevents SPECjAppServer2004 from successfuly running on Geronimo - SjAS requires a support of READ_COMMITTED and REPEATABLE_READ transaction isolation levels in XA mode, and TranQL 1.3 only supports READ_UNCOMMITTED level. Issue GERONIMO-2128 http://issues.apache.org/jira/browse/ GERONIMO-2128 is related to this issue, and it's still open. At that time Matt Hostrom said he has plans to add the necessary support in TranQL 1.3.1 or 1.4, but as I can see, G2.0.1 still uses TranQL 1.3: http://article.gmane.org/gmane.comp.java.geronimo.user/3427 http://thread.gmane.org/gmane.comp.java.openejb.devel/3926 Matt, could you, or anyone else, please shed some light on the current situation with this issue? Thank you very much! Vasily Zakharov Intel ESSD --- Closed Joint Stock Company Intel A/O Registered legal address: 125252, Moscow, Russian Federation, Chapayevsky Per, 14. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Closed Joint Stock Company Intel A/O Registered legal address: 125252, Moscow, Russian Federation, Chapayevsky Per, 14. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Closed Joint Stock Company Intel A/O Registered legal address: 125252, Moscow, Russian Federation, Chapayevsky Per, 14. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
[jira] Created: (GERONIMO-3602) SEI specified in webservices.xml does not overwrite annotation
SEI specified in webservices.xml does not overwrite annotation -- Key: GERONIMO-3602 URL: https://issues.apache.org/jira/browse/GERONIMO-3602 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: webservices Affects Versions: 2.0.x, 2.1 Reporter: Jarek Gawor Looks like SEI specified in the webservices.xml is getting ignored with CXF and Axis2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3602) SEI specified in webservices.xml does not overwrite annotation
[ https://issues.apache.org/jira/browse/GERONIMO-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3602: - Assignee: Jarek Gawor SEI specified in webservices.xml does not overwrite annotation -- Key: GERONIMO-3602 URL: https://issues.apache.org/jira/browse/GERONIMO-3602 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: webservices Affects Versions: 2.0.x, 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor Looks like SEI specified in the webservices.xml is getting ignored with CXF and Axis2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r594117 [1/2] - in /geronimo/server/trunk: assemblies/geronimo-jetty6-javaee5/src/main/assembly/ assemblies/geronimo-jetty6-javaee5/src/main/resources/cluster-repository/ assemblies/ge
On Nov 13, 2007 4:40 PM, Kevan Miller [EMAIL PROTECTED] wrote:
Hi Gianny,I notice that this scheme is storing admin username and
password in clear text. It will also make the username/password accessible
via JMX. I think we need to avoid this. Would prefer to see this information
handled in a manner more consistent with our handling of sensitive
information in var/security. Would you agree?
David Jencks reminded me that 'password' properties in config.xml will be
encrypted.
--kevan
--kevan
On Nov 12, 2007, at 8:35 AM, [EMAIL PROTECTED] wrote:
Modified:
geronimo/server/trunk/plugins/clustering/clustering/src/main/plan/plan.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/clustering/clustering/src/main/plan/plan.xml?rev=594117r1=594116r2=594117view=diff
==
---
geronimo/server/trunk/plugins/clustering/clustering/src/main/plan/plan.xml
(original)
+++
geronimo/server/trunk/plugins/clustering/clustering/src/main/plan/plan.xml
Mon Nov 12 05:35:48 2007
@@ -27,4 +27,78 @@
/reference
/gbean
+gbean name=MasterRepository class=
org.apache.geronimo.system.repository.Maven2Repository
+attribute name=rootmaster-repository//attribute
+reference name=ServerInfo
+nameServerInfo/name
+/reference
+/gbean
+
+gbean name=MasterConfigurationStore class=
org.apache.geronimo.clustering.deployment.MasterConfigurationStore
+xml-attribute name=defaultEnvironment
+environment xmlns=
http://geronimo.apache.org/xml/ns/deployment-${geronimoSchemaVersion};
+dependencies
+dependency
+groupId${pom.groupId}/groupId
+artifactIdclustering/artifactId
+typecar/type
+/dependency
+/dependencies
+/environment
+/xml-attribute
+reference name=Repository
+nameMasterRepository/name
+/reference
+reference name=ClusterInfo
+nameClusterInfo/name
+/reference
+reference name=ClusterConfigurationStoreClient
+nameClusterConfigurationStoreClient/name
+/reference
+/gbean
+
+gbean name=ClusterConfigurationStoreClient class=
org.apache.geronimo.clustering.deployment.BasicClusterConfigurationStoreClient
+attribute
name=clusterConfigurationStoreNameQuery?name=ClusterConfigurationStore/attribute
+/gbean
+
+gbean name=ClusterRepository class=
org.apache.geronimo.system.repository.Maven2Repository
+attribute name=rootcluster-repository//attribute
+reference name=ServerInfo
+nameServerInfo/name
+/reference
+/gbean
+
+gbean name=ClusterStore class=
org.apache.geronimo.system.configuration.RepositoryConfigurationStore
+reference name=Repository
+nameClusterRepository/name
+/reference
+/gbean
+
+gbean name=ClusterConfigurationStore class=
org.apache.geronimo.clustering.deployment.BasicClusterConfigurationStore
+reference name=ConfigurationStore
+nameClusterStore/name
+/reference
+/gbean
+
+!-- Static Cluster Configuration --
+gbean name=ClusterInfo class=
org.apache.geronimo.clustering.config.BasicClusterInfo
+attribute name=name${PlanClusterName}/attribute
+reference name=NodeInfos/reference
+/gbean
+
+gbean name=NodeInfo class=
org.apache.geronimo.clustering.config.BasicNodeInfo
+ attribute name=nameNodeName/attribute
+ xml-attribute name=extendedJMXConnectorInfo
+ ns:javabean xmlns:ns=
http://geronimo.apache.org/xml/ns/deployment/javabean-1.0; class=
org.apache.geronimo.clustering.config.BasicExtendedJMXConnectorInfo
+ ns:property name=usernamesystem/ns:property
+ ns:property name=passwordmanager/ns:property
+ ns:property name=protocolrmi/ns:property
+ ns:property name=hostlocalhost/ns:property
+ ns:property name=port1099/ns:property
+ ns:property name=urlPathJMXConnector/ns:property
+ ns:property name=localtrue/ns:property
+ /ns:javabean
+ /xml-attribute
+ /gbean
+
/module
[BUILD] 2.1: Failed for Revision: 595028
OpenEJB trunk at 594733 Geronimo Revision: 595028 built with tests included See the full build-1500.log file at http://people.apache.org/~prasad/binaries/trunk/20071114/build-1500.log 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] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) jtidy:jtidy:jar:8.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=jtidy -DartifactId=jtidy \ -Dversion=8.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=jtidy -DartifactId=jtidy \ -Dversion=8.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.plugins:testsuite-maven-plugin:maven-plugin:2.1-SNAPSHOT 2) jtidy:jtidy:jar:8.0-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:testsuite-maven-plugin:maven-plugin:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), jtidy.sourceforge (http://jtidy.sourceforge.net/snapshots), 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/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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(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.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) jtidy:jtidy:jar:8.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=jtidy -DartifactId=jtidy \ -Dversion=8.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=jtidy -DartifactId=jtidy \ -Dversion=8.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.plugins:testsuite-maven-plugin:maven-plugin:2.1-SNAPSHOT 2) jtidy:jtidy:jar:8.0-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:testsuite-maven-plugin:maven-plugin:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), jtidy.sourceforge (http://jtidy.sourceforge.net/snapshots), 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
Re: svn commit: r594117 [1/2] - in /geronimo/server/trunk: assemblies/geronimo-jetty6-javaee5/src/main/assembly/ assemblies/geronimo-jetty6-javaee5/src/main/resources/cluster-repository/ assemblies/ge
Hi Kevan,
Sorry for my late reply and thanks for raising this security issue. I
believe that the encryption of password attributes is not enough in
this case as password in this case is an XML JavaBean attribute;
based on a cursory review of GBeanOverride, it seems that this case
is not yet handled.
I will fix this problem tonight or in the next couple of days.
Thanks,
Gianny
On 15/11/2007, at 6:54 AM, Kevan Miller wrote:
On Nov 13, 2007 4:40 PM, Kevan Miller [EMAIL PROTECTED] wrote:
Hi Gianny,
I notice that this scheme is storing admin username and password
in clear text. It will also make the username/password accessible
via JMX. I think we need to avoid this. Would prefer to see this
information handled in a manner more consistent with our handling
of sensitive information in var/security. Would you agree?
David Jencks reminded me that 'password' properties in config.xml
will be encrypted.
--kevan
--kevan
On Nov 12, 2007, at 8:35 AM, [EMAIL PROTECTED] wrote:
Modified: geronimo/server/trunk/plugins/clustering/clustering/src/
main/plan/plan.xml
URL: http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/
clustering/clustering/src/main/plan/plan.xml?
rev=594117r1=594116r2=594117view=diff
=
=
--- geronimo/server/trunk/plugins/clustering/clustering/src/main/
plan/plan.xml (original)
+++ geronimo/server/trunk/plugins/clustering/clustering/src/main/
plan/plan.xml Mon Nov 12 05:35:48 2007
@@ -27,4 +27,78 @@
/reference
/gbean
+gbean name=MasterRepository
class=org.apache.geronimo.system.repository.Maven2Repository
+attribute name=rootmaster-repository//attribute
+reference name=ServerInfo
+nameServerInfo/name
+/reference
+/gbean
+
+gbean name=MasterConfigurationStore class=
org.apache.geronimo.clustering.deployment.MasterConfigurationStore
+xml-attribute name=defaultEnvironment
+environment xmlns= http://geronimo.apache.org/xml/
ns/deployment-${geronimoSchemaVersion}
+dependencies
+dependency
+groupId${pom.groupId }/groupId
+artifactIdclustering/artifactId
+typecar/type
+/dependency
+/dependencies
+/environment
+/xml-attribute
+reference name=Repository
+nameMasterRepository/name
+/reference
+reference name=ClusterInfo
+nameClusterInfo/name
+/reference
+reference name=ClusterConfigurationStoreClient
+nameClusterConfigurationStoreClient/name
+/reference
+/gbean
+
+gbean name=ClusterConfigurationStoreClient
class=org.apache.geronimo.clustering.deployment.BasicClusterConfigur
ationStoreClient
+attribute name=clusterConfigurationStoreNameQuery?
name=ClusterConfigurationStore/attribute
+/gbean
+
+gbean name=ClusterRepository class=
org.apache.geronimo.system.repository.Maven2Repository
+attribute name=rootcluster-repository//attribute
+reference name=ServerInfo
+nameServerInfo/name
+/reference
+/gbean
+
+gbean name=ClusterStore
class=org.apache.geronimo.system.configuration.RepositoryConfigurati
onStore
+reference name=Repository
+nameClusterRepository/name
+/reference
+/gbean
+
+gbean name=ClusterConfigurationStore
class=org.apache.geronimo.clustering.deployment.BasicClusterConfigur
ationStore
+reference name=ConfigurationStore
+nameClusterStore/name
+/reference
+/gbean
+
+!-- Static Cluster Configuration --
+gbean name=ClusterInfo
class=org.apache.geronimo.clustering.config.BasicClusterInfo
+attribute name=name${PlanClusterName}/attribute
+reference name=NodeInfos/reference
+/gbean
+
+gbean name=NodeInfo
class=org.apache.geronimo.clustering.config.BasicNodeInfo
+ attribute name=nameNodeName/attribute
+ xml-attribute name=extendedJMXConnectorInfo
+ ns:javabean xmlns:ns=http://geronimo.apache.org/
xml/ns/deployment/javabean-1.0
class=org.apache.geronimo.clustering.config.BasicExtendedJMXConnecto
rInfo
+ ns:property name=usernamesystem/ns:property
+ ns:property name=passwordmanager/ns:property
+ ns:property name=protocolrmi/ns:property
+ ns:property name=hostlocalhost/ns:property
+ ns:property name=port1099/ns:property
+ ns:property name=urlPathJMXConnector/
ns:property
+ ns:property name=localtrue/ns:property
+ /ns:javabean
+ /xml-attribute
+ /gbean
+
/module
[BUILD] 2.0: Failed for Revision: 595021
Geronimo Revision: 595021 built with tests included See the full build-1500.log file at http://people.apache.org/~prasad/binaries/2.0/20071114/build-1500.log codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) Path to dependency: 1) org.apache.geronimo.plugins:testsuite-maven-plugin:maven-plugin:2.0.3-SNAPSHOT 2) jtidy:jtidy:jar:8.0-SNAPSHOT Caused by I/O exception: Connection timed out [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error transferring file jtidy:jtidy:jar:8.0-20060801.131059-3 from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), jtidy.sourceforge (http://jtidy.sourceforge.net/snapshots), 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/) Path to dependency: 1) org.apache.geronimo.plugins:testsuite-maven-plugin:maven-plugin:2.0.3-SNAPSHOT 2) jtidy:jtidy:jar:8.0-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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(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.artifact.resolver.ArtifactResolutionException: Error transferring file jtidy:jtidy:jar:8.0-20060801.131059-3 from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), jtidy.sourceforge (http://jtidy.sourceforge.net/snapshots), 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/) Path to dependency: 1) org.apache.geronimo.plugins:testsuite-maven-plugin:maven-plugin:2.0.3-SNAPSHOT 2) jtidy:jtidy:jar:8.0-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:201) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:294) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more Caused by: org.apache.maven.wagon.TransferFailedException: Error transferring file at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:104) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:462) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:347
RE: Moving to TranQL 1.4 ?
Whoa, that's great! If there's anything I could do to help - I'd gladly do. Thank you! Vasily -Original Message- From: Matt Hogstrom [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 14, 2007 9:36 PM To: dev@geronimo.apache.org Subject: Re: Moving to TranQL 1.4 ? Hi Vasiliy, I put a draft out about two weeks ago and need to publish the final. I'd expect with Thanksgiving and some other stuff I'd be able to get going in early December. On Nov 13, 2007, at 10:40 PM, Zakharov, Vasily M wrote: Matt, Are there any news on that? :) Thanks! Vasily -Original Message- From: Matt Hogstrom [mailto:[EMAIL PROTECTED] Sent: Friday, October 05, 2007 8:48 AM To: dev@geronimo.apache.org Subject: Re: Moving to TranQL 1.4 ? Excellent ... I'm finishing some other performance work. When I get that completed I'd like to get this tested. It will be nice to finally run the monster ;-P On Oct 4, 2007, at 11:29 PM, Zakharov, Vasily M wrote: Hi, Matt, Great to hear from you, and great to hear the news! I've tried to update the deployment plans to G2.0.1 as best as I could, here's what I have now: http://cwiki.apache.org/confluence/download/attachments/64828/sjas- app.x ml http://cwiki.apache.org/confluence/download/attachments/64828/sjas- db.xm l http://cwiki.apache.org/confluence/download/attachments/64828/sjas- jms.x ml http://cwiki.apache.org/confluence/display/GMOxDOC20/ SPECjAppServer2004 It has issues working (e. g. for now I can't lookup the beans through JNDI externally), but at least it deploys with no errors. I assume some things there are anyway obsolete and have to be replaced. Please also note issues OPENEJB-700 and OPENEJB-701 filed while trying to make the things above work, adjustments were made to workaround OPENEJB-701. Thanks alot for your help! Vasily -Original Message- From: Matt Hogstrom [mailto:[EMAIL PROTECTED] Sent: Friday, October 05, 2007 6:56 AM To: dev@geronimo.apache.org Subject: Re: Moving to TranQL 1.4 ? Vasily, We've moved from TranQL for the support of CMP to OpenJPA. Dain provided a neat bridge so we can use the same technology for EJB 3 and EJB 2.x. At this point you can achieve the desired results using the orm.xml and OpenJPA configuration. I'd be interested in helping you out on this. Do you have a current set of DDs your working from or are these the same ones as we had back in http://svn.apache.org/ repos/asf/geronimo/sandbox/specjappserver2004/ On Oct 4, 2007, at 8:57 PM, Zakharov, Vasily M wrote: Hi, Are there any plans of moving to the next version of TranQL, 1.3.1 or maybe 1.4-SNAPSHOT? Both seem to be available at http://dist.codehaus.org/tranql/jars/ When I was working with G1.x last year, it was found that a critical flaw exists in TranQL 1.3, that prevents SPECjAppServer2004 from successfuly running on Geronimo - SjAS requires a support of READ_COMMITTED and REPEATABLE_READ transaction isolation levels in XA mode, and TranQL 1.3 only supports READ_UNCOMMITTED level. Issue GERONIMO-2128 http://issues.apache.org/jira/browse/ GERONIMO-2128 is related to this issue, and it's still open. At that time Matt Hostrom said he has plans to add the necessary support in TranQL 1.3.1 or 1.4, but as I can see, G2.0.1 still uses TranQL 1.3: http://article.gmane.org/gmane.comp.java.geronimo.user/3427 http://thread.gmane.org/gmane.comp.java.openejb.devel/3926 Matt, could you, or anyone else, please shed some light on the current situation with this issue? Thank you very much! Vasily Zakharov Intel ESSD --- Closed Joint Stock Company Intel A/O Registered legal address: 125252, Moscow, Russian Federation, Chapayevsky Per, 14. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Closed Joint Stock Company Intel A/O Registered legal address: 125252, Moscow, Russian Federation, Chapayevsky Per, 14. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Closed Joint Stock Company Intel A/O Registered legal address: 125252, Moscow, Russian Federation, Chapayevsky Per, 14. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the
[jira] Commented: (GSHELL-37) New Command: clear
[
https://issues.apache.org/jira/browse/GSHELL-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542606
]
Jason Dillon commented on GSHELL-37:
You can disable ANSI colors w/:
{noformat}
./bin/gsh -C off
{noformat}
or setting the terminal:
{noformat}
./bin/gsh -T none
{noformat}
But, need to see what the behavior is in Windows... dunno, have to peep at the
src to see what it does with clear. I think its all ANSI so it probs won't
work either way. But not sure atm.
As for the warning. I would just check if ANSI is enabled in the terminal and
if its not then spit out the warning, else do the clear.
New Command: clear
--
Key: GSHELL-37
URL: https://issues.apache.org/jira/browse/GSHELL-37
Project: GShell
Issue Type: New Feature
Security Level: public(Regular issues)
Components: Commands
Reporter: Jason Warner
Assignee: Jason Warner
Fix For: 1.0-alpha-1
Attachments: GShell-37.patch
Implement the ability to use the clear command.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3602) SEI specified in webservices.xml does not overwrite annotation
[ https://issues.apache.org/jira/browse/GERONIMO-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542605 ] Jarek Gawor commented on GERONIMO-3602: --- Committed some fixes for CXF to trunk (revision 595080). Also, added some tests for this issue (revision 595082). SEI specified in webservices.xml does not overwrite annotation -- Key: GERONIMO-3602 URL: https://issues.apache.org/jira/browse/GERONIMO-3602 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: webservices Affects Versions: 2.0.x, 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor Looks like SEI specified in the webservices.xml is getting ignored with CXF and Axis2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2898) Can't edit Jetty SSL Connector in Geronimo console
[ https://issues.apache.org/jira/browse/GERONIMO-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-2898. Can't edit Jetty SSL Connector in Geronimo console -- Key: GERONIMO-2898 URL: https://issues.apache.org/jira/browse/GERONIMO-2898 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.0-M2 Environment: Linux Reporter: Karthiga Rajeevani Ratnam Assignee: Anita Kulshreshtha Fix For: 2.0-M5 Attachments: 2898-new.patch, 2898.patch, JettySSLConnector Error.jpg I tried to edit JettySSLConnector listed under Network Listeners and got the following error in command prompt. 15:06:50,729 ERROR [PortletFragment] Error in Portlet java.lang.IllegalArgumentException: No such method found (getMinThreads on org.apache.geronimo.jetty6.JettyWebConnector$$EnhancerByCGLIB$$5aaaf276) at org.apache.geronimo.console.BasePortlet.getProperty(BasePortlet.java:92) at org.apache.geronimo.console.webmanager.ConnectorPortlet.doView(ConnectorPortlet.java:388) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(JettySecurityHandler.java:133) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46) at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47) at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:67) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:192) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:73) at org.apache.pluto.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:119) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.renderPortlet(PortletContainerWrapperImpl.java:70) at org.apache.pluto.portalImpl.aggregation.PortletFragment.service(PortletFragment.java:168) at jsp.WEB_002dINF.aggregation.ColumnFragment_jsp._jspService(ColumnFragment_jsp.java:70) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:62) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(JettySecurityHandler.java:133) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46) at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47) at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:67) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:192) at
[jira] Closed: (GERONIMO-3490) Missing Jetty Connector stats
[ https://issues.apache.org/jira/browse/GERONIMO-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha closed GERONIMO-3490. Missing Jetty Connector stats - Key: GERONIMO-3490 URL: https://issues.apache.org/jira/browse/GERONIMO-3490 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Jetty Affects Versions: 2.1 Environment: windows xp Reporter: Viet Hung Nguyen Assignee: Anita Kulshreshtha Fix For: 2.1 Attachments: geronimo-3490.patch, geronimo-3490b.patch Jetty6 provides connector statistics, but they are not being surfaced in Geronimo's source code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo IRC logs
Thanks Kevan! Anita --- Kevan Miller [EMAIL PROTECTED] wrote: On Nov 8, 2007 8:55 AM, Anita Kulshreshtha [EMAIL PROTECTED] wrote: Does anyone know why IRC is not being logged? I think this should be fixed, now... Somebody needs to start an IRC conversation, before we know for sure... ;-) --kevan Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ
[jira] Commented: (GERONIMO-3602) SEI specified in webservices.xml does not overwrite annotation
[ https://issues.apache.org/jira/browse/GERONIMO-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542655 ] Jarek Gawor commented on GERONIMO-3602: --- The JSR-109 specs says the following: The service-endpoint-interface element in the deployment descriptor for an implementation bean must match @WebService.endpointInterface member attribute if it is specified for the bean. Any other value is ignored. which I interpret as saying that service-endpoint-interface override in the deployment descriptor only works for beans where @WebService.endpointInterface member attribute is not set. If the member attribute is set, the service-endpoint-interface element in DD is effectively ignored. I committed some more changes to match this understanding for CXF to trunk (revision 595185) and updated tests (revision 595186). SEI specified in webservices.xml does not overwrite annotation -- Key: GERONIMO-3602 URL: https://issues.apache.org/jira/browse/GERONIMO-3602 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: webservices Affects Versions: 2.0.x, 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor Looks like SEI specified in the webservices.xml is getting ignored with CXF and Axis2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3602) SEI specified in webservices.xml does not overwrite annotation
[ https://issues.apache.org/jira/browse/GERONIMO-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542663 ] Jarek Gawor commented on GERONIMO-3602: --- For Axis2, this might be a little more difficult. First, Axis2 uses wsgen tool to generate the WSDL. wsgen requires the service endpoint _implementation_ to be passed. It does not accept service endpoint interface (SEI) class and there is no other way to pass the SEI. So for the override to work (for web services without packaged wsdl) we would have to generate a temporary class with right annotation and pass that to wsgen. That might be a lot work for something that might be handled in another way. So for now we are not going to support this override in Axis2. SEI specified in webservices.xml does not overwrite annotation -- Key: GERONIMO-3602 URL: https://issues.apache.org/jira/browse/GERONIMO-3602 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: webservices Affects Versions: 2.0.x, 2.1 Reporter: Jarek Gawor Assignee: Jarek Gawor Looks like SEI specified in the webservices.xml is getting ignored with CXF and Axis2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-37) New Command: clear
[ https://issues.apache.org/jira/browse/GSHELL-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GSHELL-37: --- Attachment: GShell-37ANSI.patch This worked as expected on linux. I tried testing on windows, but I had issues building GShell on windows. The error was actually an error in ant 1.7.0. Have you had an issue with this? New Command: clear -- Key: GSHELL-37 URL: https://issues.apache.org/jira/browse/GSHELL-37 Project: GShell Issue Type: New Feature Security Level: public(Regular issues) Components: Commands Reporter: Jason Warner Assignee: Jason Warner Fix For: 1.0-alpha-1 Attachments: GShell-37.patch, GShell-37ANSI.patch Implement the ability to use the clear command. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: WSIT Support
For servicemix cxf bc, we support ws-security, ws-ReliableMessage, ws-policy, ws-Addressing, MTOM now Regards Freeman ArmenH wrote: Yes, thank you for replying. Please confirm whether any of the WS-* specs below are not supported. We would need a true Enterprise solution for our financial systems. Thanks again for your kind attention. WS-Trust WS-Security WS-SecureConversation WS-Federation WS-ReliableMessaging WS-AtomicTransaction WS-Coordination WS-MetadataExchange WS-Policy WS-Addressing MTOM Freeman Fang-2 wrote: From my understanding, I think the question is What's the CXF version used in servicemix? :-) Regards Freeman Bozhong Lin wrote: Just to clarify, I think CXF is used in ServiceMix version 3.2, not version 2.0.2. Regards, Bo On Nov 13, 2007 1:10 PM, Freeman Fang wrote: Yes Freeman ArmenH wrote: Thanks, Is the CXF used in ServiceMix version 2.0.2? Freeman Fang wrote: Hi, We already have servicemix-cxf-bc to leverage ws-* feature from cxf. And I also know cxf team do lots of interoperability test between cxf and WCF(including ws-* feature), if you are interested in this issue, I guess you could post this thread on cxf mailling list, where more people can answer your question. Best Regards Freeman ArmenH wrote: It appears that CXF does support most of the WS-* Has anyone used Microsoft WCF based clients/services to show full interoperability? ArmenH wrote: Does ServiceMix fully support WSIT? If not, are there plans to support it? CXF is still not fully compliant with WSIT.
Re: Deploying jboss seam 2.0.0.GA's jee5 sample onto geronimo 2.1-SNAPSHOT...almost done
On Nov 11, 2007 2:55 PM, Jacek Laskowski [EMAIL PROTECTED] wrote: When an EAR comes with an ejb module that in turn contains persistence.xml, when the ear's deployed openejb runs on the scene and searches for META-INF/persistence.xml and tries to create gbeans for PUs. Of course, when the ejb module's deployed openejb deploys it again. There's PersistenceUnitBuilderExtension or such that's executed twice and thus resulting with unnecessary work for processing PUs. I think that's where the issue of duplicate class definition comes from - openejb deploys PUs twice and since there's only one module with a plan it leads to the error. I'm digging into it, but if anybody could shed some light on it or point into a right direction I'd greatly appreciate it. I think I'm very close to deploy the sample, but don't know how much changes I should do in the sample itself or geronimo PUs processing. If it's sounded awkward, it is such, as I can't explain it better now. Still debugging it. Hi, Just to let you know I'm still working on it and ended up with the following plan with no changes to the sample application - booking. With the plan I can easily deploy the sample, seam starts up fine...almost. The PU the application uses is not injected, but the duplicate class...something is not reported. Any comments greatly appreciated. ?xml version=1.0 encoding=UTF-8? application xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; environment xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2; moduleId groupIdorg.jboss.seam.examples.jee5/groupId artifactIdjboss-seam-jee5/artifactId version2.0.0.GA/version typeear/type /moduleId dependencies dependency groupIdorg.apache.geronimo.hibernate.transaction/groupId artifactIdgeronimo-hibernate-transaction-manager-lookup/artifactId typejar/type /dependency /dependencies /environment module webjboss-seam-jee5.war/web web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1; environment xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2; moduleId groupIdorg.jboss.seam.examples.jee5/groupId artifactIdjboss-seam-jee5/artifactId version2.0.0.GA/version typewar/type /moduleId /environment context-root/seam-jee5/context-root /web-app /module module ejbjboss-seam-jee5.jar/ejb openejb-jar xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; environment xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2; moduleId groupIdorg.jboss.seam.examples.jee5/groupId artifactIdjboss-seam-jee5/artifactId version2.0.0.GA/version typejar/type /moduleId /environment !-- overrides what's in the module's persistence.xml -- persistence xmlns=http://java.sun.com/xml/ns/persistence; persistence-unit name=bookingDatabase providerorg.apache.openjpa.persistence.PersistenceProviderImpl/provider jta-data-sourcejdbc/__default/jta-data-source classorg.jboss.seam.example.booking.Booking/class classorg.jboss.seam.example.booking.Hotel/class classorg.jboss.seam.example.booking.User/class exclude-unlisted-classestrue/exclude-unlisted-classes properties property name=hibernate.transaction.manager_lookup_class value=org.apache.geronimo.hibernate.transaction.GeronimoTransactionManagerLookup / /properties /persistence-unit !-- change the way the default PU works - make it an alias to bookingDatabase PU -- persistence-unit name=cmp classorg.jboss.seam.example.booking.Booking/class classorg.jboss.seam.example.booking.Hotel/class classorg.jboss.seam.example.booking.User/class exclude-unlisted-classestrue/exclude-unlisted-classes /persistence-unit /persistence /openejb-jar /module !-- module ejbjboss-seam.jar/ejb openejb-jar xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; environment xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2; moduleId groupIdorg.jboss.seam.examples.jee5/groupId artifactIdjboss-seam/artifactId version2.0.0.GA/version typejar/type /moduleId /environment /openejb-jar /module -- ext-module connectorseam-jee5-dbpool/connector external-path xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; dep:groupIdorg.tranql/dep:groupId dep:artifactIdtranql-connector-derby-embed-xa/dep:artifactId dep:typerar/dep:type /external-path connector xmlns=http://geronimo.apache.org/xml/ns/j2ee/connector-1.2; environment xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2; moduleId groupIdorg.jboss.seam.examples.jee5/groupId artifactIdbooking-dbpool/artifactId
