[jira] Closed: (GERONIMO-4305) PortletException with Redeploy application checked for non existent application

[Rex Wang (JIRA)]

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

Rex Wang closed GERONIMO-4305.
--


Thanks Ivan

> PortletException with Redeploy application checked for non existent 
> application
> ---
>
> Key: GERONIMO-4305
> URL: https://issues.apache.org/jira/browse/GERONIMO-4305
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 2.1.3, 2.1.4
>Reporter: Jürgen Weber
>Assignee: Rex Wang
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: GERONIMO-4305-trunk.patch, GERONIMO-4305.patch
>
>
> If you deploy an application, have "Redeploy application" checked, but the 
> application does not exist, there is a PortletException.
> This does not look very professional, Geronimo should instead handle 
> gracefully the situation.
> HTTP ERROR: 500
> INTERNAL_SERVER_ERROR
> RequestURI=/console/portal//Applications/Deploy%20New/__ac0x3plugin0x2Deployment!227983155|0
> Caused by:
> javax.portlet.PortletException
>   at 
> org.apache.geronimo.console.configmanager.DeploymentPortlet.processAction(DeploymentPortlet.java:224)
> Caused by: javax.portlet.PortletException: jWhichJSP does not appear to be a 
> the name of a module available on the selected server. Perhaps it has already 
> been stopped or undeployed?  If you're trying to specify a TargetModuleID, 
> use the syntax TargetName|ModuleName instead. If you're not sure what's 
> running, try the list-modules command.
>   at 
> org.apache.geronimo.console.configmanager.DeploymentPortlet.identifyTargets(DeploymentPortlet.java:254)
>   at 
> org.apache.geronimo.console.configmanager.DeploymentPortlet.processAction(DeploymentPortlet.java:142)
>   ... 57 more
> Caused by: org.apache.geronimo.common.DeploymentException: jWhichJSP does not 
> appear to be a the name of a module available on the selected server. Perhaps 
> it has already been stopped or undeployed?  If you're trying to specify a 
> TargetModuleID, use the syntax TargetName|ModuleName instead. If you're not 
> sure what's running, try the list-modules command.
>   at 
> org.apache.geronimo.deployment.plugin.ConfigIDExtractor.identifyTargetModuleIDs(ConfigIDExtractor.java:205)
>   at 
> org.apache.geronimo.console.configmanager.DeploymentPortlet.identifyTargets(DeploymentPortlet.java:242)
>   ... 58 more
> Nested Exception is javax.portlet.PortletException: jWhichJSP does not appear 
> to be a the name of a module available on the selected server. Perhaps it has 
> already been stopped or undeployed?  If you're trying to specify a 
> TargetModuleID, use the syntax TargetName|ModuleName instead. If you're not 
> sure what's running, try the list-modules command.
>   at 
> org.apache.geronimo.console.configmanager.DeploymentPortlet.identifyTargets(DeploymentPortlet.java:254)
>   at 
> org.apache.geronimo.console.configmanager.DeploymentPortlet.processAction(DeploymentPortlet.java:142)
>   at 
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)

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

[jira] Closed: (GERONIMO-4641) XSSXSRFFilter cause some link failure

[Rex Wang (JIRA)]

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

Rex Wang closed GERONIMO-4641.
--


Thanks Ivan

> XSSXSRFFilter cause some link failure 
> --
>
> Key: GERONIMO-4641
> URL: https://issues.apache.org/jira/browse/GERONIMO-4641
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1.4, 2.1.5, 2.2
>Reporter: Rex Wang
>Assignee: Rex Wang
> Fix For: 2.1.5, 2.2
>
> Attachments: GERONIMO-4641-b21-revised.patch, 
> GERONIMO-4641-b21-updated.patch, GERONIMO-4641-trunk-revised.patch, 
> GERONIMO-4641-trunk.patch
>
>
> the XSSXSRFFilter will cause the link failure when the content contains some 
> special char.
> such as
> the links in Database Pools portlet 
> "Import from JBoss 4 "
> "Import from WebLogic 8.1 "

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

[jira] Closed: (GERONIMO-4503) PlanCreator threw exception with .war

[Rex Wang (JIRA)]

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

Rex Wang closed GERONIMO-4503.
--


Thanks Ivan.

> PlanCreator threw exception with .war
> -
>
> Key: GERONIMO-4503
> URL: https://issues.apache.org/jira/browse/GERONIMO-4503
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: PlanCreator
>Affects Versions: 2.2
> Environment: WinXP+Sun Java1.6.0+ Geronimo v2.2  Build0107 
>Reporter: Chi Runhua
>Assignee: Rex Wang
>Priority: Blocker
> Fix For: 2.2
>
> Attachments: GERONIMO-4503-updated.patch, WebAppJDBCAccess.war
>
>
> A simple WebAppJDBCAccess.war without a geronimo deployment plan, so I tried 
> to create one using wizard from v2.2 , but failed with HTTP 500 error.  
> Exception throwed from command line as followed:
> Note: Tried the same .war on Geronimo v2.1.3+Java1.6,  everything works fine.
> ++
> 2009-01-09 15:14:22,000 ERROR [[PlanCreator]] Servlet.service() for servlet 
> PlanCreator threw exception
> java.lang.ClassNotFoundException: 
> org.apache.geronimo.deployment.plugin.jmx.JMXDeploymentManager in classloader 
> org.apache.geronimo.plugins/plancreator-console-tomcat/2.2-SNAPSHOT/car
>   at 
> org.apache.geronimo.kernel.config.MultiParentClassLoader.loadOptimizedClass(MultiParentClassLoader.java:413)
>   at 
> org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:255)
>   at java.lang.ClassLoader.loadClass(Unknown Source)
>   at java.lang.ClassLoader.loadClassInternal(Unknown Source)
>   at 
> org.apache.geronimo.console.configcreator.JSR88_Util.createApplicationInfo(JSR88_Util.java:71)
>   at 
> org.apache.geronimo.console.configcreator.GetArchiveHandler.actionAfterView(GetArchiveHandler.java:70)
>   at 
> org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:114)
>   at 
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
>   at org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:535)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:472)
>   at 
> org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
>   at 
> org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
>   at 
> org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219)
>   at 
> org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
>   at 
> org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>   at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>   at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>   at 
> org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
>   at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
>   at 
> org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:406)
>   at 
> org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
>   at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>   at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>   at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>   at 
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:568)
>   at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
>   at 
> o

[jira] Closed: (GERONIMO-4534) Can't secure connect to JMX with JConsole.

[Shawn Jiang (JIRA)]

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

Shawn Jiang closed GERONIMO-4534.
-


Closing it.  Thanks Jarek.


> Can't secure connect to JMX with JConsole.
> --
>
> Key: GERONIMO-4534
> URL: https://issues.apache.org/jira/browse/GERONIMO-4534
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: management
>Affects Versions: 2.1.4, 2.2
> Environment: Windows XP 
> Sun JDK 1.5
> geronimo_tomcat6_2.1.4_snapshot/20090209/
>Reporter: Shawn Jiang
>Assignee: Jarek Gawor
> Fix For: 2.1.4, 2.2
>
>
> I'm trying to use jconsole to securely connect to the JMX server of geronimo 
> 2.1.4 snapshot according to the guide here:
> http://cwiki.apache.org/GMOxDOC21/configure-secure-jmx-server.html
> * 1, Change the config.xml and start the server.
> * 2, use "jconsole 
> -J-Djavax.net.ssl.keyStore=%GERONMO_HOME%\var\security\keystores\geronimo-default
>  -J-Djavax.net.ssl.keyStorePassword=secret 
> -J-Djavax.net.ssl.trustStore=%GERONMO_HOME%\var\security\keystores\geronimo-default
>  -J-Djavax.net.ssl.trustStorePassword=secret " start the jconsole.
> * 3, in the jconsole interface->advanced, input:
> JMX URL:   service:jmx:rmi:///jndi/rmi://localhost:1099/JMXSecureConnector
> user name: system
> password: manager
> * 4, click the connect button.
> expected result: could connect to the JMX server.
> actual result:  CAN NOT connect to the JMX server.

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

[jira] Closed: (GERONIMO-4518) Can't shutdown the server when host was set to 127.0.0.1 in config-substitutions.properties

[Shawn Jiang (JIRA)]

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

Shawn Jiang closed GERONIMO-4518.
-


Closing it.  Thanks Jarek.


> Can't shutdown the server when host was set to 127.0.0.1 in 
> config-substitutions.properties
> ---
>
> Key: GERONIMO-4518
> URL: https://issues.apache.org/jira/browse/GERONIMO-4518
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: startup/shutdown
>Affects Versions: 2.1.4, 2.2
> Environment: Windows XP + Sun JDK 1.5
>Reporter: Shawn Jiang
>Assignee: Jarek Gawor
> Fix For: 2.1.4, 2.2
>
> Attachments: G4518_Shawn.patch
>
>
> 1, change the host in config-substitutions.properties to 127.0.0.1
> 2, start the server.
> 3, shutdown the server.
> *expected result*: the server could be shutdown.
> *actual result*: the sever can't be shutdown with exception:  
> java.net.ConnectException: Connection refused: connect
> --
> C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\bin>shutdown --host 127.0.0.1
> Using GERONIMO_HOME:   C:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT
> Using GERONIMO_TMPDIR: var\temp
> Using JRE_HOME:D:\dev\JDKs\sun_jdk1.5.0_15\jre
> log4j:WARN No appenders could be found for logger 
> (org.apache.geronimo.kernel.basic.BasicKernel).
> log4j:WARN Please initialize the log4j system properly.
> Username: system
> Password: ***
> Locating server on 127.0.0.1:1099...
> Could not communicate with the server.  The server may not be running or the 
> port number may be inco
> rrect (Connection refused to host: 6.153.277.58; nested exception is:
> java.net.ConnectException: Connection refused: connect)

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

[jira] Closed: (GERONIMO-4467) null pointer acess in code.

[Shawn Jiang (JIRA)]

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

Shawn Jiang closed GERONIMO-4467.
-


Closing it.  Thanks Joe.


> null pointer acess in code.
> ---
>
> Key: GERONIMO-4467
> URL: https://issues.apache.org/jira/browse/GERONIMO-4467
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Shawn Jiang
>Assignee: Joe Bohn
>Priority: Minor
> Fix For: 2.1.4, 2.2
>
> Attachments: 4467_shawn.patch
>
>
> null pointer acess in code.  
> {code}
>   if (file == null) {
> throw new IOException("Entry not found: name=" + 
> file.getAbsolutePath());
> } else if (file.isDirectory()) {
> {code}

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

[jira] Closed: (GERONIMO-4498) ClassNotFoundException: BasicExtendedJMXConnectorInfoEditor throwned when farming geronimo using Deployment

[Shawn Jiang (JIRA)]

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

Shawn Jiang closed GERONIMO-4498.
-


Closing it.  Thanks Donald.


> ClassNotFoundException: BasicExtendedJMXConnectorInfoEditor throwned when 
> farming geronimo using Deployment
> ---
>
> Key: GERONIMO-4498
> URL: https://issues.apache.org/jira/browse/GERONIMO-4498
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.2
> Environment: Windows XP SP 2 + IBM SDK 1.5.0
>Reporter: Shawn Jiang
>Assignee: Donald Woods
>Priority: Blocker
> Fix For: 2.2
>
> Attachments: G4498_shawn_new.patch
>
>
> I'm trying to farm geronimo using deployment according to 
> http://cwiki.apache.org/GMOxDOC22/farming-using-deployment.html.
> 1, install the latest trunk 2.2-snapshot build as nodeA
> 2, update the var\config\config.xml with following farming config info:
>   {code:xml}
>  load="false">
> 
> ${clusterNodeName}
> 
> 
> ${clusterName}
> 
>name="org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=NodeInfo,name=NodeInfoB"
>  gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE-B
>  propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
>  name="extendedJMXConnectorInfo">
>  class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo" 
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2"; 
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0"; xmlns="">
> system
> manager
> rmi
> 9.123.237.58
> 1109
> JMXConnector
> false
>   
> 
> 
> {code}
> 3, start the server.
> 4, use {noformat}deploy.bat --user system --password manager start 
> org.apache.geronimo.configs/farming//car {noformat} to start the farming 
> config.
> *expected result*:   the farming config could be started without problem.
> *actual result*:the farming config could not be started up with 
> exceptions in log. the log is:
> __
> 2009-01-07 16:37:56,453 ERROR [GBeanInstanceState] Error while starting; 
> GBean is now in the FAILED state: 
> abstractName="org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?configurationName=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car"
> java.lang.IllegalStateException: Cannot load property editor 
> [org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor]
>   at 
> org.apache.geronimo.system.configuration.GBeanOverride.loadPropertyEditor(GBeanOverride.java:423)
>   at 
> org.apache.geronimo.system.configuration.GBeanOverride.getValue(GBeanOverride.java:399)
>   at 
> org.apache.geronimo.system.configuration.GBeanOverride.applyOverrides(GBeanOverride.java:359)
>   at 
> org.apache.geronimo.system.configuration.LocalAttributeManager.setAttributes(LocalAttributeManager.java:228)
>   at 
> org.apache.geronimo.system.configuration.LocalAttributeManager.applyOverrides(LocalAttributeManager.java:197)
>   at 
> org.apache.geronimo.kernel.config.Configuration.(Configuration.java:292)
>   at sun.reflect.GeneratedConstructorAccessor23.newInstance(Unknown 
> Source)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
>   at 
> org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:882)
>   at 
> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:272)
>   at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
>   at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:910)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
>   at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524)
>   at 
> org.apache.geronimo.kernel.basic.BasicKernel.startGBean(BasicKernel.java:359)
>   at 
> org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:163)
>   at 
> o

[jira] Closed: (GERONIMO-4441) The assignment to variable "handler" has no effect in ConstantLoginModule.java

[Shawn Jiang (JIRA)]

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

Shawn Jiang closed GERONIMO-4441.
-


Closing it.  Thanks Jarek.


> The assignment to variable "handler" has no effect in ConstantLoginModule.java
> --
>
> Key: GERONIMO-4441
> URL: https://issues.apache.org/jira/browse/GERONIMO-4441
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1.3, 2.1.4, 2.2
>Reporter: Shawn Jiang
>Assignee: Jarek Gawor
> Fix For: 2.1.4, 2.2
>
> Attachments: GERONIMO-4441.patch
>
>
> Seems it's a typo bug in  
> https://svn.apache.org/repos/asf/geronimo/server/trunk/framework/modules/geronimo-security/src/main/java/org/apache/geronimo/security/realm/providers/ConstantLoginModule.java
>/**
>  * Save the userName and groupNames settings for use during commit()
>  */
> public void initialize(Subject subject, CallbackHandler callbackHandler,
> Map sharedState, Map options) {
> this.subject = subject;
> this.handler = handler;
> 
> this.userName = (String)options.get(USER_NAME);
> this.groupNames = (String)options.get(GROUP_NAMES);
> }
> "  this.handler = handler;"  should be  " this.handler = callbackHandler;"

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

[jira] Closed: (GERONIMO-4595) script error when clicking the update button in portlet console ---server---Server Logs -- Log Manager

[Shawn Jiang (JIRA)]

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

Shawn Jiang closed GERONIMO-4595.
-


Closing it.  Thanks Joe.


> script error when clicking the update button in portlet console 
> ---server---Server Logs -- Log Manager 
> ---
>
> Key: GERONIMO-4595
> URL: https://issues.apache.org/jira/browse/GERONIMO-4595
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1.4, 2.1.5, 2.2
> Environment: IE7 + windows XP + sun JDK 1.5
>Reporter: Shawn Jiang
>Assignee: Joe Bohn
>Priority: Minor
> Fix For: 2.1.4, 2.1.5
>
> Attachments: patch_script_error.patch
>
>
> reproduce steps:
> 1, Use IE to login to console.
> 2, Click the update button in portlet console --->  server  --->  Server Logs 
> -->  Log Manager 
> expected result:  no error
> actual result:   there's a script error " logFile is not defined"

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

[jira] Closed: (GERONIMO-4633) extra semicolon in code.

[Shawn Jiang (JIRA)]

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

Shawn Jiang closed GERONIMO-4633.
-


Closing it.  Thanks Ivan.



> extra semicolon in code.
> 
>
> Key: GERONIMO-4633
> URL: https://issues.apache.org/jira/browse/GERONIMO-4633
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.2
> Environment: xp + sun jdk 1.5
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Trivial
> Fix For: 2.2
>
> Attachments: extra_semicolon.patch, extra_semicolon_more.patch
>
>
> extra semicolon in code.

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

[jira] Closed: (GERONIMO-4605) Text based apache license at the bottom of every console pages

[Shawn Jiang (JIRA)]

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

Shawn Jiang closed GERONIMO-4605.
-


Closing it.  Thanks Joe.


> Text based apache license at the bottom of every console pages
> --
>
> Key: GERONIMO-4605
> URL: https://issues.apache.org/jira/browse/GERONIMO-4605
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1.4, 2.1.5, 2.2
> Environment: geronimo-tomcat-2.1.4 rc2 + IBM JDK 1.5 +windows XP
>Reporter: Shawn Jiang
>Assignee: Joe Bohn
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: G4605.patch
>
>
> There are text based apache licenses at the bottom of every console pages 
> like this:
> ---
> * * Licensed to the Apache Software Foundation (ASF) under one or more * 
> contributor license agreements. See the NOTICE file distributed with * this 
> work for additional information regarding copyright ownership. * The ASF 
> licenses this file to You under the Apache License, Version 2.0 * (the 
> "License"); you may not use this file except in compliance with * the 
> License. You may obtain a copy of the License at * * 
> http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable 
> law or agreed to in writing, software * distributed under the License is 
> distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY 
> KIND, either express or implied. * See the License for the specific language 
> governing permissions and * limitations under the License. */ 
> ---
> It's not a big but an annoying problem from user's perspective. 

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

[jira] Assigned: (GERONIMO-4633) extra semicolon in code.

[Shawn Jiang (JIRA)]

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

Shawn Jiang reassigned GERONIMO-4633:
-

Assignee: Shawn Jiang

> extra semicolon in code.
> 
>
> Key: GERONIMO-4633
> URL: https://issues.apache.org/jira/browse/GERONIMO-4633
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Clustering
>Affects Versions: 2.2
> Environment: xp + sun jdk 1.5
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Trivial
> Fix For: 2.2
>
> Attachments: extra_semicolon.patch, extra_semicolon_more.patch
>
>
> extra semicolon in code.

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

Re: [VOTE] genesis 2.0 and geronimo-jaspic_1.0_spec 1.0

[David Jencks]

[X ]  +1 About time, yes yes yes


david jencks

On Jun 8, 2009, at 6:06 PM, David Jencks wrote:


This is a vote on two bits:

genesis 2.0, a new build system foundation based on great work by  
Jason Dillon and the new apache 6 pom and assembly plugin bits.


geronimo-jaspic_1.0_spec 1.0 a new spec jar for the jsr 196 jaspic  
spec.  This passes the jaspic signature test and with appropriate  
bits of jetty 7 passes the shared and servlet profile of the jaspic  
tck.


The jar type stuff is staged at

https://repository.apache.org/content/repositories/geronimo-staging-009/

In particular the source archives (which this vote is actually on)  
are at


https://repository.apache.org/content/repositories/geronimo-staging-009/org/apache/geronimo/genesis/genesis/2.0/genesis-2.0-source-release.tar.gz
https://repository.apache.org/content/repositories/geronimo-staging-009/org/apache/geronimo/genesis/genesis/2.0/genesis-2.0-source-release.zip

and

https://repository.apache.org/content/repositories/geronimo-staging-009/org/apache/geronimo/specs/geronimo-jaspic_1.0_spec/1.0/geronimo-jaspic_1.0_spec-1.0-source-release.tar.gz
https://repository.apache.org/content/repositories/geronimo-staging-009/org/apache/geronimo/specs/geronimo-jaspic_1.0_spec/1.0/geronimo-jaspic_1.0_spec-1.0-source-release.zip

with the signatures in the obvious place next to them.

The sites are staged at

http://people.apache.org/~djencks/staging-site/

in particular
http://people.apache.org/~djencks/staging-site/maven/genesis/2.0/
http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jaspic_1.0_spec/1.0/

the jar type stuff is using the new apache nexus instance which  
works great!




[ ]  +1 About time, yes yes yes
[ ] 0 Apathy
[ ]  -1 No thanks because

Please vote!

Thanks to Jason Dillon for setting up most of the new genesis 2.0  
system and to Brian Fox for getting the nexus setup working for us!


thanks
david jencks

[VOTE] genesis 2.0 and geronimo-jaspic_1.0_spec 1.0

[David Jencks]

This is a vote on two bits:

genesis 2.0, a new build system foundation based on great work by  
Jason Dillon and the new apache 6 pom and assembly plugin bits.


geronimo-jaspic_1.0_spec 1.0 a new spec jar for the jsr 196 jaspic  
spec.  This passes the jaspic signature test and with appropriate bits  
of jetty 7 passes the shared and servlet profile of the jaspic tck.


The jar type stuff is staged at

https://repository.apache.org/content/repositories/geronimo-staging-009/

In particular the source archives (which this vote is actually on) are  
at


https://repository.apache.org/content/repositories/geronimo-staging-009/org/apache/geronimo/genesis/genesis/2.0/genesis-2.0-source-release.tar.gz
https://repository.apache.org/content/repositories/geronimo-staging-009/org/apache/geronimo/genesis/genesis/2.0/genesis-2.0-source-release.zip

and

https://repository.apache.org/content/repositories/geronimo-staging-009/org/apache/geronimo/specs/geronimo-jaspic_1.0_spec/1.0/geronimo-jaspic_1.0_spec-1.0-source-release.tar.gz
https://repository.apache.org/content/repositories/geronimo-staging-009/org/apache/geronimo/specs/geronimo-jaspic_1.0_spec/1.0/geronimo-jaspic_1.0_spec-1.0-source-release.zip

with the signatures in the obvious place next to them.

The sites are staged at

http://people.apache.org/~djencks/staging-site/

in particular
http://people.apache.org/~djencks/staging-site/maven/genesis/2.0/
http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jaspic_1.0_spec/1.0/

the jar type stuff is using the new apache nexus instance which works  
great!




[ ]  +1 About time, yes yes yes
[ ] 0 Apathy
[ ]  -1 No thanks because

Please vote!

Thanks to Jason Dillon for setting up most of the new genesis 2.0  
system and to Brian Fox for getting the nexus setup working for us!


thanks
david jencks

Re: Impending votes

[David Jencks]

On Jun 8, 2009, at 1:49 PM, Kevan Miller wrote:



Dave,
Are you able to build Genesis ok?

My build fails with:

[INFO] Compiling 4 source files to /Users/kevan/geronimo/genesis/ 
trunk/genesis-maven-plugin/target/classes
[INFO]  


[ERROR] BUILD ERROR
[INFO]  


[INFO] Fatal error compiling

Embedded error: Prohibited package name: java.lang

I've seen this problem before. Seems to be an issue with Mac OS. I'm  
not sure how to fix.


I'm not seeing that problem, build works OK for me.  I think I've seen  
that error in other places when groovy was involved, as here.  I'm on  
jdk 6


david jencks




--kevan

Re: Impending votes

[Kevan Miller]

Dave,
Are you able to build Genesis ok?

My build fails with:

[INFO] Compiling 4 source files to /Users/kevan/geronimo/genesis/trunk/ 
genesis-maven-plugin/target/classes
[INFO]  


[ERROR] BUILD ERROR
[INFO]  


[INFO] Fatal error compiling

Embedded error: Prohibited package name: java.lang

I've seen this problem before. Seems to be an issue with Mac OS. I'm  
not sure how to fix.


--kevan

Re: Impending votes

[Kevan Miller]

On Jun 8, 2009, at 4:06 PM, David Jencks wrote:



On Jun 8, 2009, at 11:54 AM, Kevan Miller wrote:



On Jun 8, 2009, at 2:58 AM, David Jencks wrote:

I've been playing around with genesis to get it releasable and the  
jaspi spec jar.  Jetty needs the latter for their incipient IP  
review so we need to get it out quickly.


It looks like the site plugin is totally broken http://jira.codehaus.org/browse/MSITE-395 
 so I'll beat my head against that wall for only a few more  
minutes before giving up on having maven generated sites for  
multip module projects.  AFAICT the apache-release profile is  
working OK.


If anyone wants to take a look at this now's the time.  I plan to  
tag and call a vote tomorrow (monday).


There's one snapshot in genesis I still need to fix, the assembly  
plugin source-release descriptor.


David,
The NOTICE files being generated for jar files is not up to the  
currently-understood-standard for NOTICE files:


// --
// NOTICE file corresponding to the section 4d of The Apache License,
// Version 2.0, in this case for Genesis Configuration :: Geronimo  
Skin

// --

Genesis Configuration :: Geronimo Skin
Copyright 2003-2008 Apache Software Foundation

In particular, the prolog needs to go... geronimo/genesis/trunk/ 
NOTICE looks good (assuming that I'm up to date in my  
understanding...). Would be best if all the notices looked like  
that, I think...


I scanned the source and didn't see any problems...


I'm not sure where that came from I'm not building a genesis  
skin (although I might by the time I release).  The currently  
generated notices look like this:



Java Authentication SPI for Containers
Copyright 2003-2009 The Apache Software Foundation

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).


Does that look OK?


Yes, it does. Wonder if I had some old files sitting around. I might  
not have "cleaned" before building... I'll give it a try.


--kevan

Re: Impending votes

[David Jencks]

On Jun 8, 2009, at 11:54 AM, Kevan Miller wrote:



On Jun 8, 2009, at 2:58 AM, David Jencks wrote:

I've been playing around with genesis to get it releasable and the  
jaspi spec jar.  Jetty needs the latter for their incipient IP  
review so we need to get it out quickly.


It looks like the site plugin is totally broken http://jira.codehaus.org/browse/MSITE-395 
 so I'll beat my head against that wall for only a few more minutes  
before giving up on having maven generated sites for multip module  
projects.  AFAICT the apache-release profile is working OK.


If anyone wants to take a look at this now's the time.  I plan to  
tag and call a vote tomorrow (monday).


There's one snapshot in genesis I still need to fix, the assembly  
plugin source-release descriptor.


David,
The NOTICE files being generated for jar files is not up to the  
currently-understood-standard for NOTICE files:


// --
// NOTICE file corresponding to the section 4d of The Apache License,
// Version 2.0, in this case for Genesis Configuration :: Geronimo  
Skin

// --

Genesis Configuration :: Geronimo Skin
Copyright 2003-2008 Apache Software Foundation

In particular, the prolog needs to go... geronimo/genesis/trunk/ 
NOTICE looks good (assuming that I'm up to date in my  
understanding...). Would be best if all the notices looked like  
that, I think...


I scanned the source and didn't see any problems...


I'm not sure where that came from I'm not building a genesis skin  
(although I might by the time I release).  The currently generated  
notices look like this:



Java Authentication SPI for Containers
Copyright 2003-2009 The Apache Software Foundation

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).


Does that look OK?

thanks
david jencks



--kevan

Re: unable to start the blueprint sample bundle

[Lin Sun]

I believe this is caused by the fact that config admin service is not
active yet when I attempted to start the bundleprint sample.  After I
made sure config admin is active, this error doesn't appear.

Lin


On Wed, Jun 3, 2009 at 10:41 AM, Lin Sun wrote:
> Hi,
>
> I followed the instruction in the blueprint README and everything went
> well till step 5a - start 
>
> -> start 9
> Bundle start
> [org.apache.geronimo.blueprint.container.BlueprintExtender] : Scanning
> bundle blueprint-sample for blueprint application
> [org.apache.geronimo.blueprint.container.BlueprintExtender] : Found
> blueprint application in bundle blueprint-sample with urls:
> [bundle://9.0:0/OSGI-INF/blueprint/config.xml]
> -> [org.apache.geronimo.blueprint.container.BlueprintContainerImpl] :
> Running blueprint container for bundle blueprint-sample in state
> Unknown
> [org.apache.geronimo.blueprint.container.BlueprintEventDispatcher] :
> Sending blueprint container event BlueprintEvent[type=CREATING] for
> bundle blueprint-sample
> [org.apache.geronimo.blueprint.container.BlueprintContainerImpl] :
> Running blueprint container for bundle blueprint-sample in state
> WaitForNamespaceHandlers
> [org.apache.geronimo.blueprint.ext.ExtNamespaceHandler] : Parsing
> element 
> {http://geronimo.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0}property-placeholder
> [org.apache.geronimo.blueprint.compendium.cm.CmNamespaceHandler] :
> Parsing element
> {http://www.osgi.org/xmlns/blueprint-cm/v1.0.0}managed-service-factory
> [org.apache.geronimo.blueprint.compendium.cm.CmNamespaceHandler] :
> Parsing element
> {http://www.osgi.org/xmlns/blueprint-cm/v1.0.0}property-placeholder
> [org.apache.geronimo.blueprint.compendium.cm.CmNamespaceHandler] :
> Decorating node
> {http://www.osgi.org/xmlns/blueprint-cm/v1.0.0}managed-properties
> [org.apache.geronimo.blueprint.compendium.cm.CmNamespaceHandler] :
> Decorating node
> {http://www.osgi.org/xmlns/blueprint-cm/v1.0.0}managed-properties
> [org.apache.geronimo.blueprint.compendium.cm.CmNamespaceHandler] :
> Decorating node
> {http://www.osgi.org/xmlns/blueprint-cm/v1.0.0}managed-properties
> [org.apache.geronimo.blueprint.container.BlueprintContainerImpl] :
> Running blueprint container for bundle blueprint-sample in state
> Populated
> [org.apache.geronimo.blueprint.container.BlueprintContainerImpl] :
> Tracking service references: [#recipe-81, ref, ref-list,
> blueprint.configadmin, ref2]
> [org.apache.geronimo.blueprint.container.BlueprintContainerImpl] :
> Running blueprint container for bundle blueprint-sample in state
> WaitForInitialReferences
> [org.apache.geronimo.blueprint.container.BlueprintEventDispatcher] :
> Sending blueprint container event BlueprintEvent[type=GRACE_PERIOD,
> dependencies=[(&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.osgi.service.cm.ConfigurationAdmin))]] for bundle
> blueprint-sample
>
> -> [org.apache.geronimo.blueprint.container.BlueprintContainerImpl] :
> Unable to start blueprint container for bundle blueprint-sample
> java.util.concurrent.TimeoutException
>        at 
> org.apache.geronimo.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:247)
>        at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
>        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
>        at java.util.concurrent.FutureTask.run(FutureTask.java:123)
>        at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:65)
>        at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:168)
>        at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>        at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>        at java.lang.Thread.run(Thread.java:613)
> [org.apache.geronimo.blueprint.container.BlueprintEventDispatcher] :
> Sending blueprint container event BlueprintEvent[type=FAILURE,
> dependencies=[(&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.apache.geronimo.blueprint.sample.InterfaceA)),
> (&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.apache.geronimo.blueprint.sample.Foo)),
> (&(objectClass=org.apache.geronimo.blueprint.sample.InterfaceA)),
> (&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.osgi.service.cm.ConfigurationAdmin)),
> (&(objectClass=org.apache.geronimo.blueprint.sample.InterfaceA))],
> exception=null] for bundle blueprint-sample
>
> The b

Implementing the JEE6 Web profile.

[Rick McGuire]

I've been starting to look at what might be required to implement the 
JEE6 Web Profile stack on Geronimo.  The Web Profile is a fairly small 
subset of the JEE6 definition oriented around writing web applications.  
This profile defines the minimal set of services the server must provide 
to be compliant, but additional services can also be available on the 
server without harming compliance levels.  In fact, it appears that you 
can be compliant just by implementing the full JEE stack, but that 
somewhat defeats the purpose of allowing smaller service environments to 
be created. 


The required components in the Web Profile are:

   * Servlet 3.0
   * JavaServer Pages (JSP) 2.2
   * ExpressionLanguage (EL) 2.2
   * Debugging Support for Other Languages (JSR-45) 1.0
   * Standard Tag Library for JavaServer Pages (JSTL) 1.2
   * JavaServer Faces (JSF) 2.0
   * Common Annotations for Java Platform (JSR-250) 1.1
   * Enterprise JavaBeans (EJB) 3.1 Lite
   * Java Transaction API (JTA) 1.1
   * Java Persistence API (JPA) 2.0 

Some of these components are at the same level that Geronimo currently 
uses, others are the latest levels defined in JEE6.  I've taken a first 
stab at pulling all of this together so we can get a handle on what work 
we need to do directly (e.g., creating new spec jars for the new API 
levels) and what components we might need to hunt down from other 
sources...such as a Servlet 3.0 compliant container.  The wiki page for 
this roadmap can be found here:


http://cwiki.apache.org/confluence/display/GMOxDEV/Road+map+for+JEE6+Web+Profile

This is just a first pass, if you find anything inaccurate or have 
additional information that can be added for any of these items, please 
make the updates.  The Servlet and JSP-related sections could really use 
some fleshing out.  I'm not sure I quite have a clear picture on how 
Geronimo consumes the different pieces today in all of the combinations.


I've also created a couple of Jiras for some items that we can start 
doing now to prepare for the web profile:


1)  Create an OpenJPA 2.0 plugin to allow the newer version of OpenJPA 
to be experimented with 
(https://issues.apache.org/jira/browse/GERONIMO-4680)
2)  Create a plugin group using the existing Geronimo versions of these 
components.  This will allow a non-compliant Web profile server to be 
created using the JEE5 components that would be an excellent vehicle for 
playing around with this feature set.


Rick

[jira] Created: (GERONIMO-4681) Create a plugin group that mirrors the JEE6 web profile.

[Rick McGuire (JIRA)]

Create a plugin group that mirrors the JEE6 web profile. 
-

 Key: GERONIMO-4681
 URL: https://issues.apache.org/jira/browse/GERONIMO-4681
 Project: Geronimo
  Issue Type: Wish
  Security Level: public (Regular issues)
  Components: Plugins
Reporter: Rick McGuire


The Web Profile for JEE6 is defined as containing the following JEE6 
components: 

*  Servlet 3.0
* JavaServer Pages (JSP) 2.2
* ExpressionLanguage (EL) 2.2
* Debugging Support for Other Languages (JSR-45) 1.0
* Standard Tag Library for JavaServer Pages (JSTL) 1.2
* JavaServer Faces (JSF) 2.0
* Common Annotations for Java Platform (JSR-250) 1.1
* Enterprise JavaBeans (EJB) 3.1 Lite
* Java Transaction API (JTA) 1.1
* Java Persistence API (JPA) 2.0  

Geronimo has versions of all of these, some at the equivalent level as required 
for the Web Profile, some at older levels.  A great first step toward 
implementing the Web Profile would be to create a plugin group that allowed a 
Web-profile like install to be easily created using the JEE5 levels of the 
components.  As JEE6 levels become available, additional plugins should be 
added to allow the pieces to be upgraded until we have the full stack 
available. 

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

[jira] Created: (GERONIMO-4680) Create a plugin in for OpenJPA 2.0.

[Rick McGuire (JIRA)]

Create a plugin in for OpenJPA 2.0. 


 Key: GERONIMO-4680
 URL: https://issues.apache.org/jira/browse/GERONIMO-4680
 Project: Geronimo
  Issue Type: Wish
  Security Level: public (Regular issues)
  Components: persistence
Reporter: Rick McGuire


Now that the JEE6 specifications are getting closer to reality and OpenJPA is 
getting closer to supporting the JPA 2.0 specification, we should have a plugin 
that allows OpenJPA 2.0 to replace the 1.x version so people can start kicking 
the tires on the new version.  

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

Re: Impending votes

[Kevan Miller]

On Jun 8, 2009, at 2:58 AM, David Jencks wrote:

I've been playing around with genesis to get it releasable and the  
jaspi spec jar.  Jetty needs the latter for their incipient IP  
review so we need to get it out quickly.


It looks like the site plugin is totally broken http://jira.codehaus.org/browse/MSITE-395 
 so I'll beat my head against that wall for only a few more minutes  
before giving up on having maven generated sites for multip module  
projects.  AFAICT the apache-release profile is working OK.


If anyone wants to take a look at this now's the time.  I plan to  
tag and call a vote tomorrow (monday).


There's one snapshot in genesis I still need to fix, the assembly  
plugin source-release descriptor.


David,
The NOTICE files being generated for jar files is not up to the  
currently-understood-standard for NOTICE files:


// --
// NOTICE file corresponding to the section 4d of The Apache License,
// Version 2.0, in this case for Genesis Configuration :: Geronimo Skin
// --

Genesis Configuration :: Geronimo Skin
Copyright 2003-2008 Apache Software Foundation

In particular, the prolog needs to go... geronimo/genesis/trunk/NOTICE  
looks good (assuming that I'm up to date in my understanding...).  
Would be best if all the notices looked like that, I think...


I scanned the source and didn't see any problems...

--kevan

Re: Compiling current GEP 2.2 version

[Donald Woods]

#1 and #3 should be fixed in Rev782666.

#2 is due to old 2.2-SNAPSHOT server artifacts out in the snapshot repo, 
which will require you to build [1] a local 2.2-SNAPSHOT server until 
new artifacts are published.


[1] http://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html



-Donald


Johannes Weberhofer, Weberhofer GmbH wrote:
Thank you, Donald! The mentioned issues have been resolved. Now, that I 
have completely rebuilt my local maven repo (for some other reasons), I 
get I had to manually install some jars (which I have got from the 
current Geronimo Snapshot).


This is the error-log:

Missing:
--
1) org.apache.openejb:ejb31-api-experimental:jar:3.1.1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.apache.openejb 
-DartifactId=ejb31-api-experimental -Dversion=3.1.1-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.apache.openejb 
-DartifactId=ejb31-api-experimental -Dversion=3.1.1-SNAPSHOT 
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]


  Path to dependency:
1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.2.0
2) 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT 


3) org.apache.geronimo.plugingroups:javaee5-tomcat:car:2.2-SNAPSHOT
4) org.apache.geronimo.plugingroups:framework:car:2.2-SNAPSHOT
5) org.apache.geronimo.framework:rmi-naming:car:2.2-SNAPSHOT
6) org.apache.geronimo.framework:jee-specs:car:2.2-SNAPSHOT
7) org.apache.openejb:ejb31-api-experimental:jar:3.1.1-SNAPSHOT

2) org.apache.cxf:cxf-tools-java2ws:jar:2.1.4-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.apache.cxf 
-DartifactId=cxf-tools-java2ws -Dversion=2.1.4-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.apache.cxf 
-DartifactId=cxf-tools-java2ws -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]


  Path to dependency:
1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.2.0
2) 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT 


3) org.apache.geronimo.plugingroups:javaee5-tomcat:car:2.2-SNAPSHOT
4) 
org.apache.geronimo.plugingroups:webservices-axis2:car:2.2-SNAPSHOT

5) org.apache.geronimo.configs:cxf-tools:car:2.2-SNAPSHOT
6) org.apache.geronimo.configs:cxf-jaxws-tools:car:2.2-SNAPSHOT
7) org.apache.geronimo.modules:geronimo-cxf-tools:jar:2.2-SNAPSHOT
8) org.apache.cxf:cxf-tools-java2ws:jar:2.1.4-SNAPSHOT

3) org.directwebremoting:dwr:jar:2.0.5

  Try downloading the file manually from the project website.

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


  Path to dependency:
1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.2.0
2) 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT 


3) org.apache.geronimo.plugingroups:javaee5-tomcat:car:2.2-SNAPSHOT
4) 
org.apache.geronimo.plugins:sysdb-console-tomcat:car:2.2-SNAPSHOT

5) org.directwebremoting:dwr:jar:2.0.5

--
3 required artifacts are missing.

for artifact:
  org.apache.geronimo.devtools:testsuite-eclipse:pom:2.2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  apache.incubator 
(http://people.apache.org/repo/m2-incubating-repository/),

  java.net (http://download.java.net/maven/1/),
  releases.openqa.org (http://archiva.openqa.org/repository/releases),
  geronimo-server-2.0.2 
(https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/repository/),

  apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  snapshots.openqa.org (http://archiva.openqa.org/repository/snapshots),
  codehaus-snapshots (http://snapshots.repository.codehaus.org)



When I have manually installeld the above mentioned packages the 
build-process ends with the following messages:


[INFO] 


[INFO] Building Geronimo Eclipse Plugin :: Testsuite :: Server(s)
[INFO]task-segment: [clean, install]
[INFO] 

Re: 2.2 docs index confusion?

[Jason Warner]

How often do you check?  It was my understanding that it could sometimes
take close to an hour before the wiki page was updated even though the
confluence display was updated sooner.  Is it still not updated after an
hour or two?

~Jason Warner


On Sun, Jun 7, 2009 at 10:20 PM, Ying Tang  wrote:

> Thanks, Donald.
> We notice that only URLs such as
> http://cwiki.apache.org/confluence/display/GMOxDOC22/Documentation are
> updated minutes after editing. URLs like
> http://cwiki.apache.org/GMOxDOC22/ are often out of date.
>
> Best Regards,
>
> Ying Tang
>
> 2009/6/5, Donald Woods :
> > I just triggered an export.  Unfortunately, this can only be done by a
> > Confluence Admin  Not sure why it's not happening after edits.  Have
> > you verified that the following location is updated within a couple
> > minutes after editing, which is the autoexport stagging location, before
> > the files are copied to the normal docs location?
> >   http://cwiki.apache.org/GMOxDOC22/
> >
> >
> > -Donald
> >
> >
> > Ying Tang wrote:
> >> Hi all,
> >>
> >> Can someone help trigger the export for Confluence documents
> >> periodically? Or do we need a script to build documents every day ?
> >>
> >> If possible, I may help with this task.
> >>
> >> Best Regards,
> >>
> >> Ying Tang
> >>
> >> 2009/1/5 Ying Tang  >> >
> >>
> >> Thanks, Donald.  It worked well after the autoexport.
> >> Unfortunately we found that our latest changes did not appear on
> >> that index page
> >> Maybe we have to manually trigger the autoexport from time to time?
> >>
> >>
> >>
> >>
> >> 2009/1/1 Donald Woods mailto:dwo...@apache.org
> >>
> >>
> >> I just manually ran the autoexport plugin on GMOxDOC22, so give
> >> it 1-2 hours to see if the static webpages reflect the live
> >> Confluence content...
> >>
> >>
> >> -Donald
> >>
> >>
> >> Ying Tang wrote:
> >>
> >>  >From this page  http://cwiki.apache.org/,  we were told
> >> that the index page http://cwiki.apache.org/GMOxDOC22/
> >>  was last modified on
> >> Nov 19, 2008.
> >> The index page is in fact a link to the documentation page
> >>
> >> http://cwiki.apache.org/confluence/display/GMOxDOC22/Documentation.
> >>  All changes to the documentation page after Nov 19 are not
> >> available on the index page.
> >>
> >> We guess  this index page cannot be updated by Confluence
> >> automatically,  as it is a copy on the server. Maybe someone
> >> can help trigger the build on the server,  so that  the
> >> latest  changes will take effect.
> >>
> >>
> >> 2008/12/31 chi runhua  >>   >> >>
> >>
> >>
> >>
> >>Looks like the wiki server keeps 2 copies of GMOXDOC22,
> >> changes of
> >>doc structure was not synchronized.
> >>
> >>
> >>Jeff
> >>
> >>
> >>On Wed, Dec 31, 2008 at 7:33 AM, David Jencks
> >>mailto:david_jen...@yahoo.com>
> >>  >> >> wrote:
> >>
> >>I''m confused.  Starting on
> >> http://cwiki.apache.org/GMOxDOC22/
> >>
> >>I see...
> >>
> >>#
> >>
> >>   * Custom server assemblies
> >> o Buidling,installing plugins and extracting
> >> a server
> >>from an exsiting server
> >> o Assembling a server using Maven
> >>
> >>
> >>but the link for the first line shows a sub-index
> >> that doesn't
> >>include either of the items beneath it, it has 3
> >> unrelated entries.
> >>
> >>???
> >>
> >>More seriously when I try to edit the page
> >>
> >>
> >>
> http://cwiki.apache.org/GMOxDOC22/buidlinginstalling-plugins-and-extracting-a-server-from-an-exsiting-server.html
> >> to
> >>correct the spelling I get to the page
> >>
> >>
> >> http://cwiki.apache.org/confluence/pages/editpage.action?pageId=101843
> >>which is "Assembling a server via command line"
> >>
> >>??? ??? ???
> >>
> >>thanks
> >>david jencks
> >>
> >>
> >>
> >>
> >>
> >
>

[jira] Updated: (GERONIMO-4679) many [ERROR] "The protocol for the JAR file's URL is not supported" in the build log when building geronimo on windows

[Shawn Jiang (JIRA)]

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

Shawn Jiang updated GERONIMO-4679:
--

Patch Info: [Patch Available]

> many [ERROR] "The protocol for the JAR file's URL is not supported" in  the 
> build log when building geronimo on windows
> ---
>
> Key: GERONIMO-4679
> URL: https://issues.apache.org/jira/browse/GERONIMO-4679
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: kernel
>Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4
> Environment: windows + trunk
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: G4679.patch
>
>
> When building the Geronimo from source code on windows.  There are
> many [ERROR] "The protocol for the JAR file's URL is not supported" in
> the build log like following.
> -
> [ERROR] The protocol for the JAR file's URL is not supported
> java.lang.UnsupportedOperationException: Only local file jars are
> supported jar:file:/D:/ws/gtrunck/
> server_repo/org/apache/geronimo/configs/system-database/2.2-SNAPSHOT/
> system-database-2.2-SNAPSHOT.ca
> r!/rar/tranql-connector-1.4.jar
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.cacheUrl(UrlResourceFinder.java:231)
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.rebuildClassPath(UrlResourceFinder.java
> :188)
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.addUrls(UrlResourceFinder.java:142)
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.addUrls(UrlResourceFinder.java:127)
>  
> org.apache.geronimo.kernel.classloader.JarFileClassLoader$2.run(JarFileClassLoader.java:153)
> 
> This message was thrown in  UrlResourceFinder.cacheUrl() and logged as
> ERROR in UrlResourceFinder.rebuildClassPath().
> --
>  } catch (UnsupportedOperationException ex) {
>// the protocol for the JAR file's URL is not
> supported.  This can occur when
>// the jar file is embedded in an EAR or CAR
> file.  Proceed but log the message.
>log.error("The protocol for the JAR file's URL
> is not supported", ex);
>continue;
>}
> -
> We'd better to log this as INFO or DEBUG instead of an ERROR so that the user 
> will not be mislead by a lot of ERRORs in the build log. 

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

Re: Compiling current GEP 2.2 version

[Johannes Weberhofer, Weberhofer GmbH]

Thank you, Donald! The mentioned issues have been resolved. Now, that I have 
completely rebuilt my local maven repo (for some other reasons), I get I had to 
manually install some jars (which I have got from the current Geronimo 
Snapshot).

This is the error-log:

Missing:
--
1) org.apache.openejb:ejb31-api-experimental:jar:3.1.1-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.apache.openejb 
-DartifactId=ejb31-api-experimental -Dversion=3.1.1-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.apache.openejb 
-DartifactId=ejb31-api-experimental -Dversion=3.1.1-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.2.0
2) 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT
3) org.apache.geronimo.plugingroups:javaee5-tomcat:car:2.2-SNAPSHOT
4) org.apache.geronimo.plugingroups:framework:car:2.2-SNAPSHOT
5) org.apache.geronimo.framework:rmi-naming:car:2.2-SNAPSHOT
6) org.apache.geronimo.framework:jee-specs:car:2.2-SNAPSHOT
7) org.apache.openejb:ejb31-api-experimental:jar:3.1.1-SNAPSHOT

2) org.apache.cxf:cxf-tools-java2ws:jar:2.1.4-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.apache.cxf 
-DartifactId=cxf-tools-java2ws -Dversion=2.1.4-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.apache.cxf 
-DartifactId=cxf-tools-java2ws -Dversion=2.1.4-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.2.0
2) 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT
3) org.apache.geronimo.plugingroups:javaee5-tomcat:car:2.2-SNAPSHOT
4) org.apache.geronimo.plugingroups:webservices-axis2:car:2.2-SNAPSHOT
5) org.apache.geronimo.configs:cxf-tools:car:2.2-SNAPSHOT
6) org.apache.geronimo.configs:cxf-jaxws-tools:car:2.2-SNAPSHOT
7) org.apache.geronimo.modules:geronimo-cxf-tools:jar:2.2-SNAPSHOT
8) org.apache.cxf:cxf-tools-java2ws:jar:2.1.4-SNAPSHOT

3) org.directwebremoting:dwr:jar:2.0.5

  Try downloading the file manually from the project website.

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

  Path to dependency:
1) org.apache.geronimo.devtools:testsuite-eclipse:pom:2.2.0
2) 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT
3) org.apache.geronimo.plugingroups:javaee5-tomcat:car:2.2-SNAPSHOT
4) org.apache.geronimo.plugins:sysdb-console-tomcat:car:2.2-SNAPSHOT
5) org.directwebremoting:dwr:jar:2.0.5

--
3 required artifacts are missing.

for artifact:
  org.apache.geronimo.devtools:testsuite-eclipse:pom:2.2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  apache.incubator (http://people.apache.org/repo/m2-incubating-repository/),
  java.net (http://download.java.net/maven/1/),
  releases.openqa.org (http://archiva.openqa.org/repository/releases),
  geronimo-server-2.0.2 
(https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/repository/),
  apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  snapshots.openqa.org (http://archiva.openqa.org/repository/snapshots),
  codehaus-snapshots (http://snapshots.repository.codehaus.org)



When I have manually installeld the above mentioned packages the build-process 
ends with the following messages:

[INFO] 
[INFO] Building Geronimo Eclipse Plugin :: Testsuite :: Server(s)
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean]
[INFO] Deleting file-set: /srv/project/autobuild/gep/trunk/testsuite/server 
(included: [launcher/.metadata, launcher/eclipse, launcher/results, 
launcher/server_v2.2, launcher/server_v2.1, launcher/server_v2.0, 
launcher/workspace], excluded: [])
[INFO] [buildnumber:create {executio

[jira] Updated: (GERONIMO-4679) many [ERROR] "The protocol for the JAR file's URL is not supported" in the build log when building geronimo on windows

[Shawn Jiang (JIRA)]

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

Shawn Jiang updated GERONIMO-4679:
--

Attachment: G4679.patch

Change log level from error to debug for this kind of exceptions.

> many [ERROR] "The protocol for the JAR file's URL is not supported" in  the 
> build log when building geronimo on windows
> ---
>
> Key: GERONIMO-4679
> URL: https://issues.apache.org/jira/browse/GERONIMO-4679
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: kernel
>Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4
> Environment: windows + trunk
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2
>
> Attachments: G4679.patch
>
>
> When building the Geronimo from source code on windows.  There are
> many [ERROR] "The protocol for the JAR file's URL is not supported" in
> the build log like following.
> -
> [ERROR] The protocol for the JAR file's URL is not supported
> java.lang.UnsupportedOperationException: Only local file jars are
> supported jar:file:/D:/ws/gtrunck/
> server_repo/org/apache/geronimo/configs/system-database/2.2-SNAPSHOT/
> system-database-2.2-SNAPSHOT.ca
> r!/rar/tranql-connector-1.4.jar
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.cacheUrl(UrlResourceFinder.java:231)
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.rebuildClassPath(UrlResourceFinder.java
> :188)
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.addUrls(UrlResourceFinder.java:142)
>  
> org.apache.geronimo.kernel.classloader.UrlResourceFinder.addUrls(UrlResourceFinder.java:127)
>  
> org.apache.geronimo.kernel.classloader.JarFileClassLoader$2.run(JarFileClassLoader.java:153)
> 
> This message was thrown in  UrlResourceFinder.cacheUrl() and logged as
> ERROR in UrlResourceFinder.rebuildClassPath().
> --
>  } catch (UnsupportedOperationException ex) {
>// the protocol for the JAR file's URL is not
> supported.  This can occur when
>// the jar file is embedded in an EAR or CAR
> file.  Proceed but log the message.
>log.error("The protocol for the JAR file's URL
> is not supported", ex);
>continue;
>}
> -
> We'd better to log this as INFO or DEBUG instead of an ERROR so that the user 
> will not be mislead by a lot of ERRORs in the build log. 

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

[jira] Created: (GERONIMO-4679) many [ERROR] "The protocol for the JAR file's URL is not supported" in the build log when building geronimo on windows

[Shawn Jiang (JIRA)]

many [ERROR] "The protocol for the JAR file's URL is not supported" in  the 
build log when building geronimo on windows
---

 Key: GERONIMO-4679
 URL: https://issues.apache.org/jira/browse/GERONIMO-4679
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: kernel
Affects Versions: 2.1.4, 2.1.3, 2.1.2, 2.1.1
 Environment: windows + trunk
Reporter: Shawn Jiang
Assignee: Shawn Jiang
Priority: Minor
 Fix For: 2.1.5, 2.2


When building the Geronimo from source code on windows.  There are
many [ERROR] "The protocol for the JAR file's URL is not supported" in
the build log like following.

-
[ERROR] The protocol for the JAR file's URL is not supported
java.lang.UnsupportedOperationException: Only local file jars are
supported jar:file:/D:/ws/gtrunck/
server_repo/org/apache/geronimo/configs/system-database/2.2-SNAPSHOT/
system-database-2.2-SNAPSHOT.ca
r!/rar/tranql-connector-1.4.jar

 
org.apache.geronimo.kernel.classloader.UrlResourceFinder.cacheUrl(UrlResourceFinder.java:231)

 
org.apache.geronimo.kernel.classloader.UrlResourceFinder.rebuildClassPath(UrlResourceFinder.java
:188)

 
org.apache.geronimo.kernel.classloader.UrlResourceFinder.addUrls(UrlResourceFinder.java:142)

 
org.apache.geronimo.kernel.classloader.UrlResourceFinder.addUrls(UrlResourceFinder.java:127)

 
org.apache.geronimo.kernel.classloader.JarFileClassLoader$2.run(JarFileClassLoader.java:153)




This message was thrown in  UrlResourceFinder.cacheUrl() and logged as
ERROR in UrlResourceFinder.rebuildClassPath().


--
 } catch (UnsupportedOperationException ex) {
   // the protocol for the JAR file's URL is not
supported.  This can occur when
   // the jar file is embedded in an EAR or CAR
file.  Proceed but log the message.
   log.error("The protocol for the JAR file's URL
is not supported", ex);
   continue;
   }
-

We'd better to log this as INFO or DEBUG instead of an ERROR so that the user 
will not be mislead by a lot of ERRORs in the build log. 

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

[jira] Updated: (GERONIMODEVTOOLS-577) Appclient server and client environment module ID are the same resulting in deployment error.

[viola.lu (JIRA)]

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

viola.lu updated GERONIMODEVTOOLS-577:
--

Attachment: Appclient.patch

> Appclient server and client environment module ID are the same resulting in 
> deployment error.
> -
>
> Key: GERONIMODEVTOOLS-577
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-577
> Project: Geronimo-Devtools
>  Issue Type: Bug
>  Components: eclipse-plugin
>Affects Versions: 2.1.3, 2.2.0, 2.1.4
> Environment: os:win2003
>Reporter: viola.lu
>Assignee: Tim McConnell
>Priority: Minor
> Attachments: Appclient.patch
>
>
> 1.Create an application client, and by default server and client module id in 
> deployment plan are the same , for example:
> 
> 
> default
> test
> 1.0
> car
> 
> 
> 
> 
> default
> test
> 1.0
> car
> 
> 
> 2.Deploy application client, error exists: default/test/1.0/car module 
> already exists.
> 3.And users should modify this plan manually to make server and client module 
> id are different.
> So in this patch, add "server" to server artifactid to distinguish from 
> client artifact id.

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

[jira] Created: (GERONIMODEVTOOLS-577) Appclient server and client environment module ID are the same resulting in deployment error.

[viola.lu (JIRA)]

Appclient server and client environment module ID are the same resulting in 
deployment error.
-

 Key: GERONIMODEVTOOLS-577
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-577
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.4, 2.1.3, 2.2.0
 Environment: os:win2003
Reporter: viola.lu
Assignee: Tim McConnell
Priority: Minor


1.Create an application client, and by default server and client module id in 
deployment plan are the same , for example:


default
test
1.0
car




default
test
1.0
car



2.Deploy application client, error exists: default/test/1.0/car module already 
exists.

3.And users should modify this plan manually to make server and client module 
id are different.

So in this patch, add "server" to server artifactid to distinguish from client 
artifact id.


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