Quantcast

[GitHub] camel pull request #1459: CAMEL-10817: Prevent duplicated xmlns namespace pr...

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] camel pull request #1459: CAMEL-10817: Prevent duplicated xmlns namespace pr...

ramu11
GitHub user jamesnetherton opened a pull request:

    https://github.com/apache/camel/pull/1459

    CAMEL-10817: Prevent duplicated xmlns namespace prefix

    https://issues.apache.org/jira/browse/CAMEL-10817

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jamesnetherton/camel CAMEL-10817

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1459.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1459
   
----
commit f41bc2ec16b9963b52646dd487b9d07e8c38a556
Author: James Netherton <[hidden email]>
Date:   2017-02-13T08:43:58Z

    CAMEL-10817: Prevent duplicated xmlns namespace prefix when dumping model XML

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] camel pull request #1459: CAMEL-10817: Prevent duplicated xmlns namespace pr...

ramu11
Github user jamesnetherton closed the pull request at:

    https://github.com/apache/camel/pull/1459


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Loading...