[jira] Created: (SM-904) The jmx url is wrong if there are spaces at the end of the properties
The jmx url is wrong if there are spaces at the end of the properties - Key: SM-904 URL: https://issues.apache.org/activemq/browse/SM-904 Project: ServiceMix Issue Type: Bug Components: servicemix-core Reporter: Thomas Termin Assigned To: Thomas Termin The jmx.url string is wrong if the properties in servicemix.properties have spaces at the end. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-904) The jmx url is wrong if there are spaces at the end of the properties
[
https://issues.apache.org/activemq/browse/SM-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Termin resolved SM-904.
--
Resolution: Fixed
fixed with serviceUrl = serviceUrl.replaceAll(" ", "");
Author: tterm
Date: Thu Mar 29 01:28:39 2007
New Revision: 523618
URL: http://svn.apache.org/viewvc?view=rev&rev=523618
Log:
SM-904 The jmx.url string is wrong if the properties in servicemix.properties
have spaces at the end
Modified:
incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/jmx/ConnectorServerFactoryBean.java
> The jmx url is wrong if there are spaces at the end of the properties
> -
>
> Key: SM-904
> URL: https://issues.apache.org/activemq/browse/SM-904
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
>Reporter: Thomas Termin
> Assigned To: Thomas Termin
>
> The jmx.url string is wrong if the properties in servicemix.properties have
> spaces at the end.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
SOAP binding/serialization
Hi,
I had some issues with soap messages not being serialized properly,
header/body handling (binding) etc. I'm using the wsdl11-wrapping and
I don't know if it has something to do with this. Anyways, at least it
looks like the binding stuff is being discarded at
org.apache.servicemix.http.HttpEndpoint:228, but I don't know if the
part handling (soap binding) was occurring before that; although, the
end-results weren't suggesting so. (All parts were serialized to the
soap body, or something.) So I hacked up this little patch which does
the part handling. Diffs attached. Best effort -kind of stuff, works
for me. Just if anyone else is interested.. Though, I didn't quite get
what HttpEndpoint#overrideDefinition was trying to do so that hack may
be a little conflicting.. (see the httpendpoint-patch.)
I'd also like to know if this would somehow work without the patch as
patches are a bit annoying. :)
(There also appears to be some major stuff coming in the soap2-module,
but it seemed a little incomplete so I didn't take a closer look.)
Btw., I guess the soap-headers of the reply message are being
forwarded correctly?
-janne
Index:
servicemix-soap/src/main/java/org/apache/servicemix/soap/marshalers/JBIMarshaler.java
===
---
servicemix-soap/src/main/java/org/apache/servicemix/soap/marshalers/JBIMarshaler.java
(revision 523275)
+++
servicemix-soap/src/main/java/org/apache/servicemix/soap/marshalers/JBIMarshaler.java
(working copy)
@@ -17,6 +17,8 @@
package org.apache.servicemix.soap.marshalers;
import java.net.URI;
+import java.util.Collection;
+import java.util.HashSet;
import java.util.Iterator;
import java.util.Map;
import java.util.Set;
@@ -24,11 +26,26 @@
import javax.activation.DataHandler;
import javax.jbi.messaging.Fault;
import javax.jbi.messaging.NormalizedMessage;
+import javax.wsdl.Message;
+import javax.wsdl.Part;
+import javax.wsdl.WSDLElement;
+import javax.wsdl.extensions.soap.SOAPHeader;
import javax.xml.namespace.QName;
+import javax.xml.parsers.DocumentBuilder;
+import javax.xml.parsers.ParserConfigurationException;
+import javax.xml.transform.Transformer;
+import javax.xml.transform.TransformerException;
+import javax.xml.transform.TransformerFactory;
+import javax.xml.transform.dom.DOMResult;
+import javax.xml.transform.dom.DOMSource;
import org.apache.servicemix.JbiConstants;
+import org.apache.servicemix.jbi.util.DOMUtil;
import org.apache.servicemix.soap.SoapFault;
+import org.w3c.dom.Document;
import org.w3c.dom.DocumentFragment;
+import org.w3c.dom.Node;
+import org.w3c.dom.NodeList;
/**
*
@@ -73,7 +90,8 @@
}
}
- public void fromNMS(SoapMessage soapMessage, NormalizedMessage
normalizedMessage) {
+ public void fromNMS(SoapMessage soapMessage, NormalizedMessage
normalizedMessage,
+ Message msg, WSDLElement bindingElem) {
if (normalizedMessage.getProperty(JbiConstants.SOAP_HEADERS) !=
null) {
Map headers = (Map)
normalizedMessage.getProperty(JbiConstants.SOAP_HEADERS);
for (Iterator it = headers.entrySet().iterator();
it.hasNext();) {
@@ -95,6 +113,55 @@
URI role = (URI) normalizedMessage.getProperty(SOAP_FAULT_ROLE);
SoapFault fault = new SoapFault(code, subcode, reason, node, role,
normalizedMessage.getContent());
soapMessage.setFault(fault);
+} else if (bindingElem != null) {
+ boolean success = false;
+ DocumentBuilder docBuilder = null;
+ try {
+ // QName#hashCode() is implemented suitably
+ Collection headerElems = new HashSet();
+ for (Object ext :
bindingElem.getExtensibilityElements()) {
+ if (ext instanceof SOAPHeader) {
+ Part p = msg.getPart(((SOAPHeader)
ext).getPart());
+ if (p != null && p.getElementName() !=
null)
+
headerElems.add(p.getElementName());
+ }
+ }
+ docBuilder = DOMUtil.getBuilder();
+ Transformer tr =
TransformerFactory.newInstance().newTransformer();
+ Document jbiContent = docBuilder.newDocument();
+ Document soapBody = docBuilder.newDocument();
+ tr.transform(normalizedMessage.getContent(), new
DOMResult(jbiContent));
+ NodeList wrapperMsg = jbiContent.getElementsByTagNameNS(
+
"http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper";, "message");
+ if (wrapperMsg.getLength() == 1) {
+ Node part = wrapperMsg.item(0).getFirstChild();
+
[jira] Commented: (SM-905) message filter registers predicates as mbean as well as a new predicate for on/off filtering
[ https://issues.apache.org/activemq/browse/SM-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38925 ] Guillaume Nodet commented on SM-905: A few thoughts: * the mbean related stuff should be put upper in the class hierachy (in the Endpoint class i'd say) * the endpoint could define one helper method: public void registerMBean(Object implementation, Class interfaceClass, String name) or public void registerMBean(Object implementation, Class interfaceClass) where the name could be defaulted to the interface name, minus the "MBean". Actually the interface could be also auto detected by checking all the interfaces implemented by the object that ends with "MBean", so the method could just be public void registerMBean(Object implementation) Well, maybe the three methods can be implemented ... That way, the endpoint could register an interface for a sub component (like the filter predicate), or for itself. Again, this behavior could also be turned on by default (auto-discovery of interfaces implemented by the endpoint ending with "Mbean") ... > message filter registers predicates as mbean as well as a new predicate for > on/off filtering > > > Key: SM-905 > URL: https://issues.apache.org/activemq/browse/SM-905 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-eip >Reporter: Thomas Termin >Priority: Minor > Attachments: eip-message-filter.patch > > > Predicat MBeans are registered exactly as the endpoint just with the > extension "Predicate" > Interessting is the message filter which do all with reflection and just > register predicates if an MBean interface is implemented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-906) extend ComponentSupport with methods to propagate the correlation id
extend ComponentSupport with methods to propagate the correlation id Key: SM-906 URL: https://issues.apache.org/activemq/browse/SM-906 Project: ServiceMix Issue Type: Improvement Components: servicemix-core Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Minor extends ComponentSupport that it has methods for creating exchanges with propagating the correlation id -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-907) Update to the latest version of the 1.3 spec
Update to the latest version of the 1.3 spec Key: SM-907 URL: https://issues.apache.org/activemq/browse/SM-907 Project: ServiceMix Issue Type: Improvement Components: servicemix-wsn2005 Affects Versions: 3.1 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet 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-907) Update to the latest version of the WS-Notification 1.3 spec
[ https://issues.apache.org/activemq/browse/SM-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-907. Resolution: Fixed URL: http://svn.apache.org/viewvc?view=rev&rev=523728 > Update to the latest version of the WS-Notification 1.3 spec > > > Key: SM-907 > URL: https://issues.apache.org/activemq/browse/SM-907 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-wsn2005 >Affects Versions: 3.1 >Reporter: Guillaume Nodet > Assigned To: Guillaume Nodet >Priority: Minor > 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-907) Update to the latest version of the WS-Notification 1.3 spec
[ https://issues.apache.org/activemq/browse/SM-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-907: --- Priority: Minor (was: Major) Summary: Update to the latest version of the WS-Notification 1.3 spec (was: Update to the latest version of the 1.3 spec) > Update to the latest version of the WS-Notification 1.3 spec > > > Key: SM-907 > URL: https://issues.apache.org/activemq/browse/SM-907 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-wsn2005 >Affects Versions: 3.1 >Reporter: Guillaume Nodet > Assigned To: Guillaume Nodet >Priority: Minor > 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] Created: (SM-908) Upgrade to ActiveMQ 5.0
Upgrade to ActiveMQ 5.0 --- Key: SM-908 URL: https://issues.apache.org/activemq/browse/SM-908 Project: ServiceMix Issue Type: Improvement Reporter: Guillaume Nodet 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] Created: (SM-909) Upgrade to Geronimo 2.0
Upgrade to Geronimo 2.0 --- Key: SM-909 URL: https://issues.apache.org/activemq/browse/SM-909 Project: ServiceMix Issue Type: Improvement Reporter: Guillaume Nodet 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-903) ServiceMix now requires java 5
[ https://issues.apache.org/activemq/browse/SM-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-903. Resolution: Fixed Assignee: Guillaume Nodet URL: http://svn.apache.org/viewvc?view=rev&rev=523712 To be able to fully remove backport-util-concurrent from the distribution, we need to switch to AMQ 5.0 and Geronimo 2.0 > ServiceMix now requires java 5 > -- > > Key: SM-903 > URL: https://issues.apache.org/activemq/browse/SM-903 > Project: ServiceMix > Issue Type: Improvement >Reporter: Guillaume Nodet > Assigned To: Guillaume Nodet > 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] Created: (SM-910) better handling of unavailable external http services
better handling of unavailable external http services - Key: SM-910 URL: https://issues.apache.org/activemq/browse/SM-910 Project: ServiceMix Issue Type: Improvement Components: servicemix-http Affects Versions: 3.1 Reporter: Dominique De Vito Fix For: 3.1.1 Attachments: patchfile.txt The org.apache.servicemix.http.processors.ProviderProcessor calls an external http service. When calling an unavailable external http service, the following stack trace appears after an exception rise: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:516) at java.net.Socket.connect(Socket.java:466) at java.net.Socket.(Socket.java:366) at java.net.Socket.(Socket.java:239) at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:79) at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:121) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:168) at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489) at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441) at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46) at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593) at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174) at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176) at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) I think handling could be improved in case of (exchange instanceof InOnly == false), so that a response could be returned. See the attached patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-906) extend ComponentSupport with methods to propagate the correlation id
[ https://issues.apache.org/activemq/browse/SM-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-906. -- Resolution: Fixed Author: tterm Date: Thu Mar 29 07:43:43 2007 New Revision: 523729 URL: http://svn.apache.org/viewvc?view=rev&rev=523729 Log: SM-906 extend ComponentSupport with methods to propagate the correlation id Modified: incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/components/util/ComponentSupport.java > extend ComponentSupport with methods to propagate the correlation id > > > Key: SM-906 > URL: https://issues.apache.org/activemq/browse/SM-906 > Project: ServiceMix > Issue Type: Improvement > Components: servicemix-core >Reporter: Thomas Termin > Assigned To: Thomas Termin >Priority: Minor > > extends ComponentSupport that it has methods for creating exchanges with > propagating the correlation id -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
