date:20100519


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

David Jencks commented on GERONIMO-4918:


I think I got all the changes ported to 3.0 (trunk) in rev 946044.

 EJB 3.1 Singleton Support
 -

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

 Attachments: GERONIMO-4918.patch, 
 geronimo-singleton-support-geronimo.patch, LoadOnStartupGBean.java, 
 singleton-deploy-type.patch, SingletonDeploymentGBean.java


 The singleton support hasn't been completely implemented, so it's impossible 
 to deploy an singleton session bean (EJB).
 I added the support, recompiled + tested and it's working.
 The patch requires creating a new file, so both need to be applied.
 The patch was made from the root of the svn checkout of branches/2.2. 
 The new files path from the same root is: 
 plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/SingletonDeploymentGBean.java

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

[jira] Commented: (GERONIMO-4918) EJB 3.1 Singleton Support


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

David Jencks commented on GERONIMO-4918:


um, rev 946044 only has the plugins/openejb changes.  More is needed.

 EJB 3.1 Singleton Support
 -

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

 Attachments: GERONIMO-4918.patch, 
 geronimo-singleton-support-geronimo.patch, LoadOnStartupGBean.java, 
 singleton-deploy-type.patch, SingletonDeploymentGBean.java


 The singleton support hasn't been completely implemented, so it's impossible 
 to deploy an singleton session bean (EJB).
 I added the support, recompiled + tested and it's working.
 The patch requires creating a new file, so both need to be applied.
 The patch was made from the root of the svn checkout of branches/2.2. 
 The new files path from the same root is: 
 plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/SingletonDeploymentGBean.java

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

[jira] Closed: (GERONIMO-4157) Generating plan for EAR on minimal install leads to Null Pointer Exception

2010-05-19 Thread viola.lu (JIRA)


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

viola.lu closed GERONIMO-4157.
--

Resolution: Fixed

NPE doesn't exist in latest geronimo 2.2.1 tomcat version, so close it.

 Generating plan for EAR on minimal install leads to Null Pointer Exception
 --

 Key: GERONIMO-4157
 URL: https://issues.apache.org/jira/browse/GERONIMO-4157
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: PlanCreator
Affects Versions: 2.2
 Environment: Ubuntu 7.10, Firefox 2.0.0.11
Reporter: Joseph Leong
 Fix For: 2.2.1


 When feeding the bank-ear-2.2-SNAPSHOT.ear into this plan creator on a 
 minimal-tomcat-6 server, it leads to a NPE:
 java.lang.NullPointerException
   
 org.apache.geronimo.console.configcreator.GetArchiveHandler.actionAfterView(GetArchiveHandler.java:71)
   
 org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:114)
   org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
   org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
   
 org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
   
 org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
   
 org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219)
   
 org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
   
 org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:806)

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

[jira] Commented: (GERONIMO-5324) the Console navigation is always displayed in Chinese although the browser language has been set to English-US

2010-05-19 Thread Shawn Jiang (JIRA)


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

Shawn Jiang commented on GERONIMO-5324:
---

Do all browsers(IE, firefox, chrome) in windows XP have the same behavior ?

 the Console  navigation is always displayed in Chinese although the browser 
 language has been set to English-US
 -

 Key: GERONIMO-5324
 URL: https://issues.apache.org/jira/browse/GERONIMO-5324
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2.1
 Environment: windows XP(with JDK1.5  JDK1.6)
 Linux SUSE 10
Reporter: LiWenQin
Priority: Minor
 Fix For: 2.2.1


 In the Windows XP, the Console  navigation is always displayed in Chinese 
 although the browser language has been set to English-US. I have tried it on 
 several virtual machines and the problem always happens.
 However, this problem does't appear in the LINUX SUSE 10.
 Please help pay attention to it and find out whether the problem is only 
 displayed in my enviroment...
 ps:In the Windows XP, the Console  navigation could display in Japanese if 
 the browser language has been set to Japanese.

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

[jira] Commented: (GERONIMO-5324) the Console navigation is always displayed in Chinese although the browser language has been set to English-US

2010-05-19 Thread Shawn Jiang (JIRA)


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

Shawn Jiang commented on GERONIMO-5324:
---

Please also make sure you cleaned the brower cache before swithing the browser 
locale.  

 the Console  navigation is always displayed in Chinese although the browser 
 language has been set to English-US
 -

 Key: GERONIMO-5324
 URL: https://issues.apache.org/jira/browse/GERONIMO-5324
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2.1
 Environment: windows XP(with JDK1.5  JDK1.6)
 Linux SUSE 10
Reporter: LiWenQin
Priority: Minor
 Fix For: 2.2.1


 In the Windows XP, the Console  navigation is always displayed in Chinese 
 although the browser language has been set to English-US. I have tried it on 
 several virtual machines and the problem always happens.
 However, this problem does't appear in the LINUX SUSE 10.
 Please help pay attention to it and find out whether the problem is only 
 displayed in my enviroment...
 ps:In the Windows XP, the Console  navigation could display in Japanese if 
 the browser language has been set to Japanese.

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

[jira] Assigned: (GERONIMO-5300) Class not found:org/apache/axis2/jaxws/ClientConfigurationFactory

2010-05-19 Thread Ivan (JIRA)


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

Ivan reassigned GERONIMO-5300:
--

Assignee: Ivan

 Class not found:org/apache/axis2/jaxws/ClientConfigurationFactory
 -

 Key: GERONIMO-5300
 URL: https://issues.apache.org/jira/browse/GERONIMO-5300
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: webservices
Affects Versions: 3.0
 Environment: OS:Win xp
 Server:GERONIMO 3.0-SNAPSHOT 
 JDK:1.6
Reporter: Lu Jiang
Assignee: Ivan
 Attachments: jaxws-calculator-war.war


 Try Geronimo sample jaxws-Calculator.war(see attached file ) on Geronimo 3.0 
 build.An class not found error will occur.
 org/apache/axis2/jaxws/ClientConfigurationFactory
 java.lang.NoClassDefFoundError: 
 org/apache/axis2/jaxws/ClientConfigurationFactory
   at 
 org.apache.geronimo.axis2.builder.Axis2ServiceRefBuilder.registerConfigGBean(Axis2ServiceRefBuilder.java:89)
   at 
 org.apache.geronimo.axis2.builder.Axis2ServiceRefBuilder.createService(Axis2ServiceRefBuilder.java:64)
   at 
 org.apache.geronimo.jaxws.builder.JAXWSServiceRefBuilder.buildNaming(JAXWSServiceRefBuilder.java:164)
   at 
 org.apache.geronimo.jaxws.builder.JAXWSServiceRefBuilder.buildNaming(JAXWSServiceRefBuilder.java:103)
   at 
 org.apache.geronimo.naming.deployment.SwitchingServiceRefBuilder.buildNaming(SwitchingServiceRefBuilder.java:139)
   at 
 org.apache.geronimo.j2ee.deployment.NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:68)
   at 
 org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.configureBasicWebModuleAttributes(AbstractWebModuleBuilder.java:706)
   at 
 org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:408)
   at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:175)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:690)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138)
   at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
   at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:856)
   at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
   at 
 org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
   at 
 org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
   at java.lang.Thread.run(Thread.java:619)
 Caused by: java.lang.ClassNotFoundException: 
 org.apache.axis2.jaxws.ClientConfigurationFactory
   at 
 org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:814)
   at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:61)
   at 
 org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1733)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
   at 
 org.apache.felix.framework.ModuleImpl.getClassByDelegation(ModuleImpl.java:674)
   at 
 org.apache.felix.framework.searchpolicy.R4Wire.getClass(R4Wire.java:108)
   at 
 org.apache.felix.framework.ModuleImpl.searchImports(ModuleImpl.java:1440)
   at 
 org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:753)
   at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:61)
   at 
 org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1733)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
   ... 22 more

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

[jira] Commented: (GERONIMO-5300) Class not found:org/apache/axis2/jaxws/ClientConfigurationFactory

2010-05-19 Thread Ivan (JIRA)


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

Ivan commented on GERONIMO-5300:


The exception is caused by the split-package issue with axis2, later, I found 
there is a missing import package in axiom-api.
After making those two bundles work correctly, it seems that the web serivce 
integration codes need to update.

 Class not found:org/apache/axis2/jaxws/ClientConfigurationFactory
 -

 Key: GERONIMO-5300
 URL: https://issues.apache.org/jira/browse/GERONIMO-5300
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: webservices
Affects Versions: 3.0
 Environment: OS:Win xp
 Server:GERONIMO 3.0-SNAPSHOT 
 JDK:1.6
Reporter: Lu Jiang
Assignee: Ivan
 Attachments: jaxws-calculator-war.war


 Try Geronimo sample jaxws-Calculator.war(see attached file ) on Geronimo 3.0 
 build.An class not found error will occur.
 org/apache/axis2/jaxws/ClientConfigurationFactory
 java.lang.NoClassDefFoundError: 
 org/apache/axis2/jaxws/ClientConfigurationFactory
   at 
 org.apache.geronimo.axis2.builder.Axis2ServiceRefBuilder.registerConfigGBean(Axis2ServiceRefBuilder.java:89)
   at 
 org.apache.geronimo.axis2.builder.Axis2ServiceRefBuilder.createService(Axis2ServiceRefBuilder.java:64)
   at 
 org.apache.geronimo.jaxws.builder.JAXWSServiceRefBuilder.buildNaming(JAXWSServiceRefBuilder.java:164)
   at 
 org.apache.geronimo.jaxws.builder.JAXWSServiceRefBuilder.buildNaming(JAXWSServiceRefBuilder.java:103)
   at 
 org.apache.geronimo.naming.deployment.SwitchingServiceRefBuilder.buildNaming(SwitchingServiceRefBuilder.java:139)
   at 
 org.apache.geronimo.j2ee.deployment.NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:68)
   at 
 org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.configureBasicWebModuleAttributes(AbstractWebModuleBuilder.java:706)
   at 
 org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:408)
   at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:175)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:690)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138)
   at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
   at 
 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
   at 
 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:856)
   at 
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
   at 
 org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
   at 
 org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
   at java.lang.Thread.run(Thread.java:619)
 Caused by: java.lang.ClassNotFoundException: 
 org.apache.axis2.jaxws.ClientConfigurationFactory
   at 
 org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:814)
   at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:61)
   at 
 org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1733)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
   at 
 org.apache.felix.framework.ModuleImpl.getClassByDelegation(ModuleImpl.java:674)
   at 
 org.apache.felix.framework.searchpolicy.R4Wire.getClass(R4Wire.java:108)
   at 
 org.apache.felix.framework.ModuleImpl.searchImports(ModuleImpl.java:1440)
   at 
 org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:753)
   at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:61)
   at 
 org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1733)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
   ... 22 more

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

[jira] Commented: (GERONIMO-5324) the Console navigation is always displayed in Chinese although the browser language has been set to English-US

2010-05-19 Thread LiWenQin (JIRA)


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

LiWenQin commented on GERONIMO-5324:


Hi,Shawn,
I have clear the browser cache(in IE, firefox, chrome) .
But the bug always appears.

 the Console  navigation is always displayed in Chinese although the browser 
 language has been set to English-US
 -

 Key: GERONIMO-5324
 URL: https://issues.apache.org/jira/browse/GERONIMO-5324
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2.1
 Environment: windows XP(with JDK1.5  JDK1.6)
 Linux SUSE 10
Reporter: LiWenQin
Priority: Minor
 Fix For: 2.2.1


 In the Windows XP, the Console  navigation is always displayed in Chinese 
 although the browser language has been set to English-US. I have tried it on 
 several virtual machines and the problem always happens.
 However, this problem does't appear in the LINUX SUSE 10.
 Please help pay attention to it and find out whether the problem is only 
 displayed in my enviroment...
 ps:In the Windows XP, the Console  navigation could display in Japanese if 
 the browser language has been set to Japanese.

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

Geronimo Revision: 946057 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100519/build-0300.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100519/unit-test-reports
 
2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-ajp -Dversion=8.0.0.M1-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=org.eclipse.jetty -DartifactId=jetty-ajp 
-Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
-DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT

3) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-jaspi -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-jaspi -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT

4) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-webapp -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-webapp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT

5) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-security -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-security -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT

6) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-servlet -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-servlet -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT

--
6 required artifacts are missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots),
  local (file:///home/geronimo/.m2/jtidy.repository),
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  java.net.2 (http://download.java.net/maven/1/),
  jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/),
  openqa-releases (http://nexus.openqa.org/content/repositories/releases),
  axis2-axiom-api 
(https://repository.apache.org/content/repositories/orgapachegeronimo-002/),
  smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360

[jira] Resolved: (GERONIMO-5163) Admin console assemble server problems

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

Rex Wang resolved GERONIMO-5163.

Resolution: Fixed

Admin console assemble server problems
--

Key: GERONIMO-5163
URL: https://issues.apache.org/jira/browse/GERONIMO-5163
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.2.1
Reporter: Kevan Miller
Assignee: Rex Wang
Priority: Blocker
Fix For: 2.2.1

1) The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go
to assemble server page, click expert user and try to scroll down. Unless I
make the font type very small, I can't see the system plugins and can't
scroll down to them.
2) Also, the default value for assembly target path used to default to
var/temp. It doesn't default to anything
3) This is a potentially very bad problem (and be very careful testing or you
will lose files). The assembly process seems to be trying to clean up after
itself -- which is nice. However, if you specify an existing directory, it
will wipe out all of the files in your directory. I specified the root
directory of my server and it deleted the entire server. Very bad and could
have been worse!. We should be generating a temporary directory and only
deleting this temporary directory, only.

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

[jira] Commented: (GERONIMO-5163) Admin console assemble server problems

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

Rex Wang commented on GERONIMO-5163:

I fixed #2 #3 in rev946083 @ 2.2 branch.

1# is caused by the changes in the console structure oi 2.2.x, which use the
iframe to show the portlet pages. I also found a lot of such problems in
other pages, so will open another JIRA to track this issue.

-Rex

Admin console assemble server problems
--

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

[jira] Issue Comment Edited: (GERONIMO-5163) Admin console assemble server problems

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

Rex Wang edited comment on GERONIMO-5163 at 5/19/10 4:45 AM:
-

I fixed #2 #3 in rev946083 @ 2.2 branch.

#1 is caused by the changes in the console structure of 2.2.x, which use the
iframe to show the portlet pages. I also found a lot of such problems in
other pages, so will open another JIRA to track this issue.

-Rex

was (Author: rwonly):
I fixed #2 #3 in rev946083 @ 2.2 branch.

-Rex

Admin console assemble server problems
--

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

[jira] Created: (GERONIMO-5325) iframe causes some portlets display incorrectly

iframe causes some portlets display incorrectly
---

 Key: GERONIMO-5325
 URL: https://issues.apache.org/jira/browse/GERONIMO-5325
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.2
Reporter: Rex Wang
 Fix For: 2.2.1


#1. The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go 
to assemble server page, click expert user and try to scroll down. Unless I 
make the font type very small, I can't see the system plugins and can't scroll 
down to them. 
#2, This also cause the debugviews portlet displays incorrectly.


See the attachment.

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

[jira] Updated: (GERONIMO-5325) iframe causes some portlets display incorrectly


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

Rex Wang updated GERONIMO-5325:
---

Attachment: screenshot-1-assembly-portlet.jpg

 iframe causes some portlets display incorrectly
 ---

 Key: GERONIMO-5325
 URL: https://issues.apache.org/jira/browse/GERONIMO-5325
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
Reporter: Rex Wang
 Fix For: 2.2.1

 Attachments: screenshot-1-assembly-portlet.jpg


 #1. The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go 
 to assemble server page, click expert user and try to scroll down. Unless I 
 make the font type very small, I can't see the system plugins and can't 
 scroll down to them. 
 #2, This also cause the debugviews portlet displays incorrectly.
 See the attachment.

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

[jira] Commented: (GERONIMO-5325) iframe causes some portlets display incorrectly

2010-05-19 Thread Shawn Jiang (JIRA)


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

Shawn Jiang commented on GERONIMO-5325:
---

The reason of this JIRA is the same with 
https://issues.apache.org/jira/browse/GERONIMO-5218

I believe the fix could be the same.   I also plan to move iframe to div in the 
future to fix this kind of problems completely.  But I would not do it in 2.2.1 
release.

 iframe causes some portlets display incorrectly
 ---

 Key: GERONIMO-5325
 URL: https://issues.apache.org/jira/browse/GERONIMO-5325
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
Reporter: Rex Wang
 Fix For: 2.2.1

 Attachments: screenshot-1-assembly-portlet.jpg, 
 screenshot-debug-views.jpg


 #1. The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go 
 to assemble server page, click expert user and try to scroll down. Unless I 
 make the font type very small, I can't see the system plugins and can't 
 scroll down to them. 
 #2, This also cause the debugviews portlet displays incorrectly.
 See the attachment.

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

[jira] Updated: (GERONIMO-5325) iframe causes some portlets display incorrectly


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

Rex Wang updated GERONIMO-5325:
---

Attachment: screenshot-debug-views.jpg

 iframe causes some portlets display incorrectly
 ---

 Key: GERONIMO-5325
 URL: https://issues.apache.org/jira/browse/GERONIMO-5325
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
Reporter: Rex Wang
 Fix For: 2.2.1

 Attachments: screenshot-1-assembly-portlet.jpg, 
 screenshot-debug-views.jpg


 #1. The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go 
 to assemble server page, click expert user and try to scroll down. Unless I 
 make the font type very small, I can't see the system plugins and can't 
 scroll down to them. 
 #2, This also cause the debugviews portlet displays incorrectly.
 See the attachment.

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

[jira] Commented: (GERONIMO-5163) Admin console assemble server problems

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

Rex Wang commented on GERONIMO-5163:

https://issues.apache.org/jira/browse/GERONIMO-5325 for the issues in #1

Admin console assemble server problems
--

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

[jira] Updated: (GERONIMO-5325) iframe causes some portlets display incorrectly

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

Rex Wang updated GERONIMO-5325:
---

Description:
#1. The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go
to assemble server page, click expert user and try to scroll down. Unless I
make the font type very small, I can't see the system plugins and can't scroll
down to them.
#2, This also cause the debugviews portlet displays incorrectly.
#3, Go to repository portlet first, and then go to JMS Resources portlet. The
scroll bar is pretty long and when you scroll down, you can see there is a
huge blank at the bottom of the page.

See the attachment.

was:
#1. The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go
to assemble server page, click expert user and try to scroll down. Unless I
make the font type very small, I can't see the system plugins and can't scroll
down to them.
#2, This also cause the debugviews portlet displays incorrectly.

See the attachment.

iframe causes some portlets display incorrectly
---

Key: GERONIMO-5325
URL: https://issues.apache.org/jira/browse/GERONIMO-5325
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.2
Reporter: Rex Wang
Fix For: 2.2.1

Attachments: huge-blank.jpg, screenshot-1-assembly-portlet.jpg,
screenshot-debug-views.jpg

#1. The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go
to assemble server page, click expert user and try to scroll down. Unless I
make the font type very small, I can't see the system plugins and can't
scroll down to them.
#2, This also cause the debugviews portlet displays incorrectly.
#3, Go to repository portlet first, and then go to JMS Resources portlet. The
scroll bar is pretty long and when you scroll down, you can see there is a
huge blank at the bottom of the page.
See the attachment.

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

[jira] Updated: (GERONIMO-5325) iframe causes some portlets display incorrectly


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

Rex Wang updated GERONIMO-5325:
---

Attachment: huge-blank.jpg

 iframe causes some portlets display incorrectly
 ---

 Key: GERONIMO-5325
 URL: https://issues.apache.org/jira/browse/GERONIMO-5325
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
Reporter: Rex Wang
 Fix For: 2.2.1

 Attachments: huge-blank.jpg, screenshot-1-assembly-portlet.jpg, 
 screenshot-debug-views.jpg


 #1. The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go 
 to assemble server page, click expert user and try to scroll down. Unless I 
 make the font type very small, I can't see the system plugins and can't 
 scroll down to them. 
 #2, This also cause the debugviews portlet displays incorrectly.
 #3, Go to repository portlet first, and then go to JMS Resources portlet. The 
 scroll bar is pretty long and when you scroll down, you can see  there is a 
 huge blank at the bottom of the page.
 See the attachment.

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

[jira] Updated: (GERONIMO-5325) iframe causes some portlets display incorrectly


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

Rex Wang updated GERONIMO-5325:
---

Attachment: (was: huge-blank.jpg)

 iframe causes some portlets display incorrectly
 ---

 Key: GERONIMO-5325
 URL: https://issues.apache.org/jira/browse/GERONIMO-5325
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
Reporter: Rex Wang
 Fix For: 2.2.1

 Attachments: screenshot-1-assembly-portlet.jpg, 
 screenshot-debug-views.jpg, screenshot-huge-blank.jpg


 #1. The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go 
 to assemble server page, click expert user and try to scroll down. Unless I 
 make the font type very small, I can't see the system plugins and can't 
 scroll down to them. 
 #2, This also cause the debugviews portlet displays incorrectly.
 #3, Go to repository portlet first, and then go to JMS Resources portlet. The 
 scroll bar is pretty long and when you scroll down, you can see  there is a 
 huge blank at the bottom of the page.
 See the attachment.

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

[jira] Updated: (GERONIMO-5325) iframe causes some portlets display incorrectly


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

Rex Wang updated GERONIMO-5325:
---

Attachment: screenshot-huge-blank.jpg

 iframe causes some portlets display incorrectly
 ---

 Key: GERONIMO-5325
 URL: https://issues.apache.org/jira/browse/GERONIMO-5325
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 2.2
Reporter: Rex Wang
 Fix For: 2.2.1

 Attachments: screenshot-1-assembly-portlet.jpg, 
 screenshot-debug-views.jpg, screenshot-huge-blank.jpg


 #1. The assemble server page is not formatting properly in 2.2.1-SNAPSHOT. Go 
 to assemble server page, click expert user and try to scroll down. Unless I 
 make the font type very small, I can't see the system plugins and can't 
 scroll down to them. 
 #2, This also cause the debugviews portlet displays incorrectly.
 #3, Go to repository portlet first, and then go to JMS Resources portlet. The 
 scroll bar is pretty long and when you scroll down, you can see  there is a 
 huge blank at the bottom of the page.
 See the attachment.

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

[BUILD] branches/2.2: Failed for Revision: 946128

Geronimo Revision: 946128 built with tests included
 
See the full build-0800.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100519/build-0800.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100519/unit-test-reports
 
[INFO] [car:package]
[INFO] Packaging module configuration: 
/home/geronimo/geronimo/2.2/framework/configs/jee-specs/target/work/plan.xml
[INFO] Started deployer: 
org.apache.geronimo.framework/geronimo-gbean-deployer-bootstrap/2.2.1-SNAPSHOT/car
[INFO] [car:prepare-metadata]
[INFO] [car:archive-car]
[INFO] Building jar: 
/home/geronimo/geronimo/2.2/framework/configs/jee-specs/target/jee-specs-2.2.1-SNAPSHOT.car
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: jee-specs-2.2.1-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing 
/home/geronimo/geronimo/2.2/framework/configs/jee-specs/target/jee-specs-2.2.1-SNAPSHOT.car
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/framework/jee-specs/2.2.1-SNAPSHOT/jee-specs-2.2.1-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO] 
[INFO] Building Geronimo Framework, Modules :: Naming
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/xbean/xbean-naming/3.7/xbean-naming-3.7.pom
1K downloaded
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/xbean/xbean-naming/3.7/xbean-naming-3.7.jar
53K downloaded
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 27 source files to 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/classes
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Compiling 8 source files to 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/surefire-reports

---
 T E S T S
---
Running org.apache.geronimo.gjndi.binding.GBeanBindingTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.934 sec
Running org.apache.geronimo.gjndi.KernelContextGBeanTest
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.731 sec  
FAILURE!
Running org.apache.geronimo.gjndi.binding.FormatTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running org.apache.geronimo.gjndi.JavaCompGBeanTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.163 sec
Running org.apache.geronimo.gjndi.JavaCompContextTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.497 sec

Results :

Failed tests: 
  test(org.apache.geronimo.gjndi.KernelContextGBeanTest)

Tests run: 15, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/surefire-reports
 for the individual test results.
[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/surefire-reports
 for the individual test results.
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:580)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures

Re: [VOTE] Release Geronimo axis2 and axiom-api bundles (Second Try)

Have we had a conversation with the axis community regarding the split-package 
issue?

Minor point: I note the license/notice files in the jar have different line 
endings (mix of unix and windows line endings). Would prefer that we avoid 
this, but end of the day it's a minor issue...

It looks like there are some Axis2 fixes that we should be picking up from the 
Axis community. I think they should be included in our bundle release. Here's 
my -1. 

--kevan

On May 17, 2010, at 11:51 PM, Ivan wrote:

 Please vote for the geronimo axis2 and axiom-api bundle release, add Notice 
 and License files for axis2 and axiom-api
 
 axis2-1.5 : For there is split-package issue in the axis2 bundles which 
 Geronimo requires.
 axiom-api 1.2.8 : The official bundle does not import javax.xml.stream.util 
 package, althought Geronimo trunk works under JRE 1.6, while the package is 
 not exported by the framework bundle, as we use our own stax bundle.
 
 Staging repo is here:
 
 https://repository.apache.org/content/repositories/orgapachegeronimo-002/
 
 tag is here:
 
 https://svn.apache.org/repos/asf/geronimo/bundles/tags/axiom-api-1.2.8_1/
 https://svn.apache.org/repos/asf/geronimo/bundles/tags/axis2-1.5_1/ 
 
 Vote open 72 hours
 
 [ ] +1 release this
 [ ] 0 don't care
 [ ] -1 don't release this (please explain)
 
 
 -- 
 Ivan

[BUILD] trunk: Failed for Revision: 946169

Geronimo Revision: 946169 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100519/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100519/unit-test-reports
 
2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-ajp -Dversion=8.0.0.M1-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=org.eclipse.jetty -DartifactId=jetty-ajp 
-Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
-DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT

3) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-jaspi -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-jaspi -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT

4) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-webapp -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-webapp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT

5) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-security -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-security -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT

6) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-servlet -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-servlet -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT

--
6 required artifacts are missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots),
  local (file:///home/geronimo/.m2/jtidy.repository),
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  java.net.2 (http://download.java.net/maven/1/),
  jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/),
  openqa-releases (http://nexus.openqa.org/content/repositories/releases),
  axis2-axiom-api 
(https://repository.apache.org/content/repositories/orgapachegeronimo-002/),
  smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360

Re: Runtime entity enhancement for OSGi applications

2010-05-19 Thread Lin Sun

Seems No. 3 is the right approach, given that there is no overhead on
the user side and it gives the ability to add the imports at the last
minute, before the PU is resolved.

No. 2 gives some extra work on the user side which can make the PU not portable.

Np. 4 has to be done when PU is installed, and it is possible the
provider is not even there yet.

No. 5 can be confusing to the user as a fragment is attached to their PU.

Lin

On Tue, May 18, 2010 at 10:41 PM, Jarek Gawor jga...@gmail.com wrote:
 Hi all,

 I was looking into getting the runtime JPA entity enhancement for OSGi
 applications working in Geronimo. With some modifications to the Aries
 JPA code and some to Geronimo I was able to get runtime enhancement
 working (using the java agent approach) but with one major issue: The
 bundle that contains the persistence unit must be able to load some
 persistence provider specific (in our case openjpa) classes. That's
 because during the bytecode weaving, openjpa adds some openjpa
 specific interfaces to the entity classes. So how should we deal with
 this issue in Geronimo?

 1) We could do nothing and just say we don't support runtime enhancement.

 2) We could support runtime enhancement and require that bundles with
 PU have DynamicImport-Package: * header.

 3) Use framework classloader hooks to dynamically add imports for
 the persistence provider specific packages to the bundles with PU .
 That of course, would rely on framework specific extensions. I know
 Equinox has such hooks and I think recently something similar was
 added to Felix.

 4) Provide some url handler, e.g. jpa which would enhance the entity
 classes and add right imports during the install. Something similar to
 the webbundle url handler for web application archives. Of course,
 we would have to make sure the bundles with PU get installed via the
 url handler.

 5) Have some kind of an extender that would generate a fragment bundle
 (with right persistence provider imports) and attach it to the bundle
 with PU. Or something similar that would require manifest modification
 or generation of additional bundle.

 Thoughts?

 Jarek

[jira] Created: (GERONIMO-5326) Geronimo javamail does not work on non-ASCII platforms

2010-05-19 Thread Robin Fernandes (JIRA)

Geronimo javamail does not work on non-ASCII platforms
--

 Key: GERONIMO-5326
 URL: https://issues.apache.org/jira/browse/GERONIMO-5326
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: mail
 Environment: z/OS
Reporter: Robin Fernandes


[RFC-1939|http://www.ietf.org/rfc/rfc1939.txt] states that in the POP3 
protocol, Keywords and arguments consist of printable ASCII characters.

Geronimo javamail creates a PrintWriter to send messages down the line, but 
does not specify a Charset. Therefore, Strings written to the PrintWriter will 
be converted to bytes using the platform default encoding. On a non-ASCII 
platform, such as z/OS (which is an EBCDIC platform), this means non-ASCII data 
will be sent down the line. Consequently, the POP3 protocol is violated and the 
mail server will not understand the messages.

In my context, this manifests as a javax.mail.AuthenticationFailedException, 
presumably because the server fails to understand the login commands.

The patch below at least gets past the auth step. However, I suspect there will 
be further charset problems relating to decoding MIME etc... Essentially, a 
potential problem exists wherever the library uses new String(bytes[]), 
String.getBytes(), InputStreamReaders, OuputStreamWriters or any other entity 
that performs byte[]-String conversions without explicitly specifying which 
Charset to use.

In some environments, a workaround may be to force the default encoding to 
ASCII by setting system property file.encoding to an ASCII codepage (e.g. 
-Dfile.encoding=ISO8859-1), but this is not satisfactory if other libraries in 
the same runtime expect the default encoding to be EBCDIC.

{code} 
Index: POP3Connection.java
===
--- POP3Connection.java (revision 946178)
+++ POP3Connection.java (working copy)
@@ -22,6 +22,7 @@
 import java.net.Socket;
 import java.net.SocketException;
 import java.net.UnknownHostException;
+import java.nio.charset.Charset;
 import java.security.MessageDigest;
 import java.security.NoSuchAlgorithmException;
 import java.util.ArrayList;
@@ -156,8 +157,9 @@
 
 // The POp3 protocol is inherently a string-based protocol, so we get 
 // string readers/writers for the connection streams 
-reader = new BufferedReader(new InputStreamReader(inputStream));
-writer = new PrintWriter(new BufferedOutputStream(outputStream));
+Charset iso88591 = Charset.forName(ISO8859-1);
+reader = new BufferedReader(new InputStreamReader(inputStream, 
iso88591));
+writer = new PrintWriter(new OutputStreamWriter(new 
BufferedOutputStream(outputStream), iso88591));
 }
 
 protected void getWelcome() throws IOException {
{code} 

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

[jira] Assigned: (GERONIMO-5326) Geronimo javamail does not work on non-ASCII platforms

2010-05-19 Thread Rick McGuire (JIRA)


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

Rick McGuire reassigned GERONIMO-5326:
--

Assignee: Rick McGuire

 Geronimo javamail does not work on non-ASCII platforms
 --

 Key: GERONIMO-5326
 URL: https://issues.apache.org/jira/browse/GERONIMO-5326
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: mail
 Environment: z/OS
Reporter: Robin Fernandes
Assignee: Rick McGuire

 [RFC-1939|http://www.ietf.org/rfc/rfc1939.txt] states that in the POP3 
 protocol, Keywords and arguments consist of printable ASCII characters.
 Geronimo javamail creates a PrintWriter to send messages down the line, but 
 does not specify a Charset. Therefore, Strings written to the PrintWriter 
 will be converted to bytes using the platform default encoding. On a 
 non-ASCII platform, such as z/OS (which is an EBCDIC platform), this means 
 non-ASCII data will be sent down the line. Consequently, the POP3 protocol is 
 violated and the mail server will not understand the messages.
 In my context, this manifests as a javax.mail.AuthenticationFailedException, 
 presumably because the server fails to understand the login commands.
 The patch below at least gets past the auth step. However, I suspect there 
 will be further charset problems relating to decoding MIME etc... 
 Essentially, a potential problem exists wherever the library uses new 
 String(bytes[]), String.getBytes(), InputStreamReaders, OuputStreamWriters or 
 any other entity that performs byte[]-String conversions without explicitly 
 specifying which Charset to use.
 In some environments, a workaround may be to force the default encoding to 
 ASCII by setting system property file.encoding to an ASCII codepage (e.g. 
 -Dfile.encoding=ISO8859-1), but this is not satisfactory if other libraries 
 in the same runtime expect the default encoding to be EBCDIC.
 {code} 
 Index: POP3Connection.java
 ===
 --- POP3Connection.java   (revision 946178)
 +++ POP3Connection.java   (working copy)
 @@ -22,6 +22,7 @@
  import java.net.Socket;
  import java.net.SocketException;
  import java.net.UnknownHostException;
 +import java.nio.charset.Charset;
  import java.security.MessageDigest;
  import java.security.NoSuchAlgorithmException;
  import java.util.ArrayList;
 @@ -156,8 +157,9 @@
  
  // The POp3 protocol is inherently a string-based protocol, so we 
 get 
  // string readers/writers for the connection streams 
 -reader = new BufferedReader(new InputStreamReader(inputStream));
 -writer = new PrintWriter(new BufferedOutputStream(outputStream));
 +Charset iso88591 = Charset.forName(ISO8859-1);
 +reader = new BufferedReader(new InputStreamReader(inputStream, 
 iso88591));
 +writer = new PrintWriter(new OutputStreamWriter(new 
 BufferedOutputStream(outputStream), iso88591));
  }
  
  protected void getWelcome() throws IOException {
 {code} 

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

Re: Recover the configurationBaseUrl attribute temporary ?

2010-05-19 Thread Jarek Gawor

Ivan,

Please keep in mind when working on the web application support
(servlet 3.0, etc.) it should support two types of applications:
regular Java EE applications and OSGi web applications.
The OSGi web applications support fragment bundles. That is, the
content of a OSGi web application is looked up in the bundle itself
and as well any attached fragments. That means, the entry.getBundle()
based lookup is not enough as it does not consider the fragment
bundles. That's also why I added BundleUtils.getEntry() and
BundleUtils.getEntryPaths() utility functions which work like
Bundle.getEntry() and Bundle.getEntryPaths() but also consider the
fragment bundles. Please make sure to use those functions.

The fragment bundles are another reason why we can't really use the
configurationBaseUrl since there is no single root url through which
we can access both the bundle contents and its attached fragments.

Jarek

On Wed, May 19, 2010 at 2:34 AM, Ivan xhh...@gmail.com wrote:
 Yes, embbed jar files should not work due to different url with the host
 bundle, I forgot it ...
 OK, I would try to replace them with getEntry methods. Thanks !

 2010/5/19 David Jencks david_jen...@yahoo.com

 On May 18, 2010, at 10:54 PM, Ivan wrote:

  Hi,
      In the past, we have a magic attribute configurationBaseUrl which
  will be injected while starting the gbeans. After moving to OSGI
  environment, it is removed as all the components are running in OSGI cache.
  While looking at some web service codes, it is still refered in many
  places. And in the new OSGi environment, it should be replaced with
  something like bundle.getEntry etc. But before doing those changes, I am
  thinking to recover the configurationBaseUrl attribute temporary, using
  --
  URL baseURL = configuration.getBundle().getEntry(/);
  gbeanData.setAttribute(configurationBaseUrl, baseURL);
  ---
  In my environment, it works.
  Any thought ?

 I don't think it will work for a module embedded in an ear.  The uses I
 changed were all for wars and needed it to point to the directory in the
 unpacked car file the war was at.

 What will bringing this attribute back allow you to do that you can't do
 locally and eliminate before committing?

 thanks
 david jencks

 
  --
  Ivan




 --
 Ivan

Fwd: [ANNOUNCE] Apache Derby 10.6.1.0 released

 Original Message 
Subject: [ANNOUNCE] Apache Derby 10.6.1.0 released
Date: 19 May 2010 15:53:28 -
From: rhille...@apache.org
To: annou...@apache.org

The Apache Derby project is pleased to announce release 10.6.1.0. In
addition to introducing many new features, this release fixes a security
flaw. Please see below for more details.

Apache Derby is a subproject of the Apache DB project. Derby is a pure
Java relational database engine which conforms to the ISO/ANSI SQL and
JDBC standards. Derby aims to be easy for developers and end-users to
work with.

Derby 10.6.1.0 can be obtained from the Derby download site:

   http://db.apache.org/derby/derby_downloads.html.

Derby 10.6.1.0 contains the following new features:

* Sequence Generators - Named generators for allocating successive,
evenly spaced numbers. See feature T176 of the SQL Standard.
* User-defined types - Named types bound to serializable Java objects.
* Restricted table functions - Limits on the columns and rows
returned by table functions.
* XPLAIN statistics collection - Query plan statistics stored in
tables for later analysis.
* GROUP BY ROLLUP - A subset of the SQL Standard ROLLUP
functionality on the GROUP BY clause. See feature T431 of the SQL Standard.
* CROSS JOIN - CROSS JOIN syntax. See feature F401-04 of the SQL
Standard.
* Named columns join - USING clauses in joins.
* SHOW FUNCTIONS - IJ command that lists stored functions.
* In-memory back end enhancements - Numerous improvements, including
the ability to delete in-memory databases.
* ORDER BY in subqueries - Syntax for explicitly ordering rows
returned by subqueries. See features F851, F852, and F855 of the SQL
Standard.
* OFFSET, FETCH FIRST/NEXT in subqueries - Generalized syntax for
retrieving row subsets. See features F856, F857, F858, F859, F861, F862,
F863, and F864 of the SQL Standard.
* NATURAL JOIN - Support for NATURAL JOIN. See feature T431 of the
SQL Standard.
* Qualified identifers in ij - Ability to reference cursors and
prepared statements in other connections.
* Configurable hash algorithm - Ability to customize the hash
algorithm used by BUILTIN authentication.
* Context-sniffing scripts - Ability of shipped scripts to locate
Derby jars when DERBY_HOME isn't set.
* Case-insensitive strings - Ability to ignore case in string
comparisons and sorts.

In addition, Derby 10.6.1.0 contains many bug and documentation fixes.

Please try out this new release.

-- IMPORTANT SECURITY NOTE -- IMPORTANT SECURITY NOTE -- IMPORTANT
SECURITY NOTE --

Derby 10.6.1.0 also fixes a security flaw tracked by the Apache Common
Vulnerabilities and Exposures id CVE-2009-4269. This flaw made it easy
to crack passwords managed by Derby's BUILTIN authentication logic.
Originally, the BUILTIN logic was intended only for testing purposes.
However, Derby's user documentation suggested that this scheme was
production-ready and it appears that many users rely on BUILTIN
authentication in production. Tracked by DERBY-4483, the flaw is
addressed as follows:

1) The bug itself is corrected for newly created 10.6 databases.

2) Password substitution is not allowed when logging into a database
where the bug is corrected and BUILTIN passwords are stored in the
database. See the release note for DERBY-4483.

3) Derby's default password-hashing scheme is changed from SHA-1 to
SHA-256, which is harder to crack.

4) The user guides are glossed with warnings against production use of
the BUILTIN authentication mechanism.

Users are urged to

i) Migrate production systems off the BUILTIN mechanism onto Derby's
LDAP and user-customized authentication schemes.

ii) Or hard-upgrade to 10.6.1.0 immediately and perform the following
additional steps:

a) Set derby.authentication.builtin.algorithm to a stronger
authentication scheme like SHA-256 or SHA-512.

b) Reset all passwords stored in the database.

c) Stop using strong password substitution. Instead, encrypt all network
traffic using SSL/TLS.

-- IMPORTANT SECURITY NOTE -- IMPORTANT SECURITY NOTE -- IMPORTANT
SECURITY NOTE --

[BUILD] branches/2.2: Failed for Revision: 946293

Geronimo Revision: 946293 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100519/build-1400.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100519/unit-test-reports
 
[INFO] [car:package]
[INFO] Packaging module configuration: 
/home/geronimo/geronimo/2.2/framework/configs/jee-specs/target/work/plan.xml
[INFO] Started deployer: 
org.apache.geronimo.framework/geronimo-gbean-deployer-bootstrap/2.2.1-SNAPSHOT/car
[INFO] [car:prepare-metadata]
[INFO] [car:archive-car]
[INFO] Building jar: 
/home/geronimo/geronimo/2.2/framework/configs/jee-specs/target/jee-specs-2.2.1-SNAPSHOT.car
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: jee-specs-2.2.1-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing 
/home/geronimo/geronimo/2.2/framework/configs/jee-specs/target/jee-specs-2.2.1-SNAPSHOT.car
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/framework/jee-specs/2.2.1-SNAPSHOT/jee-specs-2.2.1-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO] 
[INFO] Building Geronimo Framework, Modules :: Naming
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/xbean/xbean-naming/3.7/xbean-naming-3.7.pom
1K downloaded
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/xbean/xbean-naming/3.7/xbean-naming-3.7.jar
53K downloaded
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 27 source files to 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/classes
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Compiling 8 source files to 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/surefire-reports

---
 T E S T S
---
Running org.apache.geronimo.gjndi.binding.GBeanBindingTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.898 sec
Running org.apache.geronimo.gjndi.KernelContextGBeanTest
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.617 sec  
FAILURE!
Running org.apache.geronimo.gjndi.binding.FormatTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running org.apache.geronimo.gjndi.JavaCompGBeanTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.164 sec
Running org.apache.geronimo.gjndi.JavaCompContextTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.985 sec

Results :

Failed tests: 
  test(org.apache.geronimo.gjndi.KernelContextGBeanTest)

Tests run: 15, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/surefire-reports
 for the individual test results.
[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/surefire-reports
 for the individual test results.
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:580)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures

[jira] Resolved: (GERONIMO-5326) Geronimo javamail does not work on non-ASCII platforms

2010-05-19 Thread Rick McGuire (JIRA)


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

Rick McGuire resolved GERONIMO-5326.


Resolution: Fixed

Committed revision 946312. and 946314.

I believe I found all the places where this might be an issue.  There were 
quite a few potential exposures. 

 Geronimo javamail does not work on non-ASCII platforms
 --

 Key: GERONIMO-5326
 URL: https://issues.apache.org/jira/browse/GERONIMO-5326
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: mail
 Environment: z/OS
Reporter: Robin Fernandes
Assignee: Rick McGuire

 [RFC-1939|http://www.ietf.org/rfc/rfc1939.txt] states that in the POP3 
 protocol, Keywords and arguments consist of printable ASCII characters.
 Geronimo javamail creates a PrintWriter to send messages down the line, but 
 does not specify a Charset. Therefore, Strings written to the PrintWriter 
 will be converted to bytes using the platform default encoding. On a 
 non-ASCII platform, such as z/OS (which is an EBCDIC platform), this means 
 non-ASCII data will be sent down the line. Consequently, the POP3 protocol is 
 violated and the mail server will not understand the messages.
 In my context, this manifests as a javax.mail.AuthenticationFailedException, 
 presumably because the server fails to understand the login commands.
 The patch below at least gets past the auth step. However, I suspect there 
 will be further charset problems relating to decoding MIME etc... 
 Essentially, a potential problem exists wherever the library uses new 
 String(bytes[]), String.getBytes(), InputStreamReaders, OuputStreamWriters or 
 any other entity that performs byte[]-String conversions without explicitly 
 specifying which Charset to use.
 In some environments, a workaround may be to force the default encoding to 
 ASCII by setting system property file.encoding to an ASCII codepage (e.g. 
 -Dfile.encoding=ISO8859-1), but this is not satisfactory if other libraries 
 in the same runtime expect the default encoding to be EBCDIC.
 {code} 
 Index: POP3Connection.java
 ===
 --- POP3Connection.java   (revision 946178)
 +++ POP3Connection.java   (working copy)
 @@ -22,6 +22,7 @@
  import java.net.Socket;
  import java.net.SocketException;
  import java.net.UnknownHostException;
 +import java.nio.charset.Charset;
  import java.security.MessageDigest;
  import java.security.NoSuchAlgorithmException;
  import java.util.ArrayList;
 @@ -156,8 +157,9 @@
  
  // The POp3 protocol is inherently a string-based protocol, so we 
 get 
  // string readers/writers for the connection streams 
 -reader = new BufferedReader(new InputStreamReader(inputStream));
 -writer = new PrintWriter(new BufferedOutputStream(outputStream));
 +Charset iso88591 = Charset.forName(ISO8859-1);
 +reader = new BufferedReader(new InputStreamReader(inputStream, 
 iso88591));
 +writer = new PrintWriter(new OutputStreamWriter(new 
 BufferedOutputStream(outputStream), iso88591));
  }
  
  protected void getWelcome() throws IOException {
 {code} 

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

[jira] Created: (GERONIMO-5327) SSL Certificate verification

2010-05-19 Thread Eswaran Thandi (JIRA)

SSL Certificate verification 
-

 Key: GERONIMO-5327
 URL: https://issues.apache.org/jira/browse/GERONIMO-5327
 Project: Geronimo
  Issue Type: Task
  Security Level: public (Regular issues)
  Components: security
 Environment: Linux
Reporter: Eswaran Thandi


i have a requirement to verify the SSL Certificate ( i.e. read and verify some 
attributes in the certificate). is it the outofbox feature in Geronimo or Do i 
need to write a component for this? Please clarify

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

[jira] Closed: (GERONIMO-5327) SSL Certificate verification


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

David Jencks closed GERONIMO-5327.
--

Resolution: Not A Problem

Jira is not a support forum.  Please ask on the user mailing list and explain 
what you want to do.  In particular, which ssl certificate, and under what 
circumstances.

 SSL Certificate verification 
 -

 Key: GERONIMO-5327
 URL: https://issues.apache.org/jira/browse/GERONIMO-5327
 Project: Geronimo
  Issue Type: Task
  Security Level: public(Regular issues) 
  Components: security
 Environment: Linux
Reporter: Eswaran Thandi

 i have a requirement to verify the SSL Certificate ( i.e. read and verify 
 some attributes in the certificate). is it the outofbox feature in Geronimo 
 or Do i need to write a component for this? Please clarify

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

Geronimo Revision: 946342 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100519/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100519/unit-test-reports
 
2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-ajp -Dversion=8.0.0.M1-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=org.eclipse.jetty -DartifactId=jetty-ajp 
-Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
-DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT

3) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-jaspi -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-jaspi -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT

4) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-webapp -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-webapp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT

5) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-security -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-security -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT

6) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-servlet -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-servlet -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT

--
6 required artifacts are missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots),
  local (file:///home/geronimo/.m2/jtidy.repository),
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  java.net.2 (http://download.java.net/maven/1/),
  jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/),
  openqa-releases (http://nexus.openqa.org/content/repositories/releases),
  axis2-axiom-api 
(https://repository.apache.org/content/repositories/orgapachegeronimo-002/),
  smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360

Re: Runtime entity enhancement for OSGi applications

Good summary Lin.

In the OpenJPA community, we've been telling users for awhile now not to
use the runtime enhancement, as it has known deficiencies, and should
only be used for quick prototyping and never in production.

If we need to continue supporting this in Geronimo (for the developer
scenarios), then I'd go with #3 for now.


-Donald


On 5/19/10 11:19 AM, Lin Sun wrote:
 Seems No. 3 is the right approach, given that there is no overhead on
 the user side and it gives the ability to add the imports at the last
 minute, before the PU is resolved.
 
 No. 2 gives some extra work on the user side which can make the PU not 
 portable.
 
 Np. 4 has to be done when PU is installed, and it is possible the
 provider is not even there yet.
 
 No. 5 can be confusing to the user as a fragment is attached to their PU.
 
 Lin
 
 On Tue, May 18, 2010 at 10:41 PM, Jarek Gawor jga...@gmail.com wrote:
 Hi all,

 I was looking into getting the runtime JPA entity enhancement for OSGi
 applications working in Geronimo. With some modifications to the Aries
 JPA code and some to Geronimo I was able to get runtime enhancement
 working (using the java agent approach) but with one major issue: The
 bundle that contains the persistence unit must be able to load some
 persistence provider specific (in our case openjpa) classes. That's
 because during the bytecode weaving, openjpa adds some openjpa
 specific interfaces to the entity classes. So how should we deal with
 this issue in Geronimo?

 1) We could do nothing and just say we don't support runtime enhancement.

 2) We could support runtime enhancement and require that bundles with
 PU have DynamicImport-Package: * header.

 3) Use framework classloader hooks to dynamically add imports for
 the persistence provider specific packages to the bundles with PU .
 That of course, would rely on framework specific extensions. I know
 Equinox has such hooks and I think recently something similar was
 added to Felix.

 4) Provide some url handler, e.g. jpa which would enhance the entity
 classes and add right imports during the install. Something similar to
 the webbundle url handler for web application archives. Of course,
 we would have to make sure the bundles with PU get installed via the
 url handler.

 5) Have some kind of an extender that would generate a fragment bundle
 (with right persistence provider imports) and attach it to the bundle
 with PU. Or something similar that would require manifest modification
 or generation of additional bundle.

 Thoughts?

 Jarek

[jira] Commented: (GERONIMO-4918) EJB 3.1 Singleton Support


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

David Jencks commented on GERONIMO-4918:


I think I have everything ported to trunk with rev 946366

 EJB 3.1 Singleton Support
 -

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

 Attachments: GERONIMO-4918.patch, 
 geronimo-singleton-support-geronimo.patch, LoadOnStartupGBean.java, 
 singleton-deploy-type.patch, SingletonDeploymentGBean.java


 The singleton support hasn't been completely implemented, so it's impossible 
 to deploy an singleton session bean (EJB).
 I added the support, recompiled + tested and it's working.
 The patch requires creating a new file, so both need to be applied.
 The patch was made from the root of the svn checkout of branches/2.2. 
 The new files path from the same root is: 
 plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/SingletonDeploymentGBean.java

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

Re: [VOTE] special Geronimo OpenEJB 3.1.3.0 release (second attempt)

Do we need to publish everything?  I was able to build the source, but
there were some rat:check failures in some modules (like container)...


-Donald


On 5/17/10 9:30 AM, Rick McGuire wrote:
 Please vote for the geronimo openejb 3.1.3.0 release
 
 This is a version of openejb based on revision r942249.  This is a
 special release to be used on the Geronimo 3.0-M1 release and is being
 released under the org.apache.geronimo.ext.openejb groupid.
 
 Differences from the first attempt:
 
 Copyright headers added to
 
 container/openejb-osgi/src/main/resources/default.openejb.conf
 container/openejb-activemq4/src/main/resources/login.config
 container/openejb-core/src/main/resources/login.config
 container/openejb-osgi/src/main/resources/login.config
 container/openejb-core/src/main/resources/schema/ejb-jar_1_1.xsd
 
 
 LICENSE file updated to include the W3C license for the following files:
 
 container/openejb-jee/src/main/resources/META-INF/schema/xml.xsd
 server/openejb-axis/src/main/resources/META-INF/schema/soap_encoding_1_1.xsd
 
 
 
 This is the working version of openejb that works with Geronimo 3.0. 
 This component is dependent upon the XBean release that is also
 currently up for a vote.  You may need to build XBean yourself to build
 openejb from the tag file at:
 
 https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.7
 
 Staging repo is here:
 
 https://repository.apache.org/content/repositories/orgapachegeronimo-037/
 
 tag is here:
 
 https://svn.apache.org/repos/asf/geronimo/external/tags/openejb-3.1.3.0
 
 Vote open 72 hours.  Note also that this is contingent upon the XBean
 vote also passing.
 
 [ ] +1 release this
 [ ] 0 don't care
 [ ] -1 don't release this (please explain)
 
 Rick

Re: Runtime entity enhancement for OSGi applications

2010-05-19 Thread David Jencks


On May 19, 2010, at 1:16 PM, Donald Woods wrote:

 Good summary Lin.
 
 In the OpenJPA community, we've been telling users for awhile now not to
 use the runtime enhancement, as it has known deficiencies, and should
 only be used for quick prototyping and never in production.

What are these deficiencies?  I thought you got the same bytecode whether you 
ran the enhancer using maven or as the classes are loaded using a class 
transformer.  I know the subclassing approach doesn't work well but that is not 
being discussed here AFAIK.

Is this stuff documented clearly somewhere in the openjpa docs?  I've never 
found a comprehensible explanation when I've looked in the past.

thanks
david jencks

 
 If we need to continue supporting this in Geronimo (for the developer
 scenarios), then I'd go with #3 for now.
 
 
 -Donald
 
 
 On 5/19/10 11:19 AM, Lin Sun wrote:
 Seems No. 3 is the right approach, given that there is no overhead on
 the user side and it gives the ability to add the imports at the last
 minute, before the PU is resolved.
 
 No. 2 gives some extra work on the user side which can make the PU not 
 portable.
 
 Np. 4 has to be done when PU is installed, and it is possible the
 provider is not even there yet.
 
 No. 5 can be confusing to the user as a fragment is attached to their PU.
 
 Lin
 
 On Tue, May 18, 2010 at 10:41 PM, Jarek Gawor jga...@gmail.com wrote:
 Hi all,
 
 I was looking into getting the runtime JPA entity enhancement for OSGi
 applications working in Geronimo. With some modifications to the Aries
 JPA code and some to Geronimo I was able to get runtime enhancement
 working (using the java agent approach) but with one major issue: The
 bundle that contains the persistence unit must be able to load some
 persistence provider specific (in our case openjpa) classes. That's
 because during the bytecode weaving, openjpa adds some openjpa
 specific interfaces to the entity classes. So how should we deal with
 this issue in Geronimo?
 
 1) We could do nothing and just say we don't support runtime enhancement.
 
 2) We could support runtime enhancement and require that bundles with
 PU have DynamicImport-Package: * header.
 
 3) Use framework classloader hooks to dynamically add imports for
 the persistence provider specific packages to the bundles with PU .
 That of course, would rely on framework specific extensions. I know
 Equinox has such hooks and I think recently something similar was
 added to Felix.
 
 4) Provide some url handler, e.g. jpa which would enhance the entity
 classes and add right imports during the install. Something similar to
 the webbundle url handler for web application archives. Of course,
 we would have to make sure the bundles with PU get installed via the
 url handler.
 
 5) Have some kind of an extender that would generate a fragment bundle
 (with right persistence provider imports) and attach it to the bundle
 with PU. Or something similar that would require manifest modification
 or generation of additional bundle.
 
 Thoughts?
 
 Jarek

Re: Runtime entity enhancement for OSGi applications


On May 19, 2010, at 4:16 PM, Donald Woods wrote:

 Good summary Lin.
 
 In the OpenJPA community, we've been telling users for awhile now not to
 use the runtime enhancement, as it has known deficiencies, and should
 only be used for quick prototyping and never in production.
 
 If we need to continue supporting this in Geronimo (for the developer
 scenarios), then I'd go with #3 for now.

Hmm. I'm confused, now. You don't mean the javaagent runtime ehancement is 
deficient, do you? Perhaps we have a problem with terminology?

--kevan

Re: Runtime entity enhancement for OSGi applications


On May 19, 2010, at 4:28 PM, David Jencks wrote:

 
 On May 19, 2010, at 1:16 PM, Donald Woods wrote:
 
 Good summary Lin.
 
 In the OpenJPA community, we've been telling users for awhile now not to
 use the runtime enhancement, as it has known deficiencies, and should
 only be used for quick prototyping and never in production.
 
 What are these deficiencies?  I thought you got the same bytecode whether you 
 ran the enhancer using maven or as the classes are loaded using a class 
 transformer.  I know the subclassing approach doesn't work well but that is 
 not being discussed here AFAIK.

Right. I hope Donald is referring to the subclassing approach. Which I 
agree/understand is deficient (we've seen instances of this).

 
 Is this stuff documented clearly somewhere in the openjpa docs?  I've never 
 found a comprehensible explanation when I've looked in the past.

Try this -- 
http://openjpa.apache.org/builds/2.0.0/apache-openjpa-2.0.0/docs/manual/main.html

I don't follow section 2.2. 

--kevan

Re: [VOTE] special Geronimo OpenEJB 3.1.3.0 release (second attempt)

Looks like there were really only 4 services files that had rat:check
failures, even though it gave a count of 867.

So, here's my +1.


-Donald


On 5/19/10 4:28 PM, Donald Woods wrote:
 Do we need to publish everything?  I was able to build the source, but
 there were some rat:check failures in some modules (like container)...
 
 
 -Donald
 
 
 On 5/17/10 9:30 AM, Rick McGuire wrote:
 Please vote for the geronimo openejb 3.1.3.0 release

 This is a version of openejb based on revision r942249.  This is a
 special release to be used on the Geronimo 3.0-M1 release and is being
 released under the org.apache.geronimo.ext.openejb groupid.

 Differences from the first attempt:

 Copyright headers added to

 container/openejb-osgi/src/main/resources/default.openejb.conf
 container/openejb-activemq4/src/main/resources/login.config
 container/openejb-core/src/main/resources/login.config
 container/openejb-osgi/src/main/resources/login.config
 container/openejb-core/src/main/resources/schema/ejb-jar_1_1.xsd


 LICENSE file updated to include the W3C license for the following files:

 container/openejb-jee/src/main/resources/META-INF/schema/xml.xsd
 server/openejb-axis/src/main/resources/META-INF/schema/soap_encoding_1_1.xsd



 This is the working version of openejb that works with Geronimo 3.0. 
 This component is dependent upon the XBean release that is also
 currently up for a vote.  You may need to build XBean yourself to build
 openejb from the tag file at:

 https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.7

 Staging repo is here:

 https://repository.apache.org/content/repositories/orgapachegeronimo-037/

 tag is here:

 https://svn.apache.org/repos/asf/geronimo/external/tags/openejb-3.1.3.0

 Vote open 72 hours.  Note also that this is contingent upon the XBean
 vote also passing.

 [ ] +1 release this
 [ ] 0 don't care
 [ ] -1 don't release this (please explain)

 Rick

Re: Runtime entity enhancement for OSGi applications



On 5/19/10 4:28 PM, David Jencks wrote:
 
 On May 19, 2010, at 1:16 PM, Donald Woods wrote:
 
 Good summary Lin.

 In the OpenJPA community, we've been telling users for awhile now not to
 use the runtime enhancement, as it has known deficiencies, and should
 only be used for quick prototyping and never in production.
 
 What are these deficiencies?  I thought you got the same bytecode whether you 
 ran the enhancer using maven or as the classes are loaded using a class 
 transformer.  I know the subclassing approach doesn't work well but that is 
 not being discussed here AFAIK.
 

Javaagent - yes, it should be the same.
Subclassing - no, that is what we tell people not to use.

BTW - Geronimo is the only App Server that we know of that uses the
-javaagent method for enhancing


-Donald


 Is this stuff documented clearly somewhere in the openjpa docs?  I've never 
 found a comprehensible explanation when I've looked in the past.
 
 thanks
 david jencks
 

 If we need to continue supporting this in Geronimo (for the developer
 scenarios), then I'd go with #3 for now.


 -Donald


 On 5/19/10 11:19 AM, Lin Sun wrote:
 Seems No. 3 is the right approach, given that there is no overhead on
 the user side and it gives the ability to add the imports at the last
 minute, before the PU is resolved.

 No. 2 gives some extra work on the user side which can make the PU not 
 portable.

 Np. 4 has to be done when PU is installed, and it is possible the
 provider is not even there yet.

 No. 5 can be confusing to the user as a fragment is attached to their PU.

 Lin

 On Tue, May 18, 2010 at 10:41 PM, Jarek Gawor jga...@gmail.com wrote:
 Hi all,

 I was looking into getting the runtime JPA entity enhancement for OSGi
 applications working in Geronimo. With some modifications to the Aries
 JPA code and some to Geronimo I was able to get runtime enhancement
 working (using the java agent approach) but with one major issue: The
 bundle that contains the persistence unit must be able to load some
 persistence provider specific (in our case openjpa) classes. That's
 because during the bytecode weaving, openjpa adds some openjpa
 specific interfaces to the entity classes. So how should we deal with
 this issue in Geronimo?

 1) We could do nothing and just say we don't support runtime enhancement.

 2) We could support runtime enhancement and require that bundles with
 PU have DynamicImport-Package: * header.

 3) Use framework classloader hooks to dynamically add imports for
 the persistence provider specific packages to the bundles with PU .
 That of course, would rely on framework specific extensions. I know
 Equinox has such hooks and I think recently something similar was
 added to Felix.

 4) Provide some url handler, e.g. jpa which would enhance the entity
 classes and add right imports during the install. Something similar to
 the webbundle url handler for web application archives. Of course,
 we would have to make sure the bundles with PU get installed via the
 url handler.

 5) Have some kind of an extender that would generate a fragment bundle
 (with right persistence provider imports) and attach it to the bundle
 with PU. Or something similar that would require manifest modification
 or generation of additional bundle.

 Thoughts?

 Jarek

Re: Runtime entity enhancement for OSGi applications

2010-05-19 Thread David Jencks


On May 19, 2010, at 1:41 PM, Kevan Miller wrote:

 
 On May 19, 2010, at 4:28 PM, David Jencks wrote:
 
 
 On May 19, 2010, at 1:16 PM, Donald Woods wrote:
 
 Good summary Lin.
 
 In the OpenJPA community, we've been telling users for awhile now not to
 use the runtime enhancement, as it has known deficiencies, and should
 only be used for quick prototyping and never in production.
 
 What are these deficiencies?  I thought you got the same bytecode whether 
 you ran the enhancer using maven or as the classes are loaded using a class 
 transformer.  I know the subclassing approach doesn't work well but that is 
 not being discussed here AFAIK.
 
 Right. I hope Donald is referring to the subclassing approach. Which I 
 agree/understand is deficient (we've seen instances of this).
 
 
 Is this stuff documented clearly somewhere in the openjpa docs?  I've never 
 found a comprehensible explanation when I've looked in the past.
 
 Try this -- 
 http://openjpa.apache.org/builds/2.0.0/apache-openjpa-2.0.0/docs/manual/main.html
 
 I don't follow section 2.2. 

I think you mean 3.5.2.2, but this is the explanation I've found that to me is 
difficult to understand.  I guess the ee5 runtime hooks they refer to are the 
method on PersistenceUnitInfo (provided by the container) where the provider 
can try to install a transformer.  

david jencks

 
 --kevan

Re: Runtime entity enhancement for OSGi applications

2010-05-19 Thread Guillaume Nodet

FWIW, I would think #3 is a good option, but I don't think Felix has
anything to support that (but I may be wrong).

On Wed, May 19, 2010 at 04:41, Jarek Gawor jga...@gmail.com wrote:
 Hi all,

 I was looking into getting the runtime JPA entity enhancement for OSGi
 applications working in Geronimo. With some modifications to the Aries
 JPA code and some to Geronimo I was able to get runtime enhancement
 working (using the java agent approach) but with one major issue: The
 bundle that contains the persistence unit must be able to load some
 persistence provider specific (in our case openjpa) classes. That's
 because during the bytecode weaving, openjpa adds some openjpa
 specific interfaces to the entity classes. So how should we deal with
 this issue in Geronimo?

 1) We could do nothing and just say we don't support runtime enhancement.

 2) We could support runtime enhancement and require that bundles with
 PU have DynamicImport-Package: * header.

 3) Use framework classloader hooks to dynamically add imports for
 the persistence provider specific packages to the bundles with PU .
 That of course, would rely on framework specific extensions. I know
 Equinox has such hooks and I think recently something similar was
 added to Felix.

 4) Provide some url handler, e.g. jpa which would enhance the entity
 classes and add right imports during the install. Something similar to
 the webbundle url handler for web application archives. Of course,
 we would have to make sure the bundles with PU get installed via the
 url handler.

 5) Have some kind of an extender that would generate a fragment bundle
 (with right persistence provider imports) and attach it to the bundle
 with PU. Or something similar that would require manifest modification
 or generation of additional bundle.

 Thoughts?

 Jarek




-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com

Re: Runtime entity enhancement for OSGi applications

On May 19, 2010, at 5:12 PM, David Jencks wrote:

On May 19, 2010, at 1:41 PM, Kevan Miller wrote:

On May 19, 2010, at 4:28 PM, David Jencks wrote:

On May 19, 2010, at 1:16 PM, Donald Woods wrote:

Good summary Lin.

In the OpenJPA community, we've been telling users for awhile now not to
use the runtime enhancement, as it has known deficiencies, and should
only be used for quick prototyping and never in production.

What are these deficiencies? I thought you got the same bytecode whether
you ran the enhancer using maven or as the classes are loaded using a class
transformer. I know the subclassing approach doesn't work well but that is
not being discussed here AFAIK.

Right. I hope Donald is referring to the subclassing approach. Which I
agree/understand is deficient (we've seen instances of this).

Is this stuff documented clearly somewhere in the openjpa docs? I've never
found a comprehensible explanation when I've looked in the past.

Try this --
http://openjpa.apache.org/builds/2.0.0/apache-openjpa-2.0.0/docs/manual/main.html

I don't follow section 2.2.

I think you mean 3.5.2.2, but this is the explanation I've found that to me
is difficult to understand. I guess the ee5 runtime hooks they refer to are
the method on PersistenceUnitInfo (provided by the container) where the
provider can try to install a transformer.

Oops. I pasted the wrong url. Was supposed to be
http://openjpa.apache.org/builds/2.0.0/apache-openjpa-2.0.0/docs/manual/ref_guide_pc_enhance.html

Yes. That's the section I was referring to.

--kevan

Re: Runtime entity enhancement for OSGi applications

2010-05-19 Thread Jarek Gawor

Btw, I was referring to
https://issues.apache.org/jira/browse/FELIX-2197. I thought parts of
the patch were applied to Felix but I guess I was wrong.

Jarek

On Wed, May 19, 2010 at 5:15 PM, Guillaume Nodet gno...@gmail.com wrote:
 FWIW, I would think #3 is a good option, but I don't think Felix has
 anything to support that (but I may be wrong).

 On Wed, May 19, 2010 at 04:41, Jarek Gawor jga...@gmail.com wrote:
 Hi all,

 I was looking into getting the runtime JPA entity enhancement for OSGi
 applications working in Geronimo. With some modifications to the Aries
 JPA code and some to Geronimo I was able to get runtime enhancement
 working (using the java agent approach) but with one major issue: The
 bundle that contains the persistence unit must be able to load some
 persistence provider specific (in our case openjpa) classes. That's
 because during the bytecode weaving, openjpa adds some openjpa
 specific interfaces to the entity classes. So how should we deal with
 this issue in Geronimo?

 1) We could do nothing and just say we don't support runtime enhancement.

 2) We could support runtime enhancement and require that bundles with
 PU have DynamicImport-Package: * header.

 3) Use framework classloader hooks to dynamically add imports for
 the persistence provider specific packages to the bundles with PU .
 That of course, would rely on framework specific extensions. I know
 Equinox has such hooks and I think recently something similar was
 added to Felix.

 4) Provide some url handler, e.g. jpa which would enhance the entity
 classes and add right imports during the install. Something similar to
 the webbundle url handler for web application archives. Of course,
 we would have to make sure the bundles with PU get installed via the
 url handler.

 5) Have some kind of an extender that would generate a fragment bundle
 (with right persistence provider imports) and attach it to the bundle
 with PU. Or something similar that would require manifest modification
 or generation of additional bundle.

 Thoughts?

 Jarek




 --
 Cheers,
 Guillaume Nodet
 
 Blog: http://gnodet.blogspot.com/
 
 Open Source SOA
 http://fusesource.com

Re: Runtime entity enhancement for OSGi applications

2010-05-19 Thread Guillaume Nodet

It does not look like the patch has been applied.  You'd have to
comment on it and push for a solution if you want it to be included
somehow.

On Wed, May 19, 2010 at 23:34, Jarek Gawor jga...@gmail.com wrote:
 Btw, I was referring to
 https://issues.apache.org/jira/browse/FELIX-2197. I thought parts of
 the patch were applied to Felix but I guess I was wrong.

 Jarek

 On Wed, May 19, 2010 at 5:15 PM, Guillaume Nodet gno...@gmail.com wrote:
 FWIW, I would think #3 is a good option, but I don't think Felix has
 anything to support that (but I may be wrong).

 On Wed, May 19, 2010 at 04:41, Jarek Gawor jga...@gmail.com wrote:
 Hi all,

 I was looking into getting the runtime JPA entity enhancement for OSGi
 applications working in Geronimo. With some modifications to the Aries
 JPA code and some to Geronimo I was able to get runtime enhancement
 working (using the java agent approach) but with one major issue: The
 bundle that contains the persistence unit must be able to load some
 persistence provider specific (in our case openjpa) classes. That's
 because during the bytecode weaving, openjpa adds some openjpa
 specific interfaces to the entity classes. So how should we deal with
 this issue in Geronimo?

 1) We could do nothing and just say we don't support runtime enhancement.

 2) We could support runtime enhancement and require that bundles with
 PU have DynamicImport-Package: * header.

 3) Use framework classloader hooks to dynamically add imports for
 the persistence provider specific packages to the bundles with PU .
 That of course, would rely on framework specific extensions. I know
 Equinox has such hooks and I think recently something similar was
 added to Felix.

 4) Provide some url handler, e.g. jpa which would enhance the entity
 classes and add right imports during the install. Something similar to
 the webbundle url handler for web application archives. Of course,
 we would have to make sure the bundles with PU get installed via the
 url handler.

 5) Have some kind of an extender that would generate a fragment bundle
 (with right persistence provider imports) and attach it to the bundle
 with PU. Or something similar that would require manifest modification
 or generation of additional bundle.

 Thoughts?

 Jarek




 --
 Cheers,
 Guillaume Nodet
 
 Blog: http://gnodet.blogspot.com/
 
 Open Source SOA
 http://fusesource.com





-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com

[BUILD] branches/2.2: Failed for Revision: 946479

Geronimo Revision: 946479 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100519/build-2000.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100519/unit-test-reports
 
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@36fe36fe
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2dc02dc0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2dc02dc0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@36fe36fe
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2dc02dc0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2dc02dc0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@36fe36fe
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2dc02dc0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2dc02dc0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@36fe36fe
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2dc02dc0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2dc02dc0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@36fe36fe
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2dc02dc0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2dc02dc0
Downloading: 
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/xbean/xbean-naming/3.7/xbean-naming-3.7.jar
53K downloaded
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 27 source files to 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/classes
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Compiling 8 source files to 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/test-classes
[INFO] [surefire:test]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@36fe36fe
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2dc02dc0
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@2dc02dc0
[INFO] Surefire report directory: 
/home/geronimo/geronimo/2.2/framework/modules/geronimo-naming/target/surefire-reports

---
 T E S T S
---
Running org.apache.geronimo.gjndi.JavaCompContextTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.604 sec
Running org.apache.geronimo.gjndi.binding.FormatTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
Running org.apache.geronimo.gjndi.KernelContextGBeanTest
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.921 sec

Re: [VOTE] special Geronimo OpenEJB 3.1.3.0 release (second attempt)

2010-05-19 Thread David Blevins

+1

On May 17, 2010, at 6:30 AM, Rick McGuire wrote:

 Please vote for the geronimo openejb 3.1.3.0 release
 
 This is a version of openejb based on revision r942249.  This is a special 
 release to be used on the Geronimo 3.0-M1 release and is being released under 
 the org.apache.geronimo.ext.openejb groupid.
 
 Differences from the first attempt:
 
 Copyright headers added to
 
 container/openejb-osgi/src/main/resources/default.openejb.conf
 container/openejb-activemq4/src/main/resources/login.config
 container/openejb-core/src/main/resources/login.config
 container/openejb-osgi/src/main/resources/login.config
 container/openejb-core/src/main/resources/schema/ejb-jar_1_1.xsd
 
 
 LICENSE file updated to include the W3C license for the following files:
 
 container/openejb-jee/src/main/resources/META-INF/schema/xml.xsd
 server/openejb-axis/src/main/resources/META-INF/schema/soap_encoding_1_1.xsd
 
 
 This is the working version of openejb that works with Geronimo 3.0.  This 
 component is dependent upon the XBean release that is also currently up for a 
 vote.  You may need to build XBean yourself to build openejb from the tag 
 file at:
 
 https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.7
 
 Staging repo is here:
 
 https://repository.apache.org/content/repositories/orgapachegeronimo-037/
 
 tag is here:
 
 https://svn.apache.org/repos/asf/geronimo/external/tags/openejb-3.1.3.0
 
 Vote open 72 hours.  Note also that this is contingent upon the XBean vote 
 also passing.
 
 [ ] +1 release this
 [ ] 0 don't care
 [ ] -1 don't release this (please explain)
 
 Rick

[CANEL] [VOTE] Release Geronimo axis2 and axiom-api bundles (Second Try)

2010-05-19 Thread Ivan

Cancle this vote ...

2010/5/19 Kevan Miller kevan.mil...@gmail.com

 Have we had a conversation with the axis community regarding the
 split-package issue?

 Minor point: I note the license/notice files in the jar have different line
 endings (mix of unix and windows line endings). Would prefer that we avoid
 this, but end of the day it's a minor issue...

 It looks like there are some Axis2 fixes that we should be picking up from
 the Axis community. I think they should be included in our bundle release.
 Here's my -1.

 --kevan

 On May 17, 2010, at 11:51 PM, Ivan wrote:

 Please vote for the geronimo axis2 and axiom-api bundle release, add Notice
 and License files for axis2 and axiom-api

 axis2-1.5 : For there is split-package issue in the axis2 bundles which
 Geronimo requires.
 axiom-api 1.2.8 : The official bundle does not import javax.xml.stream.util
 package, althought Geronimo trunk works under JRE 1.6, while the package is
 not exported by the framework bundle, as we use our own stax bundle.

 Staging repo is here:

 https://repository.apache.org/content/repositories/orgapachegeronimo-002/

 tag is here:

 https://svn.apache.org/repos/asf/geronimo/bundles/tags/axiom-api-1.2.8_1/
 https://svn.apache.org/repos/asf/geronimo/bundles/tags/axis2-1.5_1/

 Vote open 72 hours

 [ ] +1 release this
 [ ] 0 don't care
 [ ] -1 don't release this (please explain)


 --
 Ivan





-- 
Ivan

Re: [VOTE] Release Geronimo axis2 and axiom-api bundles (Second Try)

2010-05-19 Thread Ivan

Yes, there is already a JIRA opened for Axis2 in the past by someone, but
...

2010/5/19 Kevan Miller kevan.mil...@gmail.com

 Have we had a conversation with the axis community regarding the
 split-package issue?

 Minor point: I note the license/notice files in the jar have different line
 endings (mix of unix and windows line endings). Would prefer that we avoid
 this, but end of the day it's a minor issue...

 It looks like there are some Axis2 fixes that we should be picking up from
 the Axis community. I think they should be included in our bundle release.
 Here's my -1.

 --kevan

 On May 17, 2010, at 11:51 PM, Ivan wrote:

 Please vote for the geronimo axis2 and axiom-api bundle release, add Notice
 and License files for axis2 and axiom-api

 axis2-1.5 : For there is split-package issue in the axis2 bundles which
 Geronimo requires.
 axiom-api 1.2.8 : The official bundle does not import javax.xml.stream.util
 package, althought Geronimo trunk works under JRE 1.6, while the package is
 not exported by the framework bundle, as we use our own stax bundle.

 Staging repo is here:

 https://repository.apache.org/content/repositories/orgapachegeronimo-002/

 tag is here:

 https://svn.apache.org/repos/asf/geronimo/bundles/tags/axiom-api-1.2.8_1/
 https://svn.apache.org/repos/asf/geronimo/bundles/tags/axis2-1.5_1/

 Vote open 72 hours

 [ ] +1 release this
 [ ] 0 don't care
 [ ] -1 don't release this (please explain)


 --
 Ivan





-- 
Ivan

[BUILD] trunk: Failed for Revision: 946503

Geronimo Revision: 946503 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100519/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100519/unit-test-reports
 
2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-ajp -Dversion=8.0.0.M1-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=org.eclipse.jetty -DartifactId=jetty-ajp 
-Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
-DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT

3) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-jaspi -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-jaspi -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT

4) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-webapp -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-webapp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT

5) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-security -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-security -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT

6) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.eclipse.jetty 
-DartifactId=jetty-servlet -Dversion=8.0.0.M1-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=org.eclipse.jetty 
-DartifactId=jetty-servlet -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT
2) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT

--
6 required artifacts are missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT

from the specified remote repositories:
  apache.snapshots (http://repository.apache.org/snapshots),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots),
  local (file:///home/geronimo/.m2/jtidy.repository),
  ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/),
  java.net.2 (http://download.java.net/maven/1/),
  jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/),
  openqa-releases (http://nexus.openqa.org/content/repositories/releases),
  axis2-axiom-api 
(https://repository.apache.org/content/repositories/orgapachegeronimo-002/),
  smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/)


at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360

[jira] Commented: (GERONIMO-5323) Chinese and Japanese Translation for JIRA 5055

2010-05-19 Thread Kan Ogawa (JIRA)


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

Kan Ogawa commented on GERONIMO-5323:
-

LiWenQin,

I had a talk about your reported issue with some Japanese contributors.
Their answer is that GERONIMO-5055 doesn't need to be translated right now.

Now I'm considering that I'll do Japanese language translation work for 3.0 
version in a mass including other translations and make the backports for both 
2.1 and 2.2 versions.

Thanks,
Kan Ogawa

 Chinese and Japanese Translation for JIRA 5055
 --

 Key: GERONIMO-5323
 URL: https://issues.apache.org/jira/browse/GERONIMO-5323
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2.1
 Environment: Windows XP
Reporter: LiWenQin
Priority: Minor
 Fix For: 2.2.1

 Attachments: screenshot-1.jpg, screenshot-2.jpg


 The console will display English (it should display Chinese/English)  in a 
 few lines with Using Informix tranql XA  in g221 , if the browse language is 
 set to Chinese/Japanese. 
 Who can help translate and modify the files below?
  
 plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_zh.properties
  
  
 plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_ja.properties
 Thanks!
 PS: Refer to https://issues.apache.org/jira/browse/GERONIMO-5055,
 plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_en.properties
  has been modified. You can modify systemdatabase_zh.properties  
 systemdatabase_ja.properties accordingly.

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

[jira] Commented: (GERONIMO-5323) Chinese and Japanese Translation for JIRA 5055

2010-05-19 Thread LiWenQin (JIRA)


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

LiWenQin commented on GERONIMO-5323:


Kan Ogawa,

I see.
Thanks.


 Chinese and Japanese Translation for JIRA 5055
 --

 Key: GERONIMO-5323
 URL: https://issues.apache.org/jira/browse/GERONIMO-5323
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2.1
 Environment: Windows XP
Reporter: LiWenQin
Priority: Minor
 Fix For: 2.2.1

 Attachments: screenshot-1.jpg, screenshot-2.jpg


 The console will display English (it should display Chinese/English)  in a 
 few lines with Using Informix tranql XA  in g221 , if the browse language is 
 set to Chinese/Japanese. 
 Who can help translate and modify the files below?
  
 plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_zh.properties
  
  
 plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_ja.properties
 Thanks!
 PS: Refer to https://issues.apache.org/jira/browse/GERONIMO-5055,
 plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_en.properties
  has been modified. You can modify systemdatabase_zh.properties  
 systemdatabase_ja.properties accordingly.

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

[BUILD] branches/2.1: Failed for Revision: 946531