[jira] Updated: (GERONIMO-3960) Make the spec jars OSGi friendly
[
https://issues.apache.org/jira/browse/GERONIMO-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-3960:
--
Attachment: GERONIMO-3960.diff
Most of the work on this issue has already been done -- all the spec jars now
have the OSGi metadata.
There's only one remaining problem with the jars when using them in an OSGi
environment: they all import the packages they export. E.g. the EL 1.0 bundle
exports javax.el;version="1.0" but it also imports javax.el;version="1.0"
While this is a fine configuration for some bundles, there's no good reason for
the specs bundles to import their own packages. On top of that, the import
doesn't have an upper limit set on the version imported, which means that if
you install EL 2.2 in the same OSGi framewok instance as the EL 1.0 spec
mentioned before, it's perfectly possible that the import on the latter will
resolve to the packages exported by the former version (because 2.2 >= 1.0)
Attaching a patch that removes these imports by adding the
*{{-noimport:=true}}* flag to the Export-Packages configuration
> Make the spec jars OSGi friendly
>
>
> Key: GERONIMO-3960
> URL: https://issues.apache.org/jira/browse/GERONIMO-3960
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Guillaume Nodet
> Attachments: GERONIMO-3960.diff, stax-osgi.diff
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
[
https://issues.apache.org/jira/browse/GERONIMO-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-4727:
--
Attachment: GERONIMO-4727.diff
> Setting a parameterized pojo in blueprint throws exception
> --
>
> Key: GERONIMO-4727
> URL: https://issues.apache.org/jira/browse/GERONIMO-4727
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Reporter: Gert Vanthienen
> Attachments: GERONIMO-4727.diff, GERONIMO-4727.diff
>
>
> When the setter of property uses a parameterized type (e.g.
> *{{setLruList(LruList events)}}*) and the bean being
> injected is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
> {noformat}
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> Unable to convert property value from
> org.apache.felix.karaf.gshell.log.LruList to
> org.apache.felix.karaf.gshell.log.LruList
> for injection
> public void
> org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
> at
> org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
> at
> org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
> at
> org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
> ...
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
[
https://issues.apache.org/jira/browse/GERONIMO-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-4727:
--
Attachment: GERONIMO-4727.diff
This patch will give the raw type 'the benefit of the doubt' during type
conversion before invoking the setter.
> Setting a parameterized pojo in blueprint throws exception
> --
>
> Key: GERONIMO-4727
> URL: https://issues.apache.org/jira/browse/GERONIMO-4727
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Reporter: Gert Vanthienen
> Attachments: GERONIMO-4727.diff
>
>
> When the setter of property uses a parameterized type (e.g.
> *{{setLruList(LruList events)}}*) and the bean being
> injected is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
> {noformat}
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> Unable to convert property value from
> org.apache.felix.karaf.gshell.log.LruList to
> org.apache.felix.karaf.gshell.log.LruList
> for injection
> public void
> org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
> at
> org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
> at
> org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
> at
> org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
> at
> org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
> ...
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
Setting a parameterized pojo in blueprint throws exception
--
Key: GERONIMO-4727
URL: https://issues.apache.org/jira/browse/GERONIMO-4727
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Reporter: Gert Vanthienen
When the setter of property uses a parameterized type (e.g.
*{{setLruList(LruList events)}}*) and the bean being injected
is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException:
Unable to convert property value from org.apache.felix.karaf.gshell.log.LruList
to
org.apache.felix.karaf.gshell.log.LruList
for injection
public void
org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
at
org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1119) Encoding problem in text returned by HTTP-SU
[ https://issues.apache.org/activemq/browse/SM-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40588 ] Gert Vanthienen commented on SM-1119: - Right you are! Although every message will be re-encoded by the SourceTransformer, I wrongfully assumed that it would always encode the response in UTF-8, while in reality this can be configured through the 'org.apache.servicemix.default.charset' system property. Thanks for reviewing the code so carefully! http://svn.apache.org/viewvc?view=rev&revision=594255 (3.1 branch) http://svn.apache.org/viewvc?view=rev&revision=594267 (3.2 branch) http://svn.apache.org/viewvc?view=rev&revision=594259 (3.3 -- trunk) > Encoding problem in text returned by HTTP-SU > > > Key: SM-1119 > URL: https://issues.apache.org/activemq/browse/SM-1119 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core, servicemix-http, servicemix-jsr181 >Affects Versions: 3.1, 3.1.1, 3.1.2 > Environment: This issue can be reproduced on Windows XP Pro and Red > Hat Linux. >Reporter: Philip Webster > Fix For: 3.1.3, 3.2.1, 3.3 > > Attachments: multimatch-search.zip, multimatch-search2.zip, > SM-1119.patch, wsdl-first-sa-3.2-SNAPSHOT.jar > > > It looks as though there is an encoding problem at the point after the > results are returned from the JSR181 service unit. > The issue can be reproduced on 3.1, 3.1.1, 3.1.2 and the October 25th > snapshot of 3.2 > As discussed on this thread: > http://www.nabble.com/Encoding-problem-in-text-returned-by-HTTP-SU-tf4676140s12049r3.html > The attached service usints and service assembly can be used to reproduce the > issue. > Use the following input against http://localhost:8492/MultiMatchSearch/ > http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:sear="http://eir.multimatch.org/search";> > > > > > >Charles Perrault >Title >~ > > SPANISH > ENGLISH > nonCached > metadata > >TEXT >0 >1 > > > false > > > > The result is: > http://schemas.xmlsoap.org/soap/envelope/";> > > http://eir.multimatch.org/search";> > > > > urn://org.multimatch/search/result/1193668323010 >MeñiquÃn Charles Perrault ; traducción de Teodoro > Baró >http://www.google.com/ > > > > > > The result should be: > http://schemas.xmlsoap.org/soap/envelope/";> > > http://eir.multimatch.org/search";> > > > > urn://org.multimatch/search/result/1193668323010 >Meñiquín Charles Perrault ; traducción de Teodoro > Baró >http://www.google.com/ > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1119) Encoding problem in text returned by HTTP-SU
[ https://issues.apache.org/activemq/browse/SM-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1119. - Resolution: Fixed Fix Version/s: 3.3 3.2.1 3.1.3 Thank you, Philip, for providing the necessary test SAs to verify this fix! Adding "charset=utf-8" to the content type fixes the issue: http://svn.apache.org/viewvc?view=rev&revision=594063 (3.1 branch) http://svn.apache.org/viewvc?view=rev&revision=594078 (3.2 branch) http://svn.apache.org/viewvc?view=rev&revision=594064 (3.3 -- trunk) > Encoding problem in text returned by HTTP-SU > > > Key: SM-1119 > URL: https://issues.apache.org/activemq/browse/SM-1119 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-core, servicemix-http, servicemix-jsr181 >Affects Versions: 3.1, 3.1.1, 3.1.2 > Environment: This issue can be reproduced on Windows XP Pro and Red > Hat Linux. >Reporter: Philip Webster > Fix For: 3.1.3, 3.2.1, 3.3 > > Attachments: multimatch-search.zip, multimatch-search2.zip, > SM-1119.patch, wsdl-first-sa-3.2-SNAPSHOT.jar > > > It looks as though there is an encoding problem at the point after the > results are returned from the JSR181 service unit. > The issue can be reproduced on 3.1, 3.1.1, 3.1.2 and the October 25th > snapshot of 3.2 > As discussed on this thread: > http://www.nabble.com/Encoding-problem-in-text-returned-by-HTTP-SU-tf4676140s12049r3.html > The attached service usints and service assembly can be used to reproduce the > issue. > Use the following input against http://localhost:8492/MultiMatchSearch/ > http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:sear="http://eir.multimatch.org/search";> > > > > > >Charles Perrault >Title >~ > > SPANISH > ENGLISH > nonCached > metadata > >TEXT >0 >1 > > > false > > > > The result is: > http://schemas.xmlsoap.org/soap/envelope/";> > > http://eir.multimatch.org/search";> > > > > urn://org.multimatch/search/result/1193668323010 >MeñiquÃn Charles Perrault ; traducción de Teodoro > Baró >http://www.google.com/ > > > > > > The result should be: > http://schemas.xmlsoap.org/soap/envelope/";> > > http://eir.multimatch.org/search";> > > > > urn://org.multimatch/search/result/1193668323010 >Meñiquín Charles Perrault ; traducción de Teodoro > Baró >http://www.google.com/ > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1124) Message content silently dropped when conversion fails
[ https://issues.apache.org/activemq/browse/SM-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1124. - Resolution: Fixed Fix Version/s: (was: 3.2) 3.2.1 Added warning when message content conversions fails + use Camel type converter for String→Source http://svn.apache.org/viewvc?view=rev&revision=591300 > Message content silently dropped when conversion fails > -- > > Key: SM-1124 > URL: https://issues.apache.org/activemq/browse/SM-1124 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-camel >Reporter: Gert Vanthienen >Priority: Trivial > Fix For: 3.2.1 > > > When a Camel message is sent to a JBI endpoint, the contents is converted > into a Source (for message normalization). When the message content can not > be transformed, it is dropped without any warning whatsoever. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1124) Message content silently dropped when conversion fails
Message content silently dropped when conversion fails -- Key: SM-1124 URL: https://issues.apache.org/activemq/browse/SM-1124 Project: ServiceMix Issue Type: Bug Components: servicemix-camel Reporter: Gert Vanthienen Priority: Trivial Fix For: 3.2 When a Camel message is sent to a JBI endpoint, the contents is converted into a Source (for message normalization). When the message content can not be transformed, it is dropped without any warning whatsoever. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-1103) Class not found (org.apache.camel.Component) while starting servicemix-camel component
[
https://issues.apache.org/activemq/browse/SM-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen closed SM-1103.
---
Resolution: Cannot Reproduce
Never mind... I guess everyone is entitled to a moment of confusion once in a
while...
> Class not found (org.apache.camel.Component) while starting servicemix-camel
> component
> --
>
> Key: SM-1103
> URL: https://issues.apache.org/activemq/browse/SM-1103
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-camel
>Affects Versions: 3.2
>Reporter: Gert Vanthienen
>
> servicemix-camel fails with new build from trunk (revision 584233)
> {code}
> ERROR - InstallerMBeanImpl - Class not found:
> org.apache.servicemix.common.DefaultBootstrap
> java.lang.NoClassDefFoundError: org/apache/camel/Component
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
> at
> org.apache.xbean.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:48)
> at
> org.apache.xbean.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:272)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.xbean.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:224)
> at
> org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:200)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> at
> org.apache.servicemix.jbi.framework.InstallerMBeanImpl.activateComponent(InstallerMBeanImpl.java:186)
> at
> org.apache.servicemix.jbi.framework.InstallerMBeanImpl.install(InstallerMBeanImpl.java:165)
> at
> org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService.java:326)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.checkPendingComponents(AutoDeploymentService.java:515)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateSharedLibrary(AutoDeploymentService.java:314)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:251)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:647)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$2(AutoDeploymentService.java:623)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:611)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1103) Class not found (org.apache.camel.Component) while starting servicemix-camel component
Class not found (org.apache.camel.Component) while starting servicemix-camel
component
--
Key: SM-1103
URL: https://issues.apache.org/activemq/browse/SM-1103
Project: ServiceMix
Issue Type: Bug
Components: servicemix-camel
Affects Versions: 3.2
Reporter: Gert Vanthienen
servicemix-camel fails with new build from trunk (revision 584233)
{code}
ERROR - InstallerMBeanImpl - Class not found:
org.apache.servicemix.common.DefaultBootstrap
java.lang.NoClassDefFoundError: org/apache/camel/Component
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at
org.apache.xbean.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java:48)
at
org.apache.xbean.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:272)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.xbean.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:224)
at
org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:200)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.apache.servicemix.jbi.framework.InstallerMBeanImpl.activateComponent(InstallerMBeanImpl.java:186)
at
org.apache.servicemix.jbi.framework.InstallerMBeanImpl.install(InstallerMBeanImpl.java:165)
at
org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService.java:326)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.checkPendingComponents(AutoDeploymentService.java:515)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateSharedLibrary(AutoDeploymentService.java:314)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:251)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:647)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$2(AutoDeploymentService.java:623)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:611)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1098) Loop in StAX ElementReader while executing web service
Loop in StAX ElementReader while executing web service -- Key: SM-1098 URL: https://issues.apache.org/activemq/browse/SM-1098 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-jsr181 Affects Versions: 3.1.2 Reporter: Gert Vanthienen Attachments: Webservice-test.zip Cfr. mailing list http://www.nabble.com/Webservice-call-failes-when-log4j-level-is-set-to-DEBUG.-tf4575623s12049.html#a13096235 The user already provided us with an example of a failing SA -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1071) Provisioning system
[ https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40159 ] Gert Vanthienen commented on SM-1071: - Another option could be to use JCR for storing/versioning/accessing the configuration... > Provisioning system > --- > > Key: SM-1071 > URL: https://issues.apache.org/activemq/browse/SM-1071 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet > Fix For: 4.0 > > > Maybe using OBR > (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or > Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). > Basically, i'm thinking about two things: > * leverage OBR to install features easily (activemq, ode, cxf, etc...) > * dynamic / automatic provisioning of applications > For the second one, a service could pull an HTTP url from time to time to > check is a new configuration for itself is available. if yes, download it > and uninstall stop / uninstall unneeded bundes, install new ones, etc... > The configuration would be a simple xml defining which bundles / version > should be started -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1056) Add NamespaceContextImpl to servicemix-core
Add NamespaceContextImpl to servicemix-core --- Key: SM-1056 URL: https://issues.apache.org/activemq/browse/SM-1056 Project: ServiceMix Issue Type: Improvement Components: servicemix-core, servicemix-drools, servicemix-eip Affects Versions: 3.1.1 Reporter: Gert Vanthienen Assignee: Gert Vanthienen Currently, servicemix-eip and servicemix-drools each ship with an almost identical copy of NamespaceContextImpl. It would be better to move this to servicemix-core (where the XPathExpression classes are -- which might also require a NamespaceContextImpl). In order not to break any existing xbean.xml files, we should keep the current classes in servicemix-eip and servicemix-drools (can become empty, simply inherit from the core one) to make sure that eip:namespace-context and drools:namespace-context still exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1042) Build fails in Java 6: Cannot find symbol StandardMBean(Object, Class)
Build fails in Java 6: Cannot find symbol StandardMBean(Object, Class)
-
Key: SM-1042
URL: https://issues.apache.org/activemq/browse/SM-1042
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.1.1
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Seems to be a problem that is mentioned in the adoption guide:
http://java.sun.com/javase/6/webnotes/adoption/adoptionguide.html#2.2.1
{noformat}
[INFO] Compilation failure
C:\projects\servicemix\core\servicemix-core\src\main\java\org\apache\servicemix\jbi\management\BaseStandardMBean.java:[117,8]
cannot
find symbol
symbol : constructor
StandardMBean(java.lang.Object,java.lang.Class)
location: class javax.management.StandardMBean
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SM-989) Backup File before Delete
[ https://issues.apache.org/activemq/browse/SM-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen closed SM-989. -- Resolution: Duplicate Fix Version/s: 3.2 Duplicate of SM-990 > Backup File before Delete > - > > Key: SM-989 > URL: https://issues.apache.org/activemq/browse/SM-989 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-file >Affects Versions: 3.2 >Reporter: Gordon Dickens >Priority: Minor > Fix For: 3.2 > > > Provide backup directory option to copy file to before deleting. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1014) WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null
[ https://issues.apache.org/activemq/browse/SM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-1014. - Resolution: Fixed Assignee: Gert Vanthienen Added a default value for defaultMep to SoapEndpoint http://svn.apache.org/viewvc?view=rev&revision=562344 http://svn.apache.org/viewvc?view=rev&revision=562351 > WSDL-first example fails javax.jbi.messaging.MessagingException: Do not > understand pattern: null > > > Key: SM-1014 > URL: https://issues.apache.org/activemq/browse/SM-1014 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-http, servicemix-soap >Affects Versions: 3.1.1 >Reporter: Gert Vanthienen >Assignee: Gert Vanthienen >Priority: Minor > Fix For: 3.1.2, 3.2 > > > The exception can be solved by specifying defaultMep on the HTTP consumer > endpoint, but I suppose it would be better to have a good default value for > the MEP (In-Out?) on the endpoint instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1014) WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null
WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null Key: SM-1014 URL: https://issues.apache.org/activemq/browse/SM-1014 Project: ServiceMix Issue Type: Bug Components: servicemix-http, servicemix-soap Affects Versions: 3.1.1 Reporter: Gert Vanthienen Priority: Minor Fix For: 3.1.2, 3.2 The exception can be solved by specifying defaultMep on the HTTP consumer endpoint, but I suppose it would be better to have a good default value for the MEP (In-Out?) on the endpoint instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1005) File BC doesnt set correlation Id and sender property
[ https://issues.apache.org/activemq/browse/SM-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39794 ] Gert Vanthienen commented on SM-1005: - On my machine, the message exchanges sent by the file binding component already contain these properties. Perhaps you're still using the 3.1 version, SM-861 fixes this in 3.1.1 for exchanges that are sent using sendSync() (such as those sent by the FilePoller) > File BC doesnt set correlation Id and sender property > - > > Key: SM-1005 > URL: https://issues.apache.org/activemq/browse/SM-1005 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-file >Affects Versions: 3.1, 3.1.1 >Reporter: Gianfranco Boccalon > > The File binding component doesn't set the properties correlation id and > sender. > We fixed the problem changing the method processFile in class > org.apache.servicemix.file.FilePollerEndpoint, adding these rows before > sending the message (sendSync): >exchange.setProperty(JbiConstants.SENDER_ENDPOINT, service.toString()); >exchange.setProperty(JbiConstants.CORRELATION_ID, > exchange.getExchangeId()); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1005) File BC doesnt set correlation Id and sender property
[ https://issues.apache.org/activemq/browse/SM-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39768 ] Gert Vanthienen commented on SM-1005: - Gianfranco, I haven't tested the 3.1 release, but at least the 3.1.1 release already does this correctly. Can you describe the problem you were having with this? Gert > File BC doesnt set correlation Id and sender property > - > > Key: SM-1005 > URL: https://issues.apache.org/activemq/browse/SM-1005 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-file >Affects Versions: 3.1, 3.1.1 >Reporter: Gianfranco Boccalon > > The File binding component doesn't set the properties correlation id and > sender. > We fixed the problem changing the method processFile in class > org.apache.servicemix.file.FilePollerEndpoint, adding these rows before > sending the message (sendSync): >exchange.setProperty(JbiConstants.SENDER_ENDPOINT, service.toString()); >exchange.setProperty(JbiConstants.CORRELATION_ID, > exchange.getExchangeId()); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-664) org.apache.servicemix.http.HttpAddressingTest (Hangs)
[ https://issues.apache.org/activemq/browse/SM-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-664. Resolution: Cannot Reproduce Because I was unable to reproduce this while going through the binding components for issue SM-623, I removed the exclusion from the test suite. We can always reopen the issue if someone can reproduce it... http://svn.apache.org/viewvc?view=rev&revision=557757 > org.apache.servicemix.http.HttpAddressingTest (Hangs) > - > > Key: SM-664 > URL: https://issues.apache.org/activemq/browse/SM-664 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-http >Affects Versions: incubation >Reporter: Fritz Oconer > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-653) org.apache.servicemix.eip.WireTapJmsFlowTest
[ https://issues.apache.org/activemq/browse/SM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-653: --- Fix Version/s: 3.2 > org.apache.servicemix.eip.WireTapJmsFlowTest > > > Key: SM-653 > URL: https://issues.apache.org/activemq/browse/SM-653 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-663) org.apache.servicemix.eip.ContentBasedRouterTxTest
[ https://issues.apache.org/activemq/browse/SM-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-663. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.ContentBasedRouterTxTest > -- > > Key: SM-663 > URL: https://issues.apache.org/activemq/browse/SM-663 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-662) org.apache.servicemix.eip.SpringConfigurationTest
[ https://issues.apache.org/activemq/browse/SM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-662. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.SpringConfigurationTest > - > > Key: SM-662 > URL: https://issues.apache.org/activemq/browse/SM-662 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-660) org.apache.servicemix.eip.DeploymentTest
[ https://issues.apache.org/activemq/browse/SM-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-660. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.DeploymentTest > > > Key: SM-660 > URL: https://issues.apache.org/activemq/browse/SM-660 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-661) org.apache.servicemix.eip.support.NamespaceContextImplTest
[ https://issues.apache.org/activemq/browse/SM-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-661. Resolution: Fixed Fix Version/s: 3.2 > org.apache.servicemix.eip.support.NamespaceContextImplTest > -- > > Key: SM-661 > URL: https://issues.apache.org/activemq/browse/SM-661 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-659) org.apache.servicemix.eip.XPathSplitterTxTest
[ https://issues.apache.org/activemq/browse/SM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-659. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.XPathSplitterTxTest > - > > Key: SM-659 > URL: https://issues.apache.org/activemq/browse/SM-659 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-658) org.apache.servicemix.eip.WireTapTxTest
[ https://issues.apache.org/activemq/browse/SM-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-658: --- Fix Version/s: 3.2 > org.apache.servicemix.eip.WireTapTxTest > --- > > Key: SM-658 > URL: https://issues.apache.org/activemq/browse/SM-658 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-658) org.apache.servicemix.eip.WireTapTxTest
[ https://issues.apache.org/activemq/browse/SM-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-658. Resolution: Fixed Cfr. explanation on SM-623 > org.apache.servicemix.eip.WireTapTxTest > --- > > Key: SM-658 > URL: https://issues.apache.org/activemq/browse/SM-658 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-657) org.apache.servicemix.eip.MessageFilterTxTest
[ https://issues.apache.org/activemq/browse/SM-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-657. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.MessageFilterTxTest > - > > Key: SM-657 > URL: https://issues.apache.org/activemq/browse/SM-657 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-656) org.apache.servicemix.eip.StaticRecipientListTxTest
[ https://issues.apache.org/activemq/browse/SM-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-656. Resolution: Fixed Cfr. explanation on SM-623 > org.apache.servicemix.eip.StaticRecipientListTxTest > --- > > Key: SM-656 > URL: https://issues.apache.org/activemq/browse/SM-656 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-655) org.apache.servicemix.eip.SplitAggregatorTxTest
[ https://issues.apache.org/activemq/browse/SM-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-655. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.SplitAggregatorTxTest > --- > > Key: SM-655 > URL: https://issues.apache.org/activemq/browse/SM-655 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-654) org.apache.servicemix.eip.PipelineTxTest
[ https://issues.apache.org/activemq/browse/SM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-654. Resolution: Fixed Cfr. explanation on SM-623 > org.apache.servicemix.eip.PipelineTxTest > > > Key: SM-654 > URL: https://issues.apache.org/activemq/browse/SM-654 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-654) org.apache.servicemix.eip.PipelineTxTest
[ https://issues.apache.org/activemq/browse/SM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-654: --- Fix Version/s: 3.2 > org.apache.servicemix.eip.PipelineTxTest > > > Key: SM-654 > URL: https://issues.apache.org/activemq/browse/SM-654 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-653) org.apache.servicemix.eip.WireTapJmsFlowTest
[ https://issues.apache.org/activemq/browse/SM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-653. Resolution: Fixed Cfr. explanation on SM-623 > org.apache.servicemix.eip.WireTapJmsFlowTest > > > Key: SM-653 > URL: https://issues.apache.org/activemq/browse/SM-653 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-652) org.apache.servicemix.eip.StaticRoutingSlipTxTest
[ https://issues.apache.org/activemq/browse/SM-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved SM-652. Resolution: Fixed Fix Version/s: 3.2 Cfr. explanation on SM-623 > org.apache.servicemix.eip.StaticRoutingSlipTxTest > - > > Key: SM-652 > URL: https://issues.apache.org/activemq/browse/SM-652 > Project: ServiceMix > Issue Type: Sub-task > Components: servicemix-eip >Affects Versions: incubation >Reporter: Fritz Oconer > Fix For: 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-623) Unit test that fails when building using maven2.
[ https://issues.apache.org/activemq/browse/SM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39662 ] Gert Vanthienen commented on SM-623: It appears the servicemix-eip tests were failing when no additional memory was reserved for the unit tests (currently: -Xmx512m). With Adrian's centralized surefire configuration in place, all these tests now work fine. I have removed the s from the pom.xml (cfr. http://svn.apache.org/viewvc?view=rev&revision=555652) > Unit test that fails when building using maven2. > > > Key: SM-623 > URL: https://issues.apache.org/activemq/browse/SM-623 > Project: ServiceMix > Issue Type: Test >Reporter: Fritz Oconer > > Check the sub tasks. These are unit tests that fails when building using > maven 2 and jdk1.5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1000) ServiceMix :: Maven2 JBI Plugin checkstyle issues
[
https://issues.apache.org/activemq/browse/SM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39657
]
Gert Vanthienen commented on SM-1000:
-
Rabi,
Was this a checkout from trunk? I cannot reproduce the CheckStyle errors with
my latest checkout here. Could you try to do an 'svn up' and retry it?
Gert
> ServiceMix :: Maven2 JBI Plugin checkstyle issues
> --
>
> Key: SM-1000
> URL: https://issues.apache.org/activemq/browse/SM-1000
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
>Affects Versions: 3.2
> Environment: Windows
>Reporter: Rabi
>
> [INFO] Building ServiceMix :: Maven2 JBI Plugin
> [INFO]task-segment: [install]
> [INFO]
> -
> ---
> [INFO] Ignoring available plugin update: 2.3 as it requires Maven version
> 2.0.5
> [INFO] [checkstyle:checkstyle {execution: validate}]
> [INFO] Starting audit...
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:58:37: More than
> 7 p
> arameters.
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\GraphArtifactCollector.java:96:18: More than
> 7 p
> arameters.
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37: method
> def
> modifier at indentation level 2 not at correct indentation, 4
> E:\Rabi\work\workspace\servicemix\tooling\jbi-maven-plugin\src\main\java\org\apa
> che\servicemix\maven\plugin\jbi\JbiComponentDescriptorWriter.java:37:15: More
> th
> an 7 parameters.
> Audit done.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An error has occurred in Checkstyle report generation.
> Embedded error: There are 4 checkstyle errors.
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 28 seconds
> [INFO] Finished at: Wed Jul 11 16:34:15 IST 2007
> [INFO] Final Memory: 13M/24M
> [INFO]
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-997) Basic example fails to build: InvalidProjectModelException
[
https://issues.apache.org/activemq/browse/SM-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39643
]
Gert Vanthienen commented on SM-997:
The file at
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
doesn't match the pom.xml that is in SVN for tag {{servicemix-3.1.1}}, so I
guess something went wrong with the publishing. Does anyone know how to
publish a correct file?
> Basic example fails to build: InvalidProjectModelException
> --
>
> Key: SM-997
> URL: https://issues.apache.org/activemq/browse/SM-997
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-assembly
>Affects Versions: 3.1.1
> Environment: Servicemix 3.1.1-incubating, Windows XP, Java 1.5.0_12,
> Maven 2.0.6
>Reporter: Evan Deaubl
>
> When I attempt to run either mvn install, or mvn jbi:embeddedServicemix on
> the project in examples/basic, I receive the following error. I have
> completely removed my Maven repository and had it redownload everything from
> scratch, and still received this error. I manually checked the file it had
> downloaded, and the XML file was indeed invalid, and downloading the file
> directly from the source
> (http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom)
> using Firefox yields an XML Parsing Error.
> [INFO] Scanning for projects...
> Downloading:
> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/samples/3.1.1-incubating/samples-3.1.1-incubating.pom
> 2K downloaded
> Downloading:
> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
> 69K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '507906935d130cfa9b44696270f62e006367533d'; remote =
> 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - RETRYING
> Downloading:
> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/servicemix/3.1.1-incubating/servicemix-3.1.1-incubating.pom
> 69K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '507906935d130cfa9b44696270f62e006367533d'; remote =
> 'a79a1012430e34db6e471c444f0dd77c28be9d0e' - IGNORING
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Error building POM (may not be this project's POM).
> Project ID: org.apache.servicemix:samples:pom:null
> Reason: Cannot find parent: org.apache.servicemix:servicemix for project:
> org.apache.servicemix:samples:pom:null
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> org.apache.servicemix:servicemix for project:
> org.apache.servicemix:samples:pom:null
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find
> parent: org.apache.servicemix:servicemix for project:
> org.apache.servicemix:samples:pom:null
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1264)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1281)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:749)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
> at org.apache.maven.DefaultMaven.
[jira] Created: (SM-988) WSDL generation fails (SU built by servicemix-jsr181-annotated-service-unit archetype)
WSDL generation fails (SU built by servicemix-jsr181-annotated-service-unit
archetype)
--
Key: SM-988
URL: https://issues.apache.org/activemq/browse/SM-988
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.1
Reporter: Gert Vanthienen
Priority: Minor
If you build a SU using the servicemix-jsr181-annotated-service-unit, it
generates a pom.xml file which calls upon XFire's wsdlgen to generate a WSDL
file. However, this WSDL generation fails with this exception:
{noformat}
Embedded error: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'org.codehaus.xfire.spring.ServiceBean' defined in file
[C:\opt\project\jsr181-sample\wsdl-generate-sample\wsdlgen-jsr181-su\src\main\resources\services.xml]:
Error setting property values; nested
exception is org.springframework.beans.PropertyAccessExceptionsException:
PropertyAccessExceptionsException (1 errors); nested propertyAccessExceptions
are: [org.springframework.beans.TypeMismatchException: Failed to convert
property value of type [java.lang.String] to required type [java.lang.Class
] for property 'serviceClass'; nested exception is
java.lang.IllegalArgumentException: Class not found: com.sample.ExampleService]
{noformat}
Seems like the generator can't find the class, but yet the configuration for
the Ant task looks correct...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-939) CXF based Service Engine and Bnding Component
[ https://issues.apache.org/activemq/browse/SM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39544 ] Gert Vanthienen commented on SM-939: Applied and tested the second patch: everything compiles and tests run without failures. Committed as http://svn.apache.org/viewvc?view=rev&revision=551139 Thanks to Freeman Fang... > CXF based Service Engine and Bnding Component > - > > Key: SM-939 > URL: https://issues.apache.org/activemq/browse/SM-939 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Freeman Fang >Priority: Critical > Fix For: 3.2 > > Attachments: patch.txt, patch0627.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-960) JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE )
[
https://issues.apache.org/activemq/browse/SM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated SM-960:
---
Attachment: citytime-sa-1.0-SNAPSHOT.jar
This is a SA that shows the problem when deploying it. Could this be bug
within XFire, StAX, ...?
> JSR181 Orchestration sample doesn't work (Current state not START_ELEMENT,
> END_ELEMENT or ENTITY_REFERENCE )
>
>
> Key: SM-960
> URL: https://issues.apache.org/activemq/browse/SM-960
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
>Reporter: Sangwoo Han
>Priority: Minor
> Attachments: citytime-sa-1.0-SNAPSHOT.jar
>
>
> The jsr181 orchestration sample doesn't work.
> In the sample of jsr181 orchestration's CityTimeImpl.java class file
> [...]
> public GetCityTimeResponse getCityTime(GetCityTimeRequest
> GetCityTimeRequest) {
>
> GetInfoByCity GetInfoByCity = new GetInfoByCity();
> GetInfoByCity.setUSCity(GetCityTimeRequest.getCity());
>
> GetInfoByCityResponse r = usZip.getInfoByCity(GetInfoByCity);
> Element e = (Element)
> r.getGetInfoByCityResult().getContent().get(0);
> e = (Element) e.getElementsByTagName("Table").item(0);
> e = (Element) e.getElementsByTagName("ZIP").item(0);
> String ZipCode = e.getTextContent();
>
> //String lt = localTime.localTimeByZipCode(ZipCode); // at this
> part it errored
> GetCityTimeResponse rep = new GetCityTimeResponse();
> rep.getString().add("23:23");
> //rep.setTime(lt); // wsgen didn't generate "setTime" function
> return rep;
> }
> [...]
> and the error output is below:
>
> [...]
> DEBUG - header - << "Content-Length: 426[\r][\n]"
> DEBUG - content- << " encoding="utf-8"?>http://schemas.xmlso
> ap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";> dy> xmlns="http://ripedev.com/xsd/ZipCodeResults.xsd";>5/30/2007
> 8:51:44 PM ocalTimeByZipCodeResult>"
>
> DEBUG - Client - Received message to
> urn:xfire:transport:jbi:11805763005154-996237611
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase pre-dispatch
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase dispatch
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase dispatch
> DEBUG - HandlerPipeline- Invoking phase transport
> DEBUG - HandlerPipeline- Invoking phase parse
> DEBUG - HandlerPipeline- Invoking phase pre-dispatch
> DEBUG - HandlerPipeline- Invoking handler
> org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch
> DEBUG - Client - Correlating context with ID
> 118057630051551778993400
> DEBUG - Client - Found correlated context with ID
> 118057630051551778993400
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase service
> DEBUG - HandlerPipeline- Invoking phase dispatch
> DEBUG - HandlerPipeline- Invoking handler
> org.codehaus.xfire.handler.LocateBindingHandler in phase dispatch
> DEBUG - HandlerPipeline- Invoking handler
> org.codehaus.xfire.soap.handler.SoapBodyHandler in phase dispatch
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase user
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase pre-dispatch
> DEBUG - HandlerPipeline- Invoking phase transport
> DEBUG - HandlerPipeline- Invoking phase parse
> DEBUG - HandlerPipeline- Invoking phase pre-dispatch
> DEBUG - HandlerPipeline- Invoking handler
> org.codehaus.xfire.client.CorrelatorHandler in phase pre-dispatch
> DEBUG - Client - Correlating context with ID
> 118057630051551778993400
> DEBUG - Client - Found correlated context with ID
> 118057630051551778993400
> DEBUG - HandlerPipeline- adding handler [EMAIL PROTECTED] to
> phase service
> DEBUG - HandlerPipeline- Invoking phase dispatch
> DEBUG - HandlerPipeline- Invoking phase policy
> DEBUG - HandlerPipeline- Invoking phase user
> DEBUG - HandlerPipeline- Invoking handler
> org.codehaus.xfire.client.ClientFaultConverter in phase user
> DEBUG - HandlerPipel
[jira] Updated: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-932: --- Attachment: SM-932-xmpp.patch SM-932-truezip.patch Patches for servicemix-truezip and servicemix-xmpp > Enable PMD/CheckStyle for binding components > > > Key: SM-932 > URL: https://issues.apache.org/activemq/browse/SM-932 > Project: ServiceMix > Issue Type: Task > Components: servicemix-file, servicemix-ftp, servicemix-http, > servicemix-jms, servicemix-truezip >Reporter: Gert Vanthienen >Priority: Minor > Attachments: SM-932-file.patch, SM-932-ftp.patch, SM-932-jms.patch, > SM-932-truezip.patch, SM-932-xmpp.patch > > > PMD/CheckStyle should be enabled for binding components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-932: --- Attachment: SM-932-jms.patch SM-932-jms.patch fixes PDM/CheckStyle errors for servicemix-jms > Enable PMD/CheckStyle for binding components > > > Key: SM-932 > URL: https://issues.apache.org/activemq/browse/SM-932 > Project: ServiceMix > Issue Type: Task > Components: servicemix-file, servicemix-ftp, servicemix-http, > servicemix-jms, servicemix-truezip >Reporter: Gert Vanthienen >Priority: Minor > Attachments: SM-932-file.patch, SM-932-ftp.patch, SM-932-jms.patch > > > PMD/CheckStyle should be enabled for binding components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-932: --- Attachment: SM-932-ftp.patch SM-932-ftp.patch fixes PDM/CheckStyle errors for servicemix-ftp > Enable PMD/CheckStyle for binding components > > > Key: SM-932 > URL: https://issues.apache.org/activemq/browse/SM-932 > Project: ServiceMix > Issue Type: Task > Components: servicemix-file, servicemix-ftp, servicemix-http, > servicemix-jms, servicemix-truezip >Reporter: Gert Vanthienen >Priority: Minor > Attachments: SM-932-file.patch, SM-932-ftp.patch > > > PMD/CheckStyle should be enabled for binding components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-915) FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
[
https://issues.apache.org/activemq/browse/SM-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38955
]
Gert Vanthienen commented on SM-915:
... but the original problem still isn't solved.
We get an additional stacktrace when ServiceMix is stopping and the problem
only appears to exist when the FTP server is IIS.
{code}
java.io.IOException: Fatal thread interruption during read.
at
org.apache.commons.net.telnet.TelnetInputStream.read(TelnetInputStream.java:344)
at
org.apache.commons.net.telnet.TelnetInputStream.read(TelnetInputStream.java:466)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at org.apache.commons.net.ftp.FTP.__getReply(FTP.java:264)
at org.apache.commons.net.ftp.FTP.getReply(FTP.java:605)
at
org.apache.commons.net.ftp.FTPClient.completePendingCommand(FTPClient.java:1253)
at
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2400)
at
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
at org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
at
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:210)
at
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:202)
at
org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:77)
at
org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
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:595)
{code}
I've asked the commons mailing list for help on this one...
> FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
>
>
> Key: SM-915
> URL: https://issues.apache.org/activemq/browse/SM-915
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-ftp
>Affects Versions: 3.1
>Reporter: Gert Vanthienen
> Attachments: SM-915.patch
>
>
> FTP poller threads stop working with the stack trace below, causing the FTP
> client pool to run out of connections
> {code}
> Name: pool-component.servicemix-ftp-thread-2
> State: RUNNABLE
> Total blocked: 78,430 Total waited: 4,771
> Stack trace:
> java.net.PlainSocketImpl.socketAccept(Native Method)
> java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
> java.net.ServerSocket.implAccept(ServerSocket.java:450)
> java.net.ServerSocket.accept(ServerSocket.java:421)
>
> org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:502)
>
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
>
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:211)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:203)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:78)
>
> org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> java.lang.Thread.run(Thread.java:595)
> {code}
> See http://www.nabble.com/FTP-poller-stalls...-tf3490690s12049.html for more
> information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-915) FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
[
https://issues.apache.org/activemq/browse/SM-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38944
]
Gert Vanthienen commented on SM-915:
Some additional observations - the problem only appears when:
* when a lot of files become available on the FTP server together
* some of them are being downloaded before they are complete, i.e. incomplete
XML messages are being read and processing fails for these messages
In the FTP poller code, we find
{code}
InputStream in = ftp.retrieveFileStream(file);
InOnly exchange = getExchangeFactory().createInOnlyExchange();
configureExchangeTarget(exchange);
NormalizedMessage message = exchange.createMessage();
exchange.setInMessage(message);
marshaler.readMessage(exchange, message, in, file);
sendSync(exchange);
in.close();
ftp.completePendingCommand();
{code}
My question: Is it possible that {{sendSync(exchange)}} throws an Exception
when an incomplete XML message is retrieved from the server? If it does, the
inputstream is never closed and {{completePendingCommand()}} is never called,
which might explain the problems
> FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
>
>
> Key: SM-915
> URL: https://issues.apache.org/activemq/browse/SM-915
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-ftp
>Affects Versions: 3.1
>Reporter: Gert Vanthienen
>
> FTP poller threads stop working with the stack trace below, causing the FTP
> client pool to run out of connections
> {code}
> Name: pool-component.servicemix-ftp-thread-2
> State: RUNNABLE
> Total blocked: 78,430 Total waited: 4,771
> Stack trace:
> java.net.PlainSocketImpl.socketAccept(Native Method)
> java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
> java.net.ServerSocket.implAccept(ServerSocket.java:450)
> java.net.ServerSocket.accept(ServerSocket.java:421)
>
> org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:502)
>
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
>
> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:211)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:203)
>
> org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:78)
>
> org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> java.lang.Thread.run(Thread.java:595)
> {code}
> See http://www.nabble.com/FTP-poller-stalls...-tf3490690s12049.html for more
> information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-915) FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
FTP poller stalls with threads waiting on PlainSocketImpl.socketAccept()
Key: SM-915
URL: https://issues.apache.org/activemq/browse/SM-915
Project: ServiceMix
Issue Type: Bug
Components: servicemix-ftp
Affects Versions: 3.1
Reporter: Gert Vanthienen
FTP poller threads stop working with the stack trace below, causing the FTP
client pool to run out of connections
{code}
Name: pool-component.servicemix-ftp-thread-2
State: RUNNABLE
Total blocked: 78,430 Total waited: 4,771
Stack trace:
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
java.net.ServerSocket.implAccept(ServerSocket.java:450)
java.net.ServerSocket.accept(ServerSocket.java:421)
org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:502)
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:211)
org.apache.servicemix.ftp.FtpPollerEndpoint.pollFileOrDirectory(FtpPollerEndpoint.java:203)
org.apache.servicemix.ftp.FtpPollerEndpoint.poll(FtpPollerEndpoint.java:78)
org.apache.servicemix.common.endpoints.PollingEndpoint$PollSchedulerTask$1.run(PollingEndpoint.java:155)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
java.lang.Thread.run(Thread.java:595)
{code}
See http://www.nabble.com/FTP-poller-stalls...-tf3490690s12049.html for more
information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-899) org.apache.servicemix.file.SpringComponentTest fails with java.lang.IllegalStateException
[
https://issues.apache.org/activemq/browse/SM-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38916
]
Gert Vanthienen commented on SM-899:
As far as I understand the code:
DefaultComponent's doInit() method first registers all endpoint, thereby lazily
creating the corresponding service unit. After all endpoint have been
registered, the serviceUnit is no longer *{{null}}* and the doInit() method
will call Registry's registerServiceUnit() which will attempt to register all
the endpoints again, resulting in the stacktrace shown above.
The simple solution would be to add a test to DefaultComponent's doInit()
method, only registering the service unit if it hasn't been registered before.
As a more general solution, the same test could also be added to Registry's
registerServiceUnit(). Does anyone see a problem with the latter approach?
> org.apache.servicemix.file.SpringComponentTest fails with
> java.lang.IllegalStateException
> -
>
> Key: SM-899
> URL: https://issues.apache.org/activemq/browse/SM-899
> Project: ServiceMix
> Issue Type: Sub-task
> Components: servicemix-file
>Affects Versions: 3.1
>Reporter: Gert Vanthienen
>
> This is the stack trace:
> {noformat}
> Caused by: javax.jbi.JBIException: Error calling init
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:195)
>
> Caused by: java.lang.IllegalStateException: An endpoint is already registered
> for key: {urn:test}service:endpoint
> at
> org.apache.servicemix.common.Registry.registerEndpoint(Registry.java:55)
> at
> org.apache.servicemix.common.Registry.registerServiceUnit(Registry.java:68)
> at
> org.apache.servicemix.common.DefaultComponent.doInit(DefaultComponent.java:292)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:187)
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-899) org.apache.servicemix.file.SpringComponentTest fails with java.lang.IllegalStateException
org.apache.servicemix.file.SpringComponentTest fails with
java.lang.IllegalStateException
-
Key: SM-899
URL: https://issues.apache.org/activemq/browse/SM-899
Project: ServiceMix
Issue Type: Sub-task
Components: servicemix-file
Affects Versions: 3.1
Reporter: Gert Vanthienen
This is the stack trace:
{noformat}
Caused by: javax.jbi.JBIException: Error calling init
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:195)
Caused by: java.lang.IllegalStateException: An endpoint is already registered
for key: {urn:test}service:endpoint
at org.apache.servicemix.common.Registry.registerEndpoint(Registry.java:55)
at
org.apache.servicemix.common.Registry.registerServiceUnit(Registry.java:68)
at
org.apache.servicemix.common.DefaultComponent.doInit(DefaultComponent.java:292)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:187)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-889) Add possibility to rename files after FTP upload
[ https://issues.apache.org/activemq/browse/SM-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-889: --- Attachment: SM-889.patch This patch allows users to specify an attribute uploadSuffix="..." on the endpoint. This suffix will be appended to the file name during upload. Upon completion, the file will be renamed to the correct name. This attribute only works if a name has been specified for upload, otherwise it is ignored. The patch also tries to solve a problem I have encountered with IIS/FTP. If no data was actually transferred to the server (e.g. because of an already existing file name), the call to client.completePendingCommand() sometimes appeared to take a very long time (waiting for some kind of time-out). With this patch, this call will only be issued if an OutputStream has actually been acquired. > Add possibility to rename files after FTP upload > > > Key: SM-889 > URL: https://issues.apache.org/activemq/browse/SM-889 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-ftp >Affects Versions: 3.1 >Reporter: Gert Vanthienen >Priority: Minor > Fix For: 3.1.1, 3.2 > > Attachments: SM-889.patch > > > Add the possibility to upload files to the FTP server using another suffix > (e.g. .part) and rename the file after the upload is completed. This way, it > is possible for another process to determine when file upload has finished. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-889) Add possibility to rename files after FTP upload
Add possibility to rename files after FTP upload Key: SM-889 URL: https://issues.apache.org/activemq/browse/SM-889 Project: ServiceMix Issue Type: Improvement Components: servicemix-ftp Affects Versions: 3.1 Reporter: Gert Vanthienen Priority: Minor Fix For: 3.1.1, 3.2 Add the possibility to upload files to the FTP server using another suffix (e.g. .part) and rename the file after the upload is completed. This way, it is possible for another process to determine when file upload has finished. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-109) Eclipse plug-in doesn't show errors on deployment
Eclipse plug-in doesn't show errors on deployment - Key: GERONIMODEVTOOLS-109 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-109 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 1.1.0 Reporter: Gert Vanthienen Priority: Minor As discussed in the thread of http://mail-archives.apache.org/mod_mbox/geronimo-user/200609.mbox/browser, errors that occur on deployment of an application are not available in the Eclipse UI. You can get to them in a log in workspace/.metadata, but a more user friendly way would be to show this information in the error dialog itself. -- 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
