[jira] [Resolved] (GERONIMO-6422) Enable usehttponly feature of tomcat in geronimo 2.1.x
[ https://issues.apache.org/jira/browse/GERONIMO-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6422. Resolution: Fixed Fix Version/s: 2.1.9 Commit the changes to 2.1-branch at rev.1459120 based on the patch from XieZhi, thanks. > Enable usehttponly feature of tomcat in geronimo 2.1.x > -- > > Key: GERONIMO-6422 > URL: https://issues.apache.org/jira/browse/GERONIMO-6422 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.1 >Reporter: xiezhi >Assignee: Ivan > Labels: patch, tomcat, usehttponly > Fix For: 2.1.9 > > Attachments: usehttponlyforgeronimo.patch > > > Geronimo 2.1.x don't have the usehttponly feature of tomcat. > In geronimo 3.0 there is a same patch for this issue. > https://issues.apache.org/jira/browse/GERONIMO-5557 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6422) Enable usehttponly feature of tomcat in geronimo 2.1.x
[ https://issues.apache.org/jira/browse/GERONIMO-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reassigned GERONIMO-6422: -- Assignee: Ivan > Enable usehttponly feature of tomcat in geronimo 2.1.x > -- > > Key: GERONIMO-6422 > URL: https://issues.apache.org/jira/browse/GERONIMO-6422 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.1 >Reporter: xiezhi >Assignee: Ivan > Labels: patch, tomcat, usehttponly > Attachments: usehttponlyforgeronimo.patch > > > Geronimo 2.1.x don't have the usehttponly feature of tomcat. > In geronimo 3.0 there is a same patch for this issue. > https://issues.apache.org/jira/browse/GERONIMO-5557 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6389) Obscuring Passwords Feature couldn't work
[ https://issues.apache.org/jira/browse/GERONIMO-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6389. Resolution: Fixed Fix Version/s: 4.0.0 3.0-beta-2 Commit the changes to 3.0 branch at rev.1459106 and trunk at rev.1459107 Thanks, Xie Zhi ! > Obscuring Passwords Feature couldn't work > - > > Key: GERONIMO-6389 > URL: https://issues.apache.org/jira/browse/GERONIMO-6389 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: crypto >Affects Versions: 3.0-beta-1 >Reporter: xiezhi >Assignee: Ivan > Fix For: 3.0-beta-2, 4.0.0 > > Attachments: ConfiguredEncryption.java.patch > > > Follow geronimo doc https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html > and Geronimo jira 6309 to use the Obscuring Passwords feature. Met the > exception below when start the server. > [] 21% 5s Loading tomcat7 > 2012-09-14 16:17:49,061 ERROR [Http11Pro > tocol] Failed to initialize end point associated with ProtocolHandler > ["http-bio-0.0.0.0-8443"] > java.io.IOException: Keystore was tampered with, or password was incorrect > at com.ibm.crypto.provider.JavaKeyStore.engineLoad(Unknown Source) > at java.security.KeyStore.load(KeyStore.java:414) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getStore(JSSESocketFactory.java:407) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeystore(JSSESocketFactory.java:306) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:565) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:505) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:449) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:169) > at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:383) > at > org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:566) > at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:417) > at > org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119) > at > org.apache.catalina.connector.Connector.initInternal(Connector.java:956) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardService.initInternal(StandardService.java:559) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.geronimo.tomcat.TomcatServerGBean.doStart(TomcatServerGBean.java:159) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:1000) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:466) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:225) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:710) > at > org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:239) > at > org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:99) > at > org.apache.geronimo.system.osgi.BootActivator$1.execute(BootActivator.java:107) > at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:68) > at > org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) > at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:32) > Caused by: java.security.UnrecoverableKeyException: Password verification > failed > ... 34 more > 2012-09-14 16:17:49,122 ERROR [StandardService] Failed to initialize > connector [Connector[HTTP/1.1-8443]] > org.apache.catalina.LifecycleException
[jira] [Assigned] (GERONIMO-6389) Obscuring Passwords Feature couldn't work
[ https://issues.apache.org/jira/browse/GERONIMO-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reassigned GERONIMO-6389: -- Assignee: Ivan (was: xiezhi) > Obscuring Passwords Feature couldn't work > - > > Key: GERONIMO-6389 > URL: https://issues.apache.org/jira/browse/GERONIMO-6389 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: crypto >Affects Versions: 3.0-beta-1 >Reporter: xiezhi >Assignee: Ivan > Attachments: ConfiguredEncryption.java.patch > > > Follow geronimo doc https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html > and Geronimo jira 6309 to use the Obscuring Passwords feature. Met the > exception below when start the server. > [] 21% 5s Loading tomcat7 > 2012-09-14 16:17:49,061 ERROR [Http11Pro > tocol] Failed to initialize end point associated with ProtocolHandler > ["http-bio-0.0.0.0-8443"] > java.io.IOException: Keystore was tampered with, or password was incorrect > at com.ibm.crypto.provider.JavaKeyStore.engineLoad(Unknown Source) > at java.security.KeyStore.load(KeyStore.java:414) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getStore(JSSESocketFactory.java:407) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeystore(JSSESocketFactory.java:306) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:565) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:505) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:449) > at > org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:169) > at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:383) > at > org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:566) > at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:417) > at > org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119) > at > org.apache.catalina.connector.Connector.initInternal(Connector.java:956) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardService.initInternal(StandardService.java:559) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.geronimo.tomcat.TomcatServerGBean.doStart(TomcatServerGBean.java:159) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:1000) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:466) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:225) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:710) > at > org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:239) > at > org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:99) > at > org.apache.geronimo.system.osgi.BootActivator$1.execute(BootActivator.java:107) > at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:68) > at > org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) > at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:32) > Caused by: java.security.UnrecoverableKeyException: Password verification > failed > ... 34 more > 2012-09-14 16:17:49,122 ERROR [StandardService] Failed to initialize > connector [Connector[HTTP/1.1-8443]] > org.apache.catalina.LifecycleException: Failed to initialize component > [Connector[HTTP/1.1-8443]] > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106) > at > org.apache.catalina.core.Stan
[jira] [Comment Edited] (GERONIMO-6138) JDBC 4 API is not supported
[
https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608100#comment-13608100
]
Moritz Hoffmann edited comment on GERONIMO-6138 at 3/20/13 8:05 PM:
Note: The tracker interprets some content as markup. Please look at the
attached patches for correct diffs.
I was able to build a custom Geronimo with JDBC 4 support for DB2. Here are the
instructions on what needs to be done.
- Checkout tranql and build it. It is available in SVN on
https://svn.codehaus.org/tranql/ra/trunk/
- This will fail as the DB2 driver is not available. Install the db2jcc4 driver
into the local maven repo using
mvn install:install-file -Dfile=${path to db2jcc4.jar} \
-DgroupId=com.ibm.db2 \
-DartifactId=db2jcc4 \
-Dversion=10.1 \
-Dpackaging=jar
mvn install:install-file -Dfile=${path to db2jcc.jar} \
-DgroupId=com.ibm.db2 \
-DartifactId=db2jcc \
-Dversion=10.1 \
-Dpackaging=jar
mvn install:install-file -Dfile=${path to db2jcc_license_cu.jar} \
-DgroupId=com.ibm.db2 \
-DartifactId=db2jcc_license_cu \
-Dversion=10.1 \
-Dpackaging=jar
- Change the tranql version to 1.8. I used the versions:set maven plug-in, set
the version to 1.8, like this:
mvn versions:set -DnewVersion=1.8
This needs to be done for tranql-connector-[db2,parent,generic].
- Tell the DB2 connector to use db2jcc4:
--- tranql-connector-db2/tranql-connector-db2-common/pom.xml(revision 862)
+++ tranql-connector-db2/tranql-connector-db2-common/pom.xml(working copy)
@@ -34,7 +34,7 @@
com.ibm.db2
-db2jcc
+db2jcc4
provided
And:
--- tranql-connector-db2/pom.xml(revision 862)
+++ tranql-connector-db2/pom.xml(working copy)
@@ -44,20 +44,20 @@
-9.5
+10.1
com.ibm.db2
-db2jcc
+db2jcc4
${db2.version}
- Try to build the generic and db2 parts and install them in the local
repository (mvn install). If a compile error occurs, then apply the following
patch:
---
tranql-connector-db2/tranql-connector-db2-common/src/main/java/org/tranql/connector/db2/XAMCF.java
(revision 862)
+++
tranql-connector-db2/tranql-connector-db2-common/src/main/java/org/tranql/connector/db2/XAMCF.java
(working copy)
@@ -54,7 +54,7 @@
public ManagedConnection createManagedConnection(Subject subject,
ConnectionRequestInfo connectionRequestInfo) throws ResourceException {
CredentialExtractor credentialExtractor = new
CredentialExtractor(subject, connectionRequestInfo, this);
-XAConnection sqlConnection = getPhysicalConnection(subject,
credentialExtractor);
+XAConnection sqlConnection =
getPhysicalConnection(credentialExtractor);
try {
ManagedXAConnection mxac = null;
if (preparedStatementCacheSize > 0) {
Try to build it again.
- Tell Geronimo to use our custom tranql 1.8 by changing some version numbers:
--- plugins/connector-1_6/pom.xml (revision 1452838)
+++ plugins/connector-1_6/pom.xml (working copy)
@@ -186,7 +186,7 @@
org.tranql
tranql-connector-db2-xa
-1.7
+1.8
rar
--- pom.xml (revision 1452838)
+++ pom.xml (working copy)
@@ -81,8 +81,8 @@
3.12
jetty8
3.1.1
-1.7
-1.7
+1.8
+1.8
2.2.3-1_1
${project.version}
- Patch Geronimo to fix one compile error:
---
plugins/connector-1_6/geronimo-connector-1_6/src/main/java/org/apache/geronimo/datasource/DataSourceService.java
(revision 1452838)
+++
plugins/connector-1_6/geronimo-connector-1_6/src/main/java/org/apache/geronimo/datasource/DataSourceService.java
(working copy)
@@ -252,9 +252,9 @@
}
@Override
-protected XAConnection getPhysicalConnection(Subject subject,
CredentialExtractor credentialExtractor)
+protected XAConnection getPhysicalConnection(CredentialExtractor
credentialExtractor)
throws ResourceException {
-XAConnection connection = super.getPhysicalConnection(subject,
credentialExtractor);
+XAConnection connection =
super.getPhysicalConnection(c
[jira] [Updated] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Moritz Hoffmann updated GERONIMO-6138: -- Attachment: geronimo.patch geronimo patch > JDBC 4 API is not supported > > > Key: GERONIMO-6138 > URL: https://issues.apache.org/jira/browse/GERONIMO-6138 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0-M1, 3.0.0 >Reporter: Arnaud MERGEY > Fix For: 3.0.1 > > Attachments: geronimo.patch, tranql.patch > > > I try to deploy an application that uses some JDBC 4 API like > java.sql.ResultSet.isClosed() > This calls fails with following error > java.lang.AbstractMethodError: > org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z > According to JEE 6 specifications, JDBC 4 API should be supported in Geronimo > 3, and it seems not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6138) JDBC 4 API is not supported
[
https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608100#comment-13608100
]
Moritz Hoffmann commented on GERONIMO-6138:
---
I was able to build a custom Geronimo with JDBC 4 support for DB2. Here are the
instructions on what needs to be done.
- Checkout tranql and build it. It is available in SVN on
https://svn.codehaus.org/tranql/ra/trunk/
- This will fail as the DB2 driver is not available. Install the db2jcc4 driver
into the local maven repo using
mvn install:install-file -Dfile=${path to db2jcc4.jar} \
-DgroupId=com.ibm.db2 \
-DartifactId=db2jcc4 \
-Dversion=10.1 \
-Dpackaging=jar
mvn install:install-file -Dfile=${path to db2jcc.jar} \
-DgroupId=com.ibm.db2 \
-DartifactId=db2jcc \
-Dversion=10.1 \
-Dpackaging=jar
mvn install:install-file -Dfile=${path to db2jcc_license_cu.jar} \
-DgroupId=com.ibm.db2 \
-DartifactId=db2jcc_license_cu \
-Dversion=10.1 \
-Dpackaging=jar
- Change the tranql version to 1.8. I used the versions:set maven plug-in, set
the version to 1.8, like this:
mvn versions:set -DnewVersion=1.8
This needs to be done for tranql-connector-[db2,parent,generic].
- Tell the DB2 connector to use db2jcc4:
--- tranql-connector-db2/tranql-connector-db2-common/pom.xml(revision 862)
+++ tranql-connector-db2/tranql-connector-db2-common/pom.xml(working copy)
@@ -34,7 +34,7 @@
com.ibm.db2
-db2jcc
+db2jcc4
provided
And:
--- tranql-connector-db2/pom.xml(revision 862)
+++ tranql-connector-db2/pom.xml(working copy)
@@ -44,20 +44,20 @@
-9.5
+10.1
com.ibm.db2
-db2jcc
+db2jcc4
${db2.version}
- Try to build the generic and db2 parts and install them in the local
repository (mvn install). If a compile error occurs, then apply the following
patch:
---
tranql-connector-db2/tranql-connector-db2-common/src/main/java/org/tranql/connector/db2/XAMCF.java
(revision 862)
+++
tranql-connector-db2/tranql-connector-db2-common/src/main/java/org/tranql/connector/db2/XAMCF.java
(working copy)
@@ -54,7 +54,7 @@
public ManagedConnection createManagedConnection(Subject subject,
ConnectionRequestInfo connectionRequestInfo) throws ResourceException {
CredentialExtractor credentialExtractor = new
CredentialExtractor(subject, connectionRequestInfo, this);
-XAConnection sqlConnection = getPhysicalConnection(subject,
credentialExtractor);
+XAConnection sqlConnection =
getPhysicalConnection(credentialExtractor);
try {
ManagedXAConnection mxac = null;
if (preparedStatementCacheSize > 0) {
Try to build it again.
- Tell Geronimo to use our custom tranql 1.8 by changing some version numbers:
--- plugins/connector-1_6/pom.xml (revision 1452838)
+++ plugins/connector-1_6/pom.xml (working copy)
@@ -186,7 +186,7 @@
org.tranql
tranql-connector-db2-xa
-1.7
+1.8
rar
--- pom.xml (revision 1452838)
+++ pom.xml (working copy)
@@ -81,8 +81,8 @@
3.12
jetty8
3.1.1
-1.7
-1.7
+1.8
+1.8
2.2.3-1_1
${project.version}
- Patch Geronimo to fix one compile error:
---
plugins/connector-1_6/geronimo-connector-1_6/src/main/java/org/apache/geronimo/datasource/DataSourceService.java
(revision 1452838)
+++
plugins/connector-1_6/geronimo-connector-1_6/src/main/java/org/apache/geronimo/datasource/DataSourceService.java
(working copy)
@@ -252,9 +252,9 @@
}
@Override
-protected XAConnection getPhysicalConnection(Subject subject,
CredentialExtractor credentialExtractor)
+protected XAConnection getPhysicalConnection(CredentialExtractor
credentialExtractor)
throws ResourceException {
-XAConnection connection = super.getPhysicalConnection(subject,
credentialExtractor);
+XAConnection connection =
super.getPhysicalConnection(credentialExtractor);
int isolationLevel = dataSourceDescription.getIsolationLevel();
if (isolationLevel != -1) {
try
[jira] [Updated] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Moritz Hoffmann updated GERONIMO-6138: -- Attachment: tranql.patch tranql patch > JDBC 4 API is not supported > > > Key: GERONIMO-6138 > URL: https://issues.apache.org/jira/browse/GERONIMO-6138 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0-M1, 3.0.0 >Reporter: Arnaud MERGEY > Fix For: 3.0.1 > > Attachments: geronimo.patch, tranql.patch > > > I try to deploy an application that uses some JDBC 4 API like > java.sql.ResultSet.isClosed() > This calls fails with following error > java.lang.AbstractMethodError: > org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z > According to JEE 6 specifications, JDBC 4 API should be supported in Geronimo > 3, and it seems not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-808) Server restarts after project is removed
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607708#comment-13607708 ] Jarek Gawor commented on GERONIMODEVTOOLS-808: -- When a (deployed) project is deleted from the workspace, Eclipse forces a publish operation on the server. Since GEP is configured with a "start server before publish" option that causes Eclipse to automatically start the server in this particular case - in order to undeploy the project from the server. It is possible for GEP to disable the "start server before publish" option and manage on its own when and how the server gets started. However, this use-case is pretty rare (and considering the changes needed for this feature) I'm marking this as a low priority issue. > Server restarts after project is removed > > > Key: GERONIMODEVTOOLS-808 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-808 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Jarek Gawor >Priority: Minor > > The server automatically starts if previously deployed project is removed > from the workspace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-808) Server restarts after project is removed
Jarek Gawor created GERONIMODEVTOOLS-808: Summary: Server restarts after project is removed Key: GERONIMODEVTOOLS-808 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-808 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Priority: Minor The server automatically starts if previously deployed project is removed from the workspace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
