Fwd: OFBiz and Camel integration updated

[grv]

Moving it to DEV list. My apologies if it is a nuisance.

I have attached plugin tar to the ticket for everybody to take a look at.
Please review and try to run the plug-in and see if there is any issue with
it.

Best,
Girish

--------- Forwarded message ---------
From: Girish Vasmatkar <[hidden email]>
Date: Mon, Aug 5, 2019 at 9:38 PM
Subject: Re: OFBiz and Camel integration updated
To: ofbizuser <[hidden email]>


I've created OFBIZ-11147 <https://issues.apache.org/jira/browse/OFBIZ-11147> to
track camel integration. I will provide the plug in along with relevant
details.

Best,
Girish

On Sat, Aug 3, 2019 at 5:07 PM Mathieu Lirzin <[hidden email]>
wrote:

> Hello,
>
> Girish Vasmatkar <[hidden email]> writes:
>
> > Thanks Bilgin for taking care of pull request. If everyone is okay with
> the
> > changes, I will go ahead and create a ticket for the same to add it as an
> > ofbiz plugin. Let me know of any issues or concerns anyone may have.
> >
> > While writing a few test cases for the various camel components (and I am
> > using CamelTestSupport), it turned out OFBiz test container does not pick
> > them up because it is still based on inheritance (extending TestCase) and
> > not on annotation (any class with @Test annotated methods). I will
> probably
> > elaborate further in a separate thread, but I feel we need to add support
> > for considering such classes as part of test suite as well. We are using
> > JUnit 4 but it is hardly being used except for being available on the
> > classpath. Using JUnit 4 classes will make sure both mechanisms will be
> > supported.
>
> Supporting the JUnit4 runner API which make use of annotations would be
> nice if it helps improving the *sad* state of OFBiz integration tests in
> term of error reporting.
>
> For the record Junit4 annotations are already supported by OFBiz unit
> tests run by ‘./gradlew test’ which by the way should be preferred over
> integration tests in most cases because they run faster.
>
> As a side note, please avoid cross-posting to ‘devel’ and ‘user’ mailing
> lists.
>
> Thanks.
>
> --
> Mathieu Lirzin
> GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37
>

[Bilgin Ibryam-2]

hi all,

I will not have time to work on integrating the repo into Ofbiz, but if
anybody wants to do it, feel free to do so.
Use the code in my repo as you wish.

Bilgin


On Wed, Aug 14, 2019 at 1:46 PM Girish Vasmatkar <
[hidden email]> wrote:

> Moving it to DEV list. My apologies if it is a nuisance.
>
> I have attached plugin tar to the ticket for everybody to take a look at.
> Please review and try to run the plug-in and see if there is any issue with
> it.
>
> Best,
> Girish
>
> --------- Forwarded message ---------
> From: Girish Vasmatkar <[hidden email]>
> Date: Mon, Aug 5, 2019 at 9:38 PM
> Subject: Re: OFBiz and Camel integration updated
> To: ofbizuser <[hidden email]>
>
>
> I've created OFBIZ-11147 <
> https://issues.apache.org/jira/browse/OFBIZ-11147> to
> track camel integration. I will provide the plug in along with relevant
> details.
>
> Best,
> Girish
>
> On Sat, Aug 3, 2019 at 5:07 PM Mathieu Lirzin <[hidden email]>
> wrote:
>
> > Hello,
> >
> > Girish Vasmatkar <[hidden email]> writes:
> >
> > > Thanks Bilgin for taking care of pull request. If everyone is okay with
> > the
> > > changes, I will go ahead and create a ticket for the same to add it as
> an
> > > ofbiz plugin. Let me know of any issues or concerns anyone may have.
> > >
> > > While writing a few test cases for the various camel components (and I
> am
> > > using CamelTestSupport), it turned out OFBiz test container does not
> pick
> > > them up because it is still based on inheritance (extending TestCase)
> and
> > > not on annotation (any class with @Test annotated methods). I will
> > probably
> > > elaborate further in a separate thread, but I feel we need to add
> support
> > > for considering such classes as part of test suite as well. We are
> using
> > > JUnit 4 but it is hardly being used except for being available on the
> > > classpath. Using JUnit 4 classes will make sure both mechanisms will be
> > > supported.
> >
> > Supporting the JUnit4 runner API which make use of annotations would be
> > nice if it helps improving the *sad* state of OFBiz integration tests in
> > term of error reporting.
> >
> > For the record Junit4 annotations are already supported by OFBiz unit
> > tests run by ‘./gradlew test’ which by the way should be preferred over
> > integration tests in most cases because they run faster.
> >
> > As a side note, please avoid cross-posting to ‘devel’ and ‘user’ mailing
> > lists.
> >
> > Thanks.
> >
> > --
> > Mathieu Lirzin
> > GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37
> >
>

--
Bilgin Ibryam
ASF Member | Architect at Red Hat
http://ofbizian.com | @bibryam <https://twitter.com/bibryam>

Kubernetes Patterns http://shop.oreilly.com/product/0636920242598.do
Camel Design Patterns https://leanpub.com/camel-design-patterns