You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2008/06/08 15:47:00 UTC

[jira] Created: (CAMEL-589) camel-example-spring-jmx cleanup and improvements

camel-example-spring-jmx cleanup and improvements
-------------------------------------------------

                 Key: CAMEL-589
                 URL: https://issues.apache.org/activemq/browse/CAMEL-589
             Project: Apache Camel
          Issue Type: Improvement
          Components: examples
    Affects Versions: 1.4.0
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
            Priority: Minor
             Fix For: 1.4.0


The new sample needed a bit of cleanup so I did some work.

I added some code comments to assist end-users.
I also let the broker be configured out-of-the-box in the spring xml instead of embedded java code that wasn't best-practice.

And I added an AOP aspect to act as a kind of audi interceptor on the server side to log all the incomming requests. Part of investigation of an aspectj-aop autoproxy bug report, that I can not reproduce in trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CAMEL-589) camel-example-spring-jms cleanup and improvements

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-589.
-------------------------------

    Resolution: Fixed

> camel-example-spring-jms cleanup and improvements
> -------------------------------------------------
>
>                 Key: CAMEL-589
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-589
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: examples
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> The new sample needed a bit of cleanup so I did some work.
> I added some code comments to assist end-users.
> I also let the broker be configured out-of-the-box in the spring xml instead of embedded java code that wasn't best-practice.
> And I added an AOP aspect to act as a kind of audi interceptor on the server side to log all the incomming requests. Part of investigation of an aspectj-aop autoproxy bug report, that I can not reproduce in trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-589) camel-example-spring-jmx cleanup and improvements

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43319#action_43319 ] 

Claus Ibsen commented on CAMEL-589:
-----------------------------------

Oh yes its the JMS messaging sample ;)

And it needs to update the wiki as well with my modifications (well Claus you get the pain when you mess with the code!)
http://activemq.apache.org/camel/tutorial-jmsremoting.html



> camel-example-spring-jmx cleanup and improvements
> -------------------------------------------------
>
>                 Key: CAMEL-589
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-589
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: examples
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> The new sample needed a bit of cleanup so I did some work.
> I added some code comments to assist end-users.
> I also let the broker be configured out-of-the-box in the spring xml instead of embedded java code that wasn't best-practice.
> And I added an AOP aspect to act as a kind of audi interceptor on the server side to log all the incomming requests. Part of investigation of an aspectj-aop autoproxy bug report, that I can not reproduce in trunk.

-- 
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-589) camel-example-spring-jmx cleanup and improvements

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on CAMEL-589 started by Claus Ibsen.

> camel-example-spring-jmx cleanup and improvements
> -------------------------------------------------
>
>                 Key: CAMEL-589
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-589
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: examples
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> The new sample needed a bit of cleanup so I did some work.
> I added some code comments to assist end-users.
> I also let the broker be configured out-of-the-box in the spring xml instead of embedded java code that wasn't best-practice.
> And I added an AOP aspect to act as a kind of audi interceptor on the server side to log all the incomming requests. Part of investigation of an aspectj-aop autoproxy bug report, that I can not reproduce in trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-589) camel-example-spring-jmx cleanup and improvements

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43318#action_43318 ] 

Willem Jiang commented on CAMEL-589:
------------------------------------

Hi Claus,

I think the sample you mentioned is the camel-example-spring-jms  not jmx.

Am I right?

Willem.


> camel-example-spring-jmx cleanup and improvements
> -------------------------------------------------
>
>                 Key: CAMEL-589
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-589
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: examples
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> The new sample needed a bit of cleanup so I did some work.
> I added some code comments to assist end-users.
> I also let the broker be configured out-of-the-box in the spring xml instead of embedded java code that wasn't best-practice.
> And I added an AOP aspect to act as a kind of audi interceptor on the server side to log all the incomming requests. Part of investigation of an aspectj-aop autoproxy bug report, that I can not reproduce in trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-589) camel-example-spring-jmx cleanup and improvements

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43317#action_43317 ] 

Claus Ibsen commented on CAMEL-589:
-----------------------------------

Hmm its sunday and the sun is shining and i'm sitting in the shade with a beer and a laptop and cranking on the sample to use AOP stuff to do audit backups with camel endpoints all configued using the xml and aspects. It's kinda scary what you can do in a few lines of code.

> camel-example-spring-jmx cleanup and improvements
> -------------------------------------------------
>
>                 Key: CAMEL-589
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-589
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: examples
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> The new sample needed a bit of cleanup so I did some work.
> I added some code comments to assist end-users.
> I also let the broker be configured out-of-the-box in the spring xml instead of embedded java code that wasn't best-practice.
> And I added an AOP aspect to act as a kind of audi interceptor on the server side to log all the incomming requests. Part of investigation of an aspectj-aop autoproxy bug report, that I can not reproduce in trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-589) camel-example-spring-jms cleanup and improvements

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-589:
------------------------------

    Summary: camel-example-spring-jms cleanup and improvements  (was: camel-example-spring-jmx cleanup and improvements)

> camel-example-spring-jms cleanup and improvements
> -------------------------------------------------
>
>                 Key: CAMEL-589
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-589
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: examples
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> The new sample needed a bit of cleanup so I did some work.
> I added some code comments to assist end-users.
> I also let the broker be configured out-of-the-box in the spring xml instead of embedded java code that wasn't best-practice.
> And I added an AOP aspect to act as a kind of audi interceptor on the server side to log all the incomming requests. Part of investigation of an aspectj-aop autoproxy bug report, that I can not reproduce in trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.