Re: [ANNOUNCE] Geronimo Eclipse Plugin 3.0-beta-1 release

2011-12-06 Thread Rex Wang
Congrats, and thanks Janet!

-Rex

2011/12/6 han hongfang hanhongf...@gmail.com

 Hi,

 Apache Geronimo project is pleased to announce the available of Apache
 Geronimo Eclipse Plugin v3.0-beta-1. It supports Geronimo 3.0-beta-1 server
 and Eclipse 3.7 (Indigo).

 Visit the links to GEP 3.0-beta-1 release notes.

 http://www.apache.org/dist/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0-beta-1.txt

 The new version have been available through eclipse update site now.
 http://www.apache.org/dist/geronimo/eclipse/updates/

 For manual installation, GEP 3.0-beta-1 can be downloaded from
 http://apache.org/dist/geronimo/eclipse/3.0-beta-1/

 THANK YOU all that contributed to this release!

 --
 Best regards,

 Han Hong Fang (Janet)
 hanhongfang AT apache.org





-- 
Lei Wang (Rex)
rwonly AT apache.org


Re: [Vote] Release Geronimo Samples Daytrader 3.0-beta-1 RC4

2011-12-06 Thread viola lu
Here is my +1
mvn clean install on suse 10 sp2
mvn rat:check, no license problem

run osgi samples.


Summary
---
Notes: 2
Binaries: 0
Archives: 0
Standards: 2

Apache Licensed: 2
Generated Documents: 0

JavaDocs are generated and so license header is optional
Generated files do not required license headers

0 Unknown Licenses

***

Archives (+ indicates readable, $ unreadable):


*
  Files with AL headers will be marked L
  Binary files (which do not require AL headers) will be marked B
  Compressed archives will be marked A
  Notices, licenses etc will be marked N
  N LICENSE
  N NOTICE
  ALpom.xml
  ALsrc/site/site.xml

 *
 Printing headers for files without AL header...



On Fri, Nov 25, 2011 at 7:02 PM, viola lu viola...@gmail.com wrote:

 Hi Devs,


 A forth release candidate for Geronimo Sample  Daytrader  3.0-beta-1 has
 been created and staged coz of previous failure release candidate.

 The tags have been created here:


 https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1

 https://svn.apache.org/repos/asf/geronimo/daytrader/tags/daytrader-3.0-beta-1/

 The staging repos is here:

 https://repository.apache.org/content/repositories/orgapachegeronimo-210/
  (Daytrader)
 *https://repository.apache.org/content/repositories/orgapachegeronimo-247*
  (Sample)


 The main artifacts up for vote are the source release archives:
 *https://repository.apache.org/content/repositories/orgapachegeronimo-247*
 *
 /org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.tar.gzhttps://repository.apache.org/content/repositories/orgapachegeronimo-231/org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.tar.gz
 *
 *https://repository.apache.org/content/repositories/orgapachegeronimo-247*
 *
 /org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.ziphttps://repository.apache.org/content/repositories/orgapachegeronimo-231/org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.zip
 *


 https://repository.apache.org/content/repositories/orgapachegeronimo-210/org/apache/geronimo/daytrader/daytrader-parent/3.0-beta-1/daytrader-parent-3.0-beta-1-source-release.tar.gz

 https://repository.apache.org/content/repositories/orgapachegeronimo-210/org/apache/geronimo/daytrader/daytrader-parent/3.0-beta-1/daytrader-parent-3.0-beta-1-source-release.zip

 Here is sample update


-  Append Java EE 6 and OSGi samples


 Remove empty java file

 https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/singletonejb-javaee6/singletonejb-javaee6-war/src/main/java/org/apache/geronimo/samples/javaee6/singletonejb/sessionBeans/

 Remove useless dependency files

 https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee5/DataCDInfo/DataCDInfo-JTA-jetty/src/main/


 The vote will be open for the 72-hour minimum.

 [  ] +1 about time to push this out the door
 [  ]  0 no opinion
 [  ] -1 not this one  (please explain why)

 --
 viola

 Apache Geronimo




-- 
viola

Apache Geronimo


[jira] [Created] (GERONIMO-6225) IllegalArgumentException when deploying a web 2.0 sample app with space in the dojox libraries

2011-12-06 Thread Forrest Xia (Created) (JIRA)
IllegalArgumentException when deploying a web 2.0 sample app with space in the 
dojox libraries
--

 Key: GERONIMO-6225
 URL: https://issues.apache.org/jira/browse/GERONIMO-6225
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Tomcat, web
Affects Versions: 3.0-beta-1
Reporter: Forrest Xia


1. Start geronimo server,
2. Deploy two derby net XA data sources with attached plan files 
VacationPool-plan_3.0.xml and DonatePool-plan_3.0.xml,
3. Deploy the JMS resources with geronimo-activemq-ra-version.rar and the 
attached plan file JMSResources-plan_3.0.xml,
4. Deploy the attached EAR, then you will see an exception in the admin console:

The application was not deployed.The application was not deployed.
java.lang.IllegalArgumentException
org.apache.geronimo.common.DeploymentException: 
java.lang.IllegalArgumentException
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:279)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
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:883)
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:736)
Caused by: java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:853)
at java.net.URI.resolve(URI.java:1039)
at org.apache.geronimo.j2ee.deployment.Module.resolve(Module.java:186)
at 
org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.installModule(AbstractWebModuleBuilder.java:378)
at 
org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.installModule(SwitchingModuleBuilder.java:162)
at 
org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:655)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255)
... 12 more
Caused by: java.net.URISyntaxException: Illegal character in path at index 39: 
dojox/data/demos/geography/Commonwealth of Australia/
at java.net.URI$Parser.fail(URI.java:2820)
at java.net.URI$Parser.checkChars(URI.java:2993)
at java.net.URI$Parser.parseHierarchical(URI.java:3077)
at java.net.URI$Parser.parse(URI.java:3035)
at java.net.URI.(URI.java:589)
at java.net.URI.create(URI.java:851)
... 18 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (GERONIMO-6225) IllegalArgumentException when deploying a web 2.0 sample app with space in the dojox libraries

2011-12-06 Thread Forrest Xia (Updated) (JIRA)

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

Forrest Xia updated GERONIMO-6225:
--

Attachment: DonateEAR.ear
JMSResources-plan_3.0.xml
DonatePool-plan_3.0.xml
VacationPool-plan_3.0.xml

 IllegalArgumentException when deploying a web 2.0 sample app with space in 
 the dojox libraries
 --

 Key: GERONIMO-6225
 URL: https://issues.apache.org/jira/browse/GERONIMO-6225
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Tomcat, web
Affects Versions: 3.0-beta-1
Reporter: Forrest Xia
  Labels: tomcat,deployment, web2.0,
 Attachments: DonateEAR.ear, DonatePool-plan_3.0.xml, 
 JMSResources-plan_3.0.xml, VacationPool-plan_3.0.xml


 1. Start geronimo server,
 2. Deploy two derby net XA data sources with attached plan files 
 VacationPool-plan_3.0.xml and DonatePool-plan_3.0.xml,
 3. Deploy the JMS resources with geronimo-activemq-ra-version.rar and the 
 attached plan file JMSResources-plan_3.0.xml,
 4. Deploy the attached EAR, then you will see an exception in the admin 
 console:
 The application was not deployed.The application was not deployed.
 java.lang.IllegalArgumentException
 org.apache.geronimo.common.DeploymentException: 
 java.lang.IllegalArgumentException
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:279)
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
 at java.lang.reflect.Method.invoke(Method.java:611)
 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:883)
 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:736)
 Caused by: java.lang.IllegalArgumentException
 at java.net.URI.create(URI.java:853)
 at java.net.URI.resolve(URI.java:1039)
 at org.apache.geronimo.j2ee.deployment.Module.resolve(Module.java:186)
 at 
 org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.installModule(AbstractWebModuleBuilder.java:378)
 at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.installModule(SwitchingModuleBuilder.java:162)
 at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:655)
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255)
 ... 12 more
 Caused by: java.net.URISyntaxException: Illegal character in path at index 
 39: dojox/data/demos/geography/Commonwealth of Australia/
 at java.net.URI$Parser.fail(URI.java:2820)
 at java.net.URI$Parser.checkChars(URI.java:2993)
 at java.net.URI$Parser.parseHierarchical(URI.java:3077)
 at java.net.URI$Parser.parse(URI.java:3035)
 at java.net.URI.(URI.java:589)
 at java.net.URI.create(URI.java:851)
 ... 18 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (GERONIMO-6226) NoClassDefFoundError when deploying DonateEAR.ear to G 3.0-beta-1 server

2011-12-06 Thread Forrest Xia (Created) (JIRA)
NoClassDefFoundError when deploying DonateEAR.ear to G 3.0-beta-1 server


 Key: GERONIMO-6226
 URL: https://issues.apache.org/jira/browse/GERONIMO-6226
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: application client, deployment
Affects Versions: 3.0-beta-1
Reporter: Forrest Xia


Recurring steps refer to GERONIMO-6225, just modify the EAR file to remove the 
demos folder from the ear, and deploy it to G server, you will see an exception 
on the admin console like this:

The application was not deployed.
Could not fully load class: Main
due to:donate.ejb.interfaces.DonateBeanRemote
in classLoader:
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@45a145a1
java.lang.NoClassDefFoundError: Could not fully load class: Main
due to:donate.ejb.interfaces.DonateBeanRemote
in classLoader:
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@45a145a1
at org.apache.xbean.finder.ClassFinder.(ClassFinder.java:136)
at 
org.apache.geronimo.client.builder.AppClientModuleBuilder.createAppClientClassFinder(AppClientModuleBuilder.java:946)
at 
org.apache.geronimo.client.builder.AppClientModuleBuilder.addGBeans(AppClientModuleBuilder.java:786)
at 
org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:763)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
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:883)
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:736)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




Re: Geronimo redeploy issue.

2011-12-06 Thread Jay D. McHugh

Hello Ranjan,

The one hint I would offer is to stop the server using either the 
console or the shutdown script.  Simply killing the java process can 
leave the server in an unstable state.


Jay

On 12/05/2011 11:16 PM, ranbaab wrote:

Hi,

Our exploded web application is extracted in the deploy folder of geronimo
during the time of installation.
The application is install and launch the UI successfully.
After stopping the server, if I manually update any jsp or any file from the
deployed application, the server got hang after restart.
-
The geronimo.log does not give any clue, the server got hang at

2011-12-01 14:42:46,199 INFO  [DirectoryMonitor] At startup, found
/geronimo/deploy/ourApplication with deploy time 1322730003272 and file time
1322729818000
2011-12-01 14:42:50,423 INFO  [DirectoryHotDeployer] *Redeploying
ourApplication*

And the console output is

Listening on Ports:
 8009 0.0.0.0 Tomcat Connector AJP TomcatAJPConnector
  0.0.0.0 JMX Remoting Connector
40080 0.0.0.0 Tomcat Connector HTTP BIO TomcatWebConnector
40099 0.0.0.0 RMI Naming
40443 0.0.0.0 Tomcat Connector HTTPS BIO TomcatWebSSLConnector

   Started Application Modules:
 WAR: ourapplication/xyz/application/war
 WAR: org.apache.geronimo.configs/remote-deploy-tomcat/2.2.1/car

   Web Applications:
 /ourApplication
 /remote-deploy

Geronimo Application Server started
-
In geronimo-web.xml, version is not a numeric
sys:versionapplication/sys:version

I am wondering whether the time stamp change of the file is causing the
issue.

According to my knowledge, the hot deploy should take care this scenerio.

The geronimo server is stop by using kill -9 PID.

Even I download the source code and try to build it, but due to some issue,
I am not able to build it.

The application got stuck in the file
org.apache.geronimo.deployment.hot.DirectoryHotDeployer method fileUpdated

  public String fileUpdated(File file, String configId) {
 log.info(*Redeploying  + file.getName())*;
 DeploymentManager mgr = null;

I would really appreciate if some one throw some light about this issue.



Thanks,
Ranjan

--
View this message in context: 
http://apache-geronimo.328035.n3.nabble.com/Geronimo-redeploy-issue-tp3563502p3563502.html
Sent from the Development mailing list archive at Nabble.com.


[jira] [Created] (GERONIMO-6227) Version numbers not resolved in resulting karaf-framework-3.0-beta-1-features.xml

2011-12-06 Thread Ulrich Romahn (Created) (JIRA)
Version numbers not resolved in resulting 
karaf-framework-3.0-beta-1-features.xml
-

 Key: GERONIMO-6227
 URL: https://issues.apache.org/jira/browse/GERONIMO-6227
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: osgi-bundles
Affects Versions: 3.0-M1
 Environment: All
Reporter: Ulrich Romahn


The build process is supposed to replace all version numbers contained in the 
source file features.xml inside 
framework/configs/karaf-framework/src/main/filtered-resources with the 
corresponding values defined somewhere.
Example: 
  the line 

bundlemvn:org.apache.geronimo.specs/geronimo-servlet_2.5_spec/${geronimo.servlet.version}/bundle
  should be expanded to something like

bundlemvn:org.apache.geronimo.specs/geronimo-servlet_2.5_spec/1.1.2/bundle
in the resulting file.
However, those environment variables are not defined anywhere and hence they 
are not resolved during build time.

This is causing error messages while trying to install an OSGI feature, such as 
the webconsole or other OSGI features that depend on such bundles/features.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




Re: Geronimo redeploy issue.

2011-12-06 Thread Kevan Miller

On Dec 6, 2011, at 12:16 AM, ranbaab wrote:

 Hi,
 
 Our exploded web application is extracted in the deploy folder of geronimo
 during the time of installation.
 The application is install and launch the UI successfully.
 After stopping the server, if I manually update any jsp or any file from the
 deployed application, the server got hang after restart.

What version of Geronimo are you using? You should create a Jira. If you can 
create a stacktrace for the server (kill -3), after it hangs, that would be 
helpful…

In the future -- this type of question/problem should be on user@, rather than 
dev@

--kevan

[jira] [Commented] (GERONIMO-6227) Version numbers not resolved in resulting karaf-framework-3.0-beta-1-features.xml

2011-12-06 Thread Ulrich Romahn (Commented) (JIRA)

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

Ulrich Romahn commented on GERONIMO-6227:
-

UPDATE:
I think I figured out what the issue is here. The pom.xml of the 
karaf-framework artifact is importing the main pom of karaf assuming it would 
also get all the properties defined therein. However, this is not what 
importing the pom does - it only imports the dependencies defined in this pom, 
but not the properties. In order to fix the issue, I had to manually copy all 
the missing properties from the karaf main pom into the pom of the Geronimo 
karaf-framework. This is not perfect but at least a stop-gap.

 Version numbers not resolved in resulting 
 karaf-framework-3.0-beta-1-features.xml
 -

 Key: GERONIMO-6227
 URL: https://issues.apache.org/jira/browse/GERONIMO-6227
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: osgi-bundles
Affects Versions: 3.0-M1
 Environment: All
Reporter: Ulrich Romahn
  Labels: build

 The build process is supposed to replace all version numbers contained in the 
 source file features.xml inside 
 framework/configs/karaf-framework/src/main/filtered-resources with the 
 corresponding values defined somewhere.
 Example: 
   the line 
 
 bundlemvn:org.apache.geronimo.specs/geronimo-servlet_2.5_spec/${geronimo.servlet.version}/bundle
   should be expanded to something like
 
 bundlemvn:org.apache.geronimo.specs/geronimo-servlet_2.5_spec/1.1.2/bundle
 in the resulting file.
 However, those environment variables are not defined anywhere and hence they 
 are not resolved during build time.
 This is causing error messages while trying to install an OSGI feature, such 
 as the webconsole or other OSGI features that depend on such bundles/features.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (GERONIMO-6225) IllegalArgumentException when deploying a web 2.0 sample app with space in the dojox libraries

2011-12-06 Thread Forrest Xia (Updated) (JIRA)

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

Forrest Xia updated GERONIMO-6225:
--

Attachment: cviewer-3.0.0.0_mod.war

A simple app to reproduce this issue easily

 IllegalArgumentException when deploying a web 2.0 sample app with space in 
 the dojox libraries
 --

 Key: GERONIMO-6225
 URL: https://issues.apache.org/jira/browse/GERONIMO-6225
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: Tomcat, web
Affects Versions: 3.0-beta-1
Reporter: Forrest Xia
  Labels: deployment,, tomcat,, web2.0,
 Attachments: DonateEAR.ear, DonatePool-plan_3.0.xml, 
 JMSResources-plan_3.0.xml, VacationPool-plan_3.0.xml, cviewer-3.0.0.0_mod.war


 1. Start geronimo server,
 2. Deploy two derby net XA data sources with attached plan files 
 VacationPool-plan_3.0.xml and DonatePool-plan_3.0.xml,
 3. Deploy the JMS resources with geronimo-activemq-ra-version.rar and the 
 attached plan file JMSResources-plan_3.0.xml,
 4. Deploy the attached EAR, then you will see an exception in the admin 
 console:
 The application was not deployed.The application was not deployed.
 java.lang.IllegalArgumentException
 org.apache.geronimo.common.DeploymentException: 
 java.lang.IllegalArgumentException
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:279)
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
 at java.lang.reflect.Method.invoke(Method.java:611)
 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:883)
 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:736)
 Caused by: java.lang.IllegalArgumentException
 at java.net.URI.create(URI.java:853)
 at java.net.URI.resolve(URI.java:1039)
 at org.apache.geronimo.j2ee.deployment.Module.resolve(Module.java:186)
 at 
 org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.installModule(AbstractWebModuleBuilder.java:378)
 at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.installModule(SwitchingModuleBuilder.java:162)
 at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:655)
 at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255)
 ... 12 more
 Caused by: java.net.URISyntaxException: Illegal character in path at index 
 39: dojox/data/demos/geography/Commonwealth of Australia/
 at java.net.URI$Parser.fail(URI.java:2820)
 at java.net.URI$Parser.checkChars(URI.java:2993)
 at java.net.URI$Parser.parseHierarchical(URI.java:3077)
 at java.net.URI$Parser.parse(URI.java:3035)
 at java.net.URI.(URI.java:589)
 at java.net.URI.create(URI.java:851)
 ... 18 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Closed] (GERONIMO-6178) Illegal character in path exception if module package contains space

2011-12-06 Thread viola.lu (Closed) (JIRA)

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

viola.lu closed GERONIMO-6178.
--

Resolution: Duplicate

duplicate with  https://issues.apache.org/jira/browse/GERONIMO-6225
close this one.

 Illegal character in path exception if module package contains space
 --

 Key: GERONIMO-6178
 URL: https://issues.apache.org/jira/browse/GERONIMO-6178
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
Affects Versions: 3.0
Reporter: viola.lu
Assignee: viola.lu
Priority: Minor
 Fix For: 3.0.1


 2011-09-26 14:30:58,250 WARN  [TomcatModuleBuilder] Web application . does 
 not contain a WEB-INF/geronimo-web.xml deployment plan.  This may or may not 
 be a problem, depending on whether you have things like resource references 
 that need to be resolved.  You can also give the deployer a separate 
 deployment plan file on the command line.
 2011-09-26 14:30:59,578 ERROR [Deployer] Deployment failed due to 
 java.lang.IllegalArgumentException
   at java.net.URI.create(URI.java:853)
   at java.net.URI.resolve(URI.java:1039)
   at org.apache.geronimo.j2ee.deployment.Module.resolve(Module.java:186)
   at 
 org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.installModule(AbstractWebModuleBuilder.java:378)
   at 
 org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.installModule(SwitchingModuleBuilder.java:162)
   at 
 org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:655)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255)
   at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
   at java.lang.reflect.Method.invoke(Method.java:611)
   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:883)
   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:736)
 Caused by: java.net.URISyntaxException: Illegal character in path at index 
 33: dojox/data/demos/geography/United States of America/
   at java.net.URI$Parser.fail(URI.java:2820)
   at java.net.URI$Parser.checkChars(URI.java:2993)
   at java.net.URI$Parser.parseHierarchical(URI.java:3077)
   at java.net.URI$Parser.parse(URI.java:3035)
   at java.net.URI.init(URI.java:589)
   at java.net.URI.create(URI.java:851)
   ... 18 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




BTW… WOW

2011-12-06 Thread Jason Dillon
Its been a long time since I fired up the server, but I just did (to look at 
the keystore muck) and WOW.  3.0 looks really nice... from the web-console at 
least.  I still have issue with the text-console you are using, but eh 
whatever ;-)

Nice work folks!

--jason

[jira] [Updated] (YOKO-437) CORBA needs to add the function of testing

2011-12-06 Thread zxpgroovy (Updated) (JIRA)

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

zxpgroovy updated YOKO-437:
---

Attachment: 2113 (2).txt

 CORBA  needs to add the function of testing
 ---

 Key: YOKO-437
 URL: https://issues.apache.org/jira/browse/YOKO-437
 Project: Yoko - CORBA Server
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: RMI-IIOP
Affects Versions: v1.0-incubating-M1
 Environment: CORBA  needs to add the function of testing
Reporter: zxpgroovy
  Labels: documentation, patch
 Attachments: 2113 (2).txt

   Original Estimate: 24h
  Remaining Estimate: 24h

 CORBA  needs to add the function of testing

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (YOKO-437) CORBA needs to add the function of testing

2011-12-06 Thread zxpgroovy (Updated) (JIRA)

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

zxpgroovy updated YOKO-437:
---

Attachment: (was: 2113 (2).txt)

 CORBA  needs to add the function of testing
 ---

 Key: YOKO-437
 URL: https://issues.apache.org/jira/browse/YOKO-437
 Project: Yoko - CORBA Server
  Issue Type: New Feature
  Security Level: public(Regular issues) 
  Components: RMI-IIOP
Affects Versions: v1.0-incubating-M1
 Environment: CORBA  needs to add the function of testing
Reporter: zxpgroovy
  Labels: documentation, patch
   Original Estimate: 24h
  Remaining Estimate: 24h

 CORBA  needs to add the function of testing

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira