[jira] Updated: (SM-1131) Redeployment fails for Geronimo integration
[ https://issues.apache.org/activemq/browse/SM-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Koehler updated SM-1131: - Attachment: geronimo-plugin.patch the patch > Redeployment fails for Geronimo integration > --- > > Key: SM-1131 > URL: https://issues.apache.org/activemq/browse/SM-1131 > Project: ServiceMix > Issue Type: Bug > Components: geronimo >Reporter: Kristian Koehler > Attachments: geronimo-plugin.patch > > > Hi > redeployments with the geronimo plugin fails for ServiceAssemblies because > the components are not deregistered from ServiceUnits. > patch attached. > Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1111) Endpoint operation information lost when routing through camel
Endpoint operation information lost when routing through camel
--
Key: SM-
URL: https://issues.apache.org/activemq/browse/SM-
Project: ServiceMix
Issue Type: Bug
Components: servicemix-camel
Reporter: Kristian Koehler
Attachments: patches.zip
Hi
I encountered problems regarding message routing to the camel service engine and
back to the jbi NMR again. The information about the ("initial") called
operation on a endpoint is lost while communicating with camel.
see also
http://www.nabble.com/Possible-Solution-to-a-camel-serviceengine-problem-or-only-a-bad-workaround---tf4645158s12049.html
IMHO there are three different strategies to solve this problem:
(thanks Guillaume pointing me to them ;-) )
* (1) DSL - API call within the RouteBuilder
It's currently not possible to do this because the JbiEndpoint doesn't have
methods to set the operation.
Sample:
--- 8< ---
String toUri = "jbi:endpoint:xxx";
Endpoint endpoint = getContext().getEndpoint(toUri);
if (endpoint instanceof JbiEndpoint) {
JbiEndpoint jbiEndpoint = (JbiEndpoint) endpoint;
//not possible
jbiEndpoint.setOperation(operation);
}
from(fromUri).to(toUri);
--- 8< ---
* (2) URI - Setting the operation within the endpoint URI.
This option specifies the operation within the given endpoint URI. It's clear
which operation should be called but you always have to define the operation
for a routing.
--- 8< ---
String toUri = "jbi:endpoint:xxx?operation=process";
from(fromUri).to(toUri);
--- 8< ---
* (3) Copying the information
This option copies the operation information from the "from-"Endpoint to the
"to-"Endpoint. This is a simple solution if you want to call the same
operation on all endpoints involved.
I think option 2 and 3 should be applied. Option 2 overrides option 3. If you
specify a direct operation information within your URI this one is used.
Kristian
ps: option 2 and 3 are available as patches within the attached file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1082) Inconsistent exception handling in ClientFactory
[ https://issues.apache.org/activemq/browse/SM-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Koehler updated SM-1082: - Attachment: servicemix-core.patch Hi Guillaume sorry for that. The attached patch includes the missing line... Kristian > Inconsistent exception handling in ClientFactory > > > Key: SM-1082 > URL: https://issues.apache.org/activemq/browse/SM-1082 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core >Reporter: Kristian Koehler > Fix For: 3.1.3, 3.2 > > Attachments: servicemix-core.patch, servicemix-core.patch > > > Hi > the org/apache/servicemix/jbi/framework/ClientFactory includes exception > handling code which is IMO not consistent. Within the start() method the > factory tries to bind itself to a jndi context. If this fails an warning is > logged. > Within the stop() the factory tries to unbind itself from jndi without > checking if its registered properly. > I attached a patch where it is checked if the bind was successful. If not the > stop method skips the unbind call. > Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1082) Inconsistent exception handling in ClientFactory
Inconsistent exception handling in ClientFactory Key: SM-1082 URL: https://issues.apache.org/activemq/browse/SM-1082 Project: ServiceMix Issue Type: Bug Components: servicemix-core Reporter: Kristian Koehler Attachments: servicemix-core.patch Hi the org/apache/servicemix/jbi/framework/ClientFactory includes exception handling code which is IMO not consistent. Within the start() method the factory tries to bind itself to a jndi context. If this fails an warning is logged. Within the stop() the factory tries to unbind itself from jndi without checking if its registered properly. I attached a patch where it is checked if the bind was successful. If not the stop method skips the unbind call. Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1037) Geronimo Plugin enhancement and bug fix
[ https://issues.apache.org/activemq/browse/SM-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Koehler updated SM-1037: - Attachment: geronimo-plugin.patch-04 This is an updated patch. The serviceMix version is changed to 3.2-SNAPSHOT. Kristian > Geronimo Plugin enhancement and bug fix > --- > > Key: SM-1037 > URL: https://issues.apache.org/activemq/browse/SM-1037 > Project: ServiceMix > Issue Type: Bug >Reporter: Kristian Koehler > Attachments: geronimo-plugin.patch, geronimo-plugin.patch, > geronimo-plugin.patch-03, geronimo-plugin.patch-04 > > > Hi > i encountered some problems with the Geronimo Plugin for ServiceMix. I > updated the version in trunk to use Geronimo 2.0.1 and "fixed a deployment > bug". > With the current version it's not possible to deploy service assemblies which > require a deployment to a service unit. > For example if you deploy JBI ODE BPEL engine package via the JBI deployment > mechanism to geronimo you are not able to deploy a service unit using this > BPEL engine. The deployment ends up in "jbi out of sync" exceptions because > the service assembly must also be deployt to the service assembly! > The attached patch fixes the Deployer and some ServiceMix Service problems. > Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1037) Geronimo Plugin enhancement and bug fix
[ https://issues.apache.org/activemq/browse/SM-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Koehler updated SM-1037: - Attachment: geronimo-plugin.patch-03 Hi this is the next version of the patch (geronimo-plugin.patch-03). Now the offline and online deployment mechanism is ready. I changed the dependency resolution for TransactionManager and ServiceMix Container and added functionality to deploy Shared Libararies. Kristian -- http://gaswerk.sourceforge.net/ > Geronimo Plugin enhancement and bug fix > --- > > Key: SM-1037 > URL: https://issues.apache.org/activemq/browse/SM-1037 > Project: ServiceMix > Issue Type: Bug >Reporter: Kristian Koehler > Attachments: geronimo-plugin.patch, geronimo-plugin.patch, > geronimo-plugin.patch-03 > > > Hi > i encountered some problems with the Geronimo Plugin for ServiceMix. I > updated the version in trunk to use Geronimo 2.0.1 and "fixed a deployment > bug". > With the current version it's not possible to deploy service assemblies which > require a deployment to a service unit. > For example if you deploy JBI ODE BPEL engine package via the JBI deployment > mechanism to geronimo you are not able to deploy a service unit using this > BPEL engine. The deployment ends up in "jbi out of sync" exceptions because > the service assembly must also be deployt to the service assembly! > The attached patch fixes the Deployer and some ServiceMix Service problems. > Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1037) Geronimo Plugin enhancement and bug fix
[ https://issues.apache.org/activemq/browse/SM-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Koehler updated SM-1037: - Attachment: geronimo-plugin.patch HI next patch for the geronimo/servicemix integration. With this patch it is possible to do "offline deployment" to Geronimo application server. Now you can create a CAR archive for your JBI Component and preconfigure your Geronimo installation with JBI support. I developed first CAR archive for servicemix-shared-lib. You can find the sample project here: https://gaswerk.svn.sourceforge.net/svnroot/gaswerk/assemblies/soa-stack/trunk/geronimo-servicemix/additional-configs/servicemix-shared-library Currently I'm working on a preconfigured Geronimo installation with JBI support. This can also be found in GASwerk subversion (assemblies/soa-stack/..). Kristian -- http://gaswerk.sourceforge.net/ > Geronimo Plugin enhancement and bug fix > --- > > Key: SM-1037 > URL: https://issues.apache.org/activemq/browse/SM-1037 > Project: ServiceMix > Issue Type: Bug >Reporter: Kristian Koehler > Attachments: geronimo-plugin.patch, geronimo-plugin.patch > > > Hi > i encountered some problems with the Geronimo Plugin for ServiceMix. I > updated the version in trunk to use Geronimo 2.0.1 and "fixed a deployment > bug". > With the current version it's not possible to deploy service assemblies which > require a deployment to a service unit. > For example if you deploy JBI ODE BPEL engine package via the JBI deployment > mechanism to geronimo you are not able to deploy a service unit using this > BPEL engine. The deployment ends up in "jbi out of sync" exceptions because > the service assembly must also be deployt to the service assembly! > The attached patch fixes the Deployer and some ServiceMix Service problems. > Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3153) Minimal assembly is missing corba spec classes
[ https://issues.apache.org/jira/browse/GERONIMO-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495230 ] Kristian Koehler commented on GERONIMO-3153: Hi I thought to "fix the problem" is way to a working assembly. Your right thats not the final solution. ;-) For test purposes I need a (up-to-date) working minimal assembly. Thought others have a same problem... ;-) Is it possible to commit the patch and comment something in G3155 that the dependency must be deleted when fixing the bug. Will you close this issue? Kristian > Minimal assembly is missing corba spec classes > -- > > Key: GERONIMO-3153 > URL: https://issues.apache.org/jira/browse/GERONIMO-3153 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Kristian Koehler > Attachments: boilderplate.patch > > > Hi > the minimal Geronimo assembly is missing dependencies to yoko classes. This > results in exceptions when deploying a simple webApp saying something like: > "Missing YOKO CORBA spec in endorsed-dir". > Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3153) Minimal assembly is missing corba spec classes
[ https://issues.apache.org/jira/browse/GERONIMO-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Koehler updated GERONIMO-3153: --- Attachment: boilderplate.patch attached patch > Minimal assembly is missing corba spec classes > -- > > Key: GERONIMO-3153 > URL: https://issues.apache.org/jira/browse/GERONIMO-3153 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Kristian Koehler > Attachments: boilderplate.patch > > > Hi > the minimal Geronimo assembly is missing dependencies to yoko classes. This > results in exceptions when deploying a simple webApp saying something like: > "Missing YOKO CORBA spec in endorsed-dir". > Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3153) Minimal assembly is missing corba spec classes
Minimal assembly is missing corba spec classes -- Key: GERONIMO-3153 URL: https://issues.apache.org/jira/browse/GERONIMO-3153 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Kristian Koehler Hi the minimal Geronimo assembly is missing dependencies to yoko classes. This results in exceptions when deploying a simple webApp saying something like: "Missing YOKO CORBA spec in endorsed-dir". Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3148) ActiveMQ Broker config is missing some dependencies
[
https://issues.apache.org/jira/browse/GERONIMO-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Koehler updated GERONIMO-3148:
---
Component/s: ActiveMQ
set the right component
> ActiveMQ Broker config is missing some dependencies
> ---
>
> Key: GERONIMO-3148
> URL: https://issues.apache.org/jira/browse/GERONIMO-3148
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
>Affects Versions: 2.0-M6
>Reporter: Kristian Koehler
> Attachments: active-mq-broker.patch
>
>
> Hi
> I tried to use an external config file for the embedded ActiveMQ broker. For
> this scenario the BrokerServiceGBeanImpl provides an attribute called
> 'brokerUri' where you can give an activemq.xml ('spring based') configuration.
> By setting this value ClassNotFound Exceptions are thrown because some spring
> and xbean libs are not configured correctly within the ActiveMQ broker
> configuration.
> The attached patch fixes the dependency problem and a smaller typo within the
> plan.xml.
> Kristian
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3148) ActiveMQ Broker config is missing some dependencies
[
https://issues.apache.org/jira/browse/GERONIMO-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Koehler updated GERONIMO-3148:
---
Attachment: active-mq-broker.patch
> ActiveMQ Broker config is missing some dependencies
> ---
>
> Key: GERONIMO-3148
> URL: https://issues.apache.org/jira/browse/GERONIMO-3148
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
>Affects Versions: 2.0-M6
>Reporter: Kristian Koehler
> Attachments: active-mq-broker.patch
>
>
> Hi
> I tried to use an external config file for the embedded ActiveMQ broker. For
> this scenario the BrokerServiceGBeanImpl provides an attribute called
> 'brokerUri' where you can give an activemq.xml ('spring based') configuration.
> By setting this value ClassNotFound Exceptions are thrown because some spring
> and xbean libs are not configured correctly within the ActiveMQ broker
> configuration.
> The attached patch fixes the dependency problem and a smaller typo within the
> plan.xml.
> Kristian
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3148) ActiveMQ Broker config is missing some dependencies
ActiveMQ Broker config is missing some dependencies
---
Key: GERONIMO-3148
URL: https://issues.apache.org/jira/browse/GERONIMO-3148
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.0-M6
Reporter: Kristian Koehler
Hi
I tried to use an external config file for the embedded ActiveMQ broker. For
this scenario the BrokerServiceGBeanImpl provides an attribute called
'brokerUri' where you can give an activemq.xml ('spring based') configuration.
By setting this value ClassNotFound Exceptions are thrown because some spring
and xbean libs are not configured correctly within the ActiveMQ broker
configuration.
The attached patch fixes the dependency problem and a smaller typo within the
plan.xml.
Kristian
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3112) WADI Clustering is missing dependency to org.apache.tomcat.juli
[ https://issues.apache.org/jira/browse/GERONIMO-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Koehler updated GERONIMO-3112: --- Attachment: dependency.patch URL: https://svn.apache.org/repos/asf/geronimo/server/trunk/configs/wadi-clustering > WADI Clustering is missing dependency to org.apache.tomcat.juli > --- > > Key: GERONIMO-3112 > URL: https://issues.apache.org/jira/browse/GERONIMO-3112 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.0-M3 >Reporter: Kristian Koehler > Attachments: dependency.patch > > > Hi > the wadi-clustering config is missing a dependency to org.apache.tomcat.juli > which causes an ClassNotFoundException when deploying a "clustering-aware" > web-application. > - > 13:15:34,949 ERROR [GBeanInstanceState] Error while starting; GBean is now in > the FAILED state: > abstractName="org.apache.geronimo.configs/wadi-clustering/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/wadi-clustering/2.0-SNAPSHOT/car,j2 > eType=GBean,name=DefaultDispatcherHolder" > java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory > at > org.apache.catalina.tribes.group.ChannelInterceptorBase.(ChannelInte > rceptorBase.java:32) > at org.codehaus.wadi.tribes.TribesCluster.(TribesCluster.java:57) > at > org.codehaus.wadi.tribes.TribesDispatcher.(TribesDispatcher.java:26) > at > org.apache.geronimo.clustering.wadi.TribesDispatcherHolder.doStart(TribesDis > patcherHolder.java:65) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance > .java:986) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanI > nstanceState.java:267) > -- > Adding the juli dependency solved the problem for me. > Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3112) WADI Clustering is missing dependency to org.apache.tomcat.juli
WADI Clustering is missing dependency to org.apache.tomcat.juli --- Key: GERONIMO-3112 URL: https://issues.apache.org/jira/browse/GERONIMO-3112 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Clustering Affects Versions: 2.0-M3 Reporter: Kristian Koehler Hi the wadi-clustering config is missing a dependency to org.apache.tomcat.juli which causes an ClassNotFoundException when deploying a "clustering-aware" web-application. - 13:15:34,949 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName="org.apache.geronimo.configs/wadi-clustering/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/wadi-clustering/2.0-SNAPSHOT/car,j2 eType=GBean,name=DefaultDispatcherHolder" java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory at org.apache.catalina.tribes.group.ChannelInterceptorBase.(ChannelInte rceptorBase.java:32) at org.codehaus.wadi.tribes.TribesCluster.(TribesCluster.java:57) at org.codehaus.wadi.tribes.TribesDispatcher.(TribesDispatcher.java:26) at org.apache.geronimo.clustering.wadi.TribesDispatcherHolder.doStart(TribesDis patcherHolder.java:65) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance .java:986) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanI nstanceState.java:267) -- Adding the juli dependency solved the problem for me. Kristian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-752) [patch] Content-Enricher Implementation
[patch] Content-Enricher Implementation --- Key: SM-752 URL: https://issues.apache.org/activemq/browse/SM-752 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Affects Versions: incubation Reporter: Kristian Koehler Attachments: patch.txt Hi this is a patch implementing the 'Content-Enricher' Pattern (http://www.enterpriseintegrationpatterns.com/DataEnricher.html). see also: http://www.nabble.com/-patch--Content-Enricher-for-ServiceMix-tf2677905s12049.html Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2228) GeronimoAsMavenServlet.java generates wrong default-repository element
[ http://issues.apache.org/jira/browse/GERONIMO-2228?page=all ] Kristian Koehler updated GERONIMO-2228: --- Attachment: diff.patch the patch > GeronimoAsMavenServlet.java generates wrong default-repository element > -- > > Key: GERONIMO-2228 > URL: http://issues.apache.org/jira/browse/GERONIMO-2228 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Plugins >Affects Versions: 1.2, 1.1, 1.1.1 >Reporter: Kristian Koehler > Attachments: diff.patch > > > The GeronimoAsMavenServlet generates a XML document which contains an element > called 'default-repository' (see > http://localhost:8080/console-standard/maven-repo/geronimo-plugins.xml). The > value of this element looks like: > --- 8< --- > ... > >HTTP/1.1://localhost:8081/console-standard/maven-repo/ > > --- 8< --- > With this issue it isn't possible to import a plugin from a Geronimo Server > running somewhere. > This should be: > --- 8< --- > ... > >http://localhost:8081/console-standard/maven-repo/ > > --- 8< --- > The attached patch resolves this issue. > Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2228) GeronimoAsMavenServlet.java generates wrong default-repository element
GeronimoAsMavenServlet.java generates wrong default-repository element -- Key: GERONIMO-2228 URL: http://issues.apache.org/jira/browse/GERONIMO-2228 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Plugins Affects Versions: 1.1, 1.1.1, 1.2 Reporter: Kristian Koehler The GeronimoAsMavenServlet generates a XML document which contains an element called 'default-repository' (see http://localhost:8080/console-standard/maven-repo/geronimo-plugins.xml). The value of this element looks like: --- 8< --- ... HTTP/1.1://localhost:8081/console-standard/maven-repo/ --- 8< --- With this issue it isn't possible to import a plugin from a Geronimo Server running somewhere. This should be: --- 8< --- ... http://localhost:8081/console-standard/maven-repo/ --- 8< --- The attached patch resolves this issue. Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2022) New printed Book available - patch for documentation page attached
[ http://issues.apache.org/jira/browse/GERONIMO-2022?page=all ] Kristian Koehler updated GERONIMO-2022: --- Attachment: book.patch sorry for the inconvenience here is the patch > New printed Book available - patch for documentation page attached > -- > > Key: GERONIMO-2022 > URL: http://issues.apache.org/jira/browse/GERONIMO-2022 > Project: Geronimo > Type: Improvement > Security: public(Regular issues) > Components: website > Versions: 1.0 > Reporter: Kristian Koehler > Assignee: Hernan Cunico > Attachments: book.patch > > Hi > we wrote a Geronimo book which is now available. Could someone please add a > link to the documentation page. ;-) > Patch attached > Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2022) New printed Book available - patch for documentation page attached
New printed Book available - patch for documentation page attached -- Key: GERONIMO-2022 URL: http://issues.apache.org/jira/browse/GERONIMO-2022 Project: Geronimo Type: Improvement Security: public (Regular issues) Components: website Versions: 1.0 Reporter: Kristian Koehler Hi we wrote a Geronimo book which is now available. Could someone please add a link to the documentation page. ;-) Patch attached Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2000) PluginInstallerGBean generates invalid geronimo-plugin.xml files
[ http://issues.apache.org/jira/browse/GERONIMO-2000?page=all ] Kristian Koehler updated GERONIMO-2000: --- Attachment: PluginInstallerGBean.java.patch the patch > PluginInstallerGBean generates invalid geronimo-plugin.xml files > > > Key: GERONIMO-2000 > URL: http://issues.apache.org/jira/browse/GERONIMO-2000 > Project: Geronimo > Type: Bug > Security: public(Regular issues) > Components: Plugins > Versions: 1.1 > Reporter: Kristian Koehler > Attachments: PluginInstallerGBean.java.patch > > When exporting a plugin via the console the PluginInstallerGBean generates an > invalid geronimo-plugin.xml file. > The GBean generates a config-id element which is not valid according to the > plugins-1.1.xsd schema. > Generated: > http://geronimo.apache.org/xml/ns/plugins-1.1";> > geronimo/activemq/1.1-SNAPSHOT/car > geronimo/activemq/1.1-SNAPSHOT/car > Please provide a description > ... > Should be > http://geronimo.apache.org/xml/ns/plugins-1.1";> > geronimo/activemq/1.1-SNAPSHOT/car > geronimo/activemq/1.1-SNAPSHOT/car > Please provide a description > ... > Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2000) PluginInstallerGBean generates invalid geronimo-plugin.xml files
PluginInstallerGBean generates invalid geronimo-plugin.xml files Key: GERONIMO-2000 URL: http://issues.apache.org/jira/browse/GERONIMO-2000 Project: Geronimo Type: Bug Security: public (Regular issues) Components: Plugins Versions: 1.1 Reporter: Kristian Koehler When exporting a plugin via the console the PluginInstallerGBean generates an invalid geronimo-plugin.xml file. The GBean generates a config-id element which is not valid according to the plugins-1.1.xsd schema. Generated: http://geronimo.apache.org/xml/ns/plugins-1.1";> geronimo/activemq/1.1-SNAPSHOT/car geronimo/activemq/1.1-SNAPSHOT/car Please provide a description ... Should be http://geronimo.apache.org/xml/ns/plugins-1.1";> geronimo/activemq/1.1-SNAPSHOT/car geronimo/activemq/1.1-SNAPSHOT/car Please provide a description ... Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1498) DriverDownloader.DriverInfo causes java.io.NotSerializableException during server shutdown
DriverDownloader.DriverInfo causes java.io.NotSerializableException during server shutdown -- Key: GERONIMO-1498 URL: http://issues.apache.org/jira/browse/GERONIMO-1498 Project: Geronimo Type: Bug Components: console Versions: 1.0 Reporter: Kristian Koehler Attachments: DriverDownloader.DriverInfo.patch Hi the DatabasePoolPortlet within the AdminConsole uses an array of DriverDownloader.DriverInfo objects to cache the result of a remote lookup for dbdriver libs. The array is added to the HTTP Session (DatabasePoolPortlet#getDriverInfo). This causes an java.io.NotSerializableException during server shutdown because this class is not serializable. To reproduce the problem go to the "Download Driver" page and shutdown the server. Patch attached. Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1498) DriverDownloader.DriverInfo causes java.io.NotSerializableException during server shutdown
[ http://issues.apache.org/jira/browse/GERONIMO-1498?page=all ] Kristian Koehler updated GERONIMO-1498: --- Attachment: DriverDownloader.DriverInfo.patch the patch > DriverDownloader.DriverInfo causes java.io.NotSerializableException during > server shutdown > -- > > Key: GERONIMO-1498 > URL: http://issues.apache.org/jira/browse/GERONIMO-1498 > Project: Geronimo > Type: Bug > Components: console > Versions: 1.0 > Reporter: Kristian Koehler > Attachments: DriverDownloader.DriverInfo.patch > > Hi > the DatabasePoolPortlet within the AdminConsole uses an array of > DriverDownloader.DriverInfo objects to cache the result of a remote lookup > for dbdriver libs. The array is added to the HTTP Session > (DatabasePoolPortlet#getDriverInfo). > This causes an java.io.NotSerializableException during server shutdown > because this class is not serializable. > To reproduce the problem go to the "Download Driver" page and shutdown the > server. > Patch attached. > Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1453) GBeanOverride throws NullPointerException when more than one reference element specified
[ http://issues.apache.org/jira/browse/GERONIMO-1453?page=all ] Kristian Koehler updated GERONIMO-1453: --- Component: core Version: 1.0 updated the affected version > GBeanOverride throws NullPointerException when more than one reference > element specified > > > Key: GERONIMO-1453 > URL: http://issues.apache.org/jira/browse/GERONIMO-1453 > Project: Geronimo > Type: Bug > Components: core > Versions: 1.0 > Reporter: Kristian Koehler > Attachments: GBeanOverride.patch > > Hi > if there are more than one reference Element for a GBean within the > config.xml file the GBeanOverride class throws a NullPointerException. > Example GBean config to add: > --- 8< --- > name="geronimo.server:J2EEApplication=null,J2EEModule=geronimo/tomcat/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=TomcatWebContainer"> > var/catalina > > > geronimo.server:J2EEApplication=null,J2EEModule=geronimo/tomcat/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=TomcatEngine > > > > geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-system/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo > > > > --- 8< --- > Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1468) FileSystemRepository#listUris() produces wrong URI array when the repository contains a malformed entry
[ http://issues.apache.org/jira/browse/GERONIMO-1468?page=all ] Kristian Koehler updated GERONIMO-1468: --- Attachment: FileSystemRepository.patch > FileSystemRepository#listUris() produces wrong URI array when the repository > contains a malformed entry > --- > > Key: GERONIMO-1468 > URL: http://issues.apache.org/jira/browse/GERONIMO-1468 > Project: Geronimo > Type: Bug > Reporter: Kristian Koehler > Attachments: FileSystemRepository.patch > > Hi > if the local repository under /repository contains files with > malformed filenames the method listURIs returns a wrong array which crashes > the AdminConsole with a NPE. This happens when in several places (e.g. Common > Libraries, Database Pools). > The attached patch fixes this issue. > Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1468) FileSystemRepository#listUris() produces wrong URI array when the repository contains a malformed entry
FileSystemRepository#listUris() produces wrong URI array when the repository contains a malformed entry --- Key: GERONIMO-1468 URL: http://issues.apache.org/jira/browse/GERONIMO-1468 Project: Geronimo Type: Bug Reporter: Kristian Koehler Hi if the local repository under /repository contains files with malformed filenames the method listURIs returns a wrong array which crashes the AdminConsole with a NPE. This happens when in several places (e.g. Common Libraries, Database Pools). The attached patch fixes this issue. Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1453) GBeanOverride throws NullPointerException when more than one reference element specified
[ http://issues.apache.org/jira/browse/GERONIMO-1453?page=all ] Kristian Koehler updated GERONIMO-1453: --- Geronimo Info: [Patch Available] > GBeanOverride throws NullPointerException when more than one reference > element specified > > > Key: GERONIMO-1453 > URL: http://issues.apache.org/jira/browse/GERONIMO-1453 > Project: Geronimo > Type: Bug > Reporter: Kristian Koehler > Attachments: GBeanOverride.patch > > Hi > if there are more than one reference Element for a GBean within the > config.xml file the GBeanOverride class throws a NullPointerException. > Example GBean config to add: > --- 8< --- > name="geronimo.server:J2EEApplication=null,J2EEModule=geronimo/tomcat/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=TomcatWebContainer"> > var/catalina > > > geronimo.server:J2EEApplication=null,J2EEModule=geronimo/tomcat/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=TomcatEngine > > > > geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-system/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo > > > > --- 8< --- > Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1453) GBeanOverride throws NullPointerException when more than one reference element specified
[ http://issues.apache.org/jira/browse/GERONIMO-1453?page=all ] Kristian Koehler updated GERONIMO-1453: --- Attachment: GBeanOverride.patch fix typo > GBeanOverride throws NullPointerException when more than one reference > element specified > > > Key: GERONIMO-1453 > URL: http://issues.apache.org/jira/browse/GERONIMO-1453 > Project: Geronimo > Type: Bug > Reporter: Kristian Koehler > Attachments: GBeanOverride.patch > > Hi > if there are more than one reference Element for a GBean within the > config.xml file the GBeanOverride class throws a NullPointerException. > Example GBean config to add: > --- 8< --- > name="geronimo.server:J2EEApplication=null,J2EEModule=geronimo/tomcat/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=TomcatWebContainer"> > var/catalina > > > geronimo.server:J2EEApplication=null,J2EEModule=geronimo/tomcat/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=TomcatEngine > > > > geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-system/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo > > > > --- 8< --- > Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1453) GBeanOverride throws NullPointerException when more than one reference element specified
GBeanOverride throws NullPointerException when more than one reference element specified Key: GERONIMO-1453 URL: http://issues.apache.org/jira/browse/GERONIMO-1453 Project: Geronimo Type: Bug Reporter: Kristian Koehler Attachments: GBeanOverride.patch Hi if there are more than one reference Element for a GBean within the config.xml file the GBeanOverride class throws a NullPointerException. Example GBean config to add: --- 8< --- var/catalina geronimo.server:J2EEApplication=null,J2EEModule=geronimo/tomcat/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=TomcatEngine geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-system/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=ServerInfo --- 8< --- Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1152) Connector portlet does not display all WebConnectors
[ http://issues.apache.org/jira/browse/GERONIMO-1152?page=all ] Kristian Koehler updated GERONIMO-1152: --- Geronimo Info: [Patch Available] set the "patch available" flag > Connector portlet does not display all WebConnectors > > > Key: GERONIMO-1152 > URL: http://issues.apache.org/jira/browse/GERONIMO-1152 > Project: Geronimo > Type: Bug > Components: console > Versions: 1.0-M5 > Environment: Win XP, Sun JDK 1.4.2_08 > Reporter: Vamsavardhana Reddy > Attachments: connector.patch > > Under WebServer management page, Connector portlet displays only jetty web > connectors and provides links to add only jetty connectors. It does not > display tomcat web connectors nor does it provide links to add tomcat > connectors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-589) Standalone war does not have a default context
[ http://issues.apache.org/jira/browse/GERONIMO-589?page=history ] Kristian Koehler updated GERONIMO-589: -- Attachment: patch.tar.gz the attached patch fixes this issue. If there is no context-root element present a default context root will be determined and set. Also the defaultPriorityClassloader element is now optional. The default value can be set via the JettyModuleBuilder plan config. Kristian > Standalone war does not have a default context > -- > > Key: GERONIMO-589 > URL: http://issues.apache.org/jira/browse/GERONIMO-589 > Project: Geronimo > Type: Bug > Components: web > Versions: 1.0-M3 > Reporter: Dain Sundstrom > Attachments: patch.tar.gz > > If I have a standalone war with the following deployment plan: > > http://geronimo.apache.org/xml/ns/web/jetty"; > configId="foo" > parentId="org/apache/geronimo/Server"> > false > > The module will deploy, but the following exception is thrown on startup: > java.lang.IllegalArgumentException: Illegal context spec:null > at > org.mortbay.http.HttpContext.canonicalContextPathSpec(HttpContext.java:241) > at org.mortbay.http.HttpContext.setContextPath(HttpContext.java:263) > at > org.mortbay.http.HttpContext$$FastClassByCGLIB$$c359e803.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanAttribute.setValue(GBeanAttribute.java:387) > at > org.apache.geronimo.gbean.runtime.GBeanAttribute.inject(GBeanAttribute.java:318) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:830) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:331) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:111) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:133) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:494) > at > org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:348) > This can be fixed by adding a context-root element to the deployment plan. > Either the context-root element should be required, or preferably set the > default context to the configuration id which is the default in the case > where you have no deployment plan. Also the context-priority-classloader > element should be optional. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-618) interop:type=NetworkService,name=RMIIIOP have to use DefaultThreadPool
[ http://issues.apache.org/jira/browse/GERONIMO-618?page=history ] Kristian Koehler updated GERONIMO-618: -- Attachment: interop.patch the patch > interop:type=NetworkService,name=RMIIIOP have to use DefaultThreadPool > -- > > Key: GERONIMO-618 > URL: http://issues.apache.org/jira/browse/GERONIMO-618 > Project: Geronimo > Type: Bug > Reporter: Kristian Koehler > Attachments: interop.patch > > Changes made within org.openejb.server.StandardServiceStackGBean (Revision > 159002) require adjustments to the interop-server-plan.xml to use the > DefaultThreadPool accordingly. patch attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-618) interop:type=NetworkService,name=RMIIIOP have to use DefaultThreadPool
interop:type=NetworkService,name=RMIIIOP have to use DefaultThreadPool -- Key: GERONIMO-618 URL: http://issues.apache.org/jira/browse/GERONIMO-618 Project: Geronimo Type: Bug Reporter: Kristian Koehler Attachments: interop.patch Changes made within org.openejb.server.StandardServiceStackGBean (Revision 159002) require adjustments to the interop-server-plan.xml to use the DefaultThreadPool accordingly. patch attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-617) Interop module is missing eclipse and intellij classpath includes
Interop module is missing eclipse and intellij classpath includes - Key: GERONIMO-617 URL: http://issues.apache.org/jira/browse/GERONIMO-617 Project: Geronimo Type: Bug Reporter: Kristian Koehler the interop module is missing "classpath entries" within the project.properties file for eclipse and intellij. Something like this should be included: maven.eclipse.classpath.include=target/src maven.idea.generated.source=src -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-616) Wrong package statement for DoubleKeyedHashMap
[ http://issues.apache.org/jira/browse/GERONIMO-616?page=history ] Kristian Koehler updated GERONIMO-616: -- Attachment: doubleKey.patch the patch > Wrong package statement for DoubleKeyedHashMap > -- > > Key: GERONIMO-616 > URL: http://issues.apache.org/jira/browse/GERONIMO-616 > Project: Geronimo > Type: Bug > Components: transaction manager > Reporter: Kristian Koehler > Attachments: doubleKey.patch > > the file DoubleKeyedHashMap.java contains a wrong package statement. > included statement: org.apache.geronimo.transaction > should be: org.apache.geronimo.transaction.context > patch attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-616) Wrong package statement for DoubleKeyedHashMap
Wrong package statement for DoubleKeyedHashMap -- Key: GERONIMO-616 URL: http://issues.apache.org/jira/browse/GERONIMO-616 Project: Geronimo Type: Bug Components: transaction manager Reporter: Kristian Koehler Attachments: doubleKey.patch the file DoubleKeyedHashMap.java contains a wrong package statement. included statement: org.apache.geronimo.transaction should be: org.apache.geronimo.transaction.context patch attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-521) [PATCH] Maven Plugin is missing dependency to geronimo-common module
[ http://nagoya.apache.org/jira/browse/GERONIMO-521?page=history ] Kristian Koehler updated GERONIMO-521: -- Attachment: missing-dependency.txt patch > [PATCH] Maven Plugin is missing dependency to geronimo-common module > > > Key: GERONIMO-521 > URL: http://nagoya.apache.org/jira/browse/GERONIMO-521 > Project: Apache Geronimo > Type: Bug > Components: deployment > Versions: 1.0-M4 > Reporter: Kristian Koehler > Attachments: missing-dependency.txt > > Hi > by moving the DeploymentException class to the common module the maven-plugin > also needs a dependency to the common module. Patch attached. > Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-521) [PATCH] Maven Plugin is missing dependency to geronimo-common module
[PATCH] Maven Plugin is missing dependency to geronimo-common module Key: GERONIMO-521 URL: http://nagoya.apache.org/jira/browse/GERONIMO-521 Project: Apache Geronimo Type: Bug Components: deployment Versions: 1.0-M4 Reporter: Kristian Koehler Attachments: missing-dependency.txt Hi by moving the DeploymentException class to the common module the maven-plugin also needs a dependency to the common module. Patch attached. Kristian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
