[jira] Created: (CAMEL-332) CXF Component
CXF Component -- Key: CAMEL-332 URL: https://issues.apache.org/activemq/browse/CAMEL-332 Project: Apache Camel Issue Type: Improvement Reporter: Aswani Kumar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-332) CXF Component
[ https://issues.apache.org/activemq/browse/CAMEL-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aswani Kumar updated CAMEL-332: --- Attachment: camel-cxf_provider_example.patch.txt Patch file with full example showing the usage of the Webservice Provider with the client using JaxWS Dispatch API. > CXF Component > -- > > Key: CAMEL-332 > URL: https://issues.apache.org/activemq/browse/CAMEL-332 > Project: Apache Camel > Issue Type: Improvement >Reporter: Aswani Kumar >Assignee: Willem Jiang > Attachments: camel-cxf_provider_example.patch.txt, jira332.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-332) CXF Component
[ https://issues.apache.org/activemq/browse/CAMEL-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-332: -- Assignee: Willem Jiang > CXF Component > -- > > Key: CAMEL-332 > URL: https://issues.apache.org/activemq/browse/CAMEL-332 > Project: Apache Camel > Issue Type: Improvement >Reporter: Aswani Kumar >Assignee: Willem Jiang > Attachments: jira332.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-324) bad content length header value in http response
[
https://issues.apache.org/activemq/browse/CAMEL-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41288#action_41288
]
alex c commented on CAMEL-324:
--
Sure, here is a route that reproduces the problem. This simply routes a java
serialized, base64 encoded request (and returns the response back) to the
echoService on a http channel:
from("direct:echoService").marshal().serialization().beanRef("base64Encoder")
.to("http://localhost:8088/echoService";).beanRef("base64Decoder").unmarshal().serialization();
from("jetty:http://localhost:8088/echoService";).beanRef("base64Decoder")
.unmarshal().serialization().to("bean:echoService").marshal().serialization().beanRef("base64Encoder");
I think the problem comes from the [un]marshall processor that copies the
complete in message (with headers) to the out message before setting the
[un]marshalled body in the out message. Here is the code:
Message in = exchange.getIn();
Object body = in.getBody();
// lets setup the out message before we invoke the dataFormat
// so that it can mutate it if necessary
Message out = exchange.getOut(true);
out.copyFrom(in);
Thanks,
Alex.
> bad content length header value in http response
>
>
> Key: CAMEL-324
> URL: https://issues.apache.org/activemq/browse/CAMEL-324
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 1.3.0
>Reporter: alex c
>Assignee: Gary Tully
>Priority: Critical
>
> By default HttpBinding class copies all request header attributes from the
> request to the response including 'Content-Length'. So the consequence is
> that the response is declaring the same size as the request which can lead to
> serious truncation problems!
> the workaround is simply to add the line:
> out.removeHeader("Content-Length");
> in the writeResponse method of the httpbinding class allowing jetty to set
> the right value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-324) bad content length header value in http response
[
https://issues.apache.org/activemq/browse/CAMEL-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41286#action_41286
]
Gary Tully commented on CAMEL-324:
--
Hi Alex,
I am having difficulty reproducing the behaviour you describe. In
writeResponse[1] on trunk, the headers are correctly copied from the out
message, not from the request. The out message defaults to an empty
DefaultMessage which would have no headers.
Would it be possible to provide a test route or xml config fragment or some
more detail?
Thanks,
Gary.
http://svn.apache.org/viewvc/activemq/camel/trunk/components/camel-http/src/main/java/org/apache/camel/component/http/HttpBinding.java?view=markup
> bad content length header value in http response
>
>
> Key: CAMEL-324
> URL: https://issues.apache.org/activemq/browse/CAMEL-324
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 1.3.0
>Reporter: alex c
>Assignee: Gary Tully
>Priority: Critical
>
> By default HttpBinding class copies all request header attributes from the
> request to the response including 'Content-Length'. So the consequence is
> that the response is declaring the same size as the request which can lead to
> serious truncation problems!
> the workaround is simply to add the line:
> out.removeHeader("Content-Length");
> in the writeResponse method of the httpbinding class allowing jetty to set
> the right value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-332) CXF Component
[ https://issues.apache.org/activemq/browse/CAMEL-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aswani Kumar updated CAMEL-332: --- Attachment: jira332.patch Please find the patch for the changes I have made. > CXF Component > -- > > Key: CAMEL-332 > URL: https://issues.apache.org/activemq/browse/CAMEL-332 > Project: Apache Camel > Issue Type: Improvement >Reporter: Aswani Kumar > Attachments: jira332.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-324) bad content length header value in http response
[
https://issues.apache.org/activemq/browse/CAMEL-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned CAMEL-324:
Assignee: Gary Tully
> bad content length header value in http response
>
>
> Key: CAMEL-324
> URL: https://issues.apache.org/activemq/browse/CAMEL-324
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 1.3.0
>Reporter: alex c
>Assignee: Gary Tully
>Priority: Critical
>
> By default HttpBinding class copies all request header attributes from the
> request to the response including 'Content-Length'. So the consequence is
> that the response is declaring the same size as the request which can lead to
> serious truncation problems!
> the workaround is simply to add the line:
> out.removeHeader("Content-Length");
> in the writeResponse method of the httpbinding class allowing jetty to set
> the right value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-330) Components / endpoints should advertise the data types they support
Components / endpoints should advertise the data types they support Key: CAMEL-330 URL: https://issues.apache.org/activemq/browse/CAMEL-330 Project: Apache Camel Issue Type: New Feature Components: camel-core Affects Versions: 1.2.0 Reporter: Hadrian Zbarcea Fix For: 1.4.0 In the current version a conversion is attempted on a best effort basis. An endpoint does not have knowledge about the data types supported by the previous or next endpoint in the route. If an endpoint would publish what data types it supports, static analysis would be possible to determine if messages could be processed successfully or additional type converters are necessary. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (CAMEL-329) Throwing the IllegalArgumentException if there are already another type bean which name is same with the URI schema
[ https://issues.apache.org/activemq/browse/CAMEL-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-329 started by Willem Jiang. > Throwing the IllegalArgumentException if there are already another type bean > which name is same with the URI schema > > > Key: CAMEL-329 > URL: https://issues.apache.org/activemq/browse/CAMEL-329 > Project: Apache Camel > Issue Type: Bug > Components: camel-core, camel-cxf >Affects Versions: 1.2.0 >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 1.3.0 > > > Please see the discussion below > http://www.nabble.com/%22cxf%22-name-conflict-in-the-spring-context-td15427019s22882.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-329) Throwing the IllegalArgumentException if there are already another type bean which name is same with the URI schema
Throwing the IllegalArgumentException if there are already another type bean which name is same with the URI schema Key: CAMEL-329 URL: https://issues.apache.org/activemq/browse/CAMEL-329 Project: Apache Camel Issue Type: Bug Components: camel-core, camel-cxf Affects Versions: 1.2.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 1.3.0 Please see the discussion below http://www.nabble.com/%22cxf%22-name-conflict-in-the-spring-context-td15427019s22882.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-328) add a simple List endpoint that can be used to keep the messages sent to it so they can be visualised in a testing or demo tool
add a simple List endpoint that can be used to keep the messages sent to it so they can be visualised in a testing or demo tool --- Key: CAMEL-328 URL: https://issues.apache.org/activemq/browse/CAMEL-328 Project: Apache Camel Issue Type: New Feature Reporter: James Strachan Fix For: 1.3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-285) support browsing of endpoints via Endpoint.createBrowser()
[
https://issues.apache.org/activemq/browse/CAMEL-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Strachan resolved CAMEL-285.
--
Resolution: Fixed
Fix Version/s: 1.3.0
We have an optional BrowseableEndpoint interface that an Endpoint can implement
now.
so you can browse the endpoints and their messages via this code
{code}
List list =
CamelContextHelper.getSingletonEndpoints(context, BrowsableEndpoint.class);
{code}
then call the getExchanges() method.
> support browsing of endpoints via Endpoint.createBrowser()
> --
>
> Key: CAMEL-285
> URL: https://issues.apache.org/activemq/browse/CAMEL-285
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: James Strachan
> Fix For: 1.3.0
>
>
> So that we can browse the available messages such as on a message queue, in a
> file system, on a HTTP server etc Useful for management really
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-328) add a simple List endpoint that can be used to keep the messages sent to it so they can be visualised in a testing or demo tool
[ https://issues.apache.org/activemq/browse/CAMEL-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Strachan resolved CAMEL-328. -- Resolution: Fixed See the documentation : http://cwiki.apache.org/CAMEL/list.html > add a simple List endpoint that can be used to keep the messages sent to it > so they can be visualised in a testing or demo tool > --- > > Key: CAMEL-328 > URL: https://issues.apache.org/activemq/browse/CAMEL-328 > Project: Apache Camel > Issue Type: New Feature >Reporter: James Strachan > Fix For: 1.3.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-331) provide a simple UI for viewing endpoints and the exchanges on them
provide a simple UI for viewing endpoints and the exchanges on them --- Key: CAMEL-331 URL: https://issues.apache.org/activemq/browse/CAMEL-331 Project: Apache Camel Issue Type: New Feature Reporter: James Strachan Fix For: 1.3.0 See the [browsable endpoint feature|http://activemq.apache.org/camel/browsableendpoint.html] for details of how it'd work -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
