You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by James Carman <ja...@carmanconsulting.com> on 2016/11/21 18:03:09 UTC
[ANNOUNCE] Introducing Microbule...
We've been working on a Microservices framework called "Microbule" which
leverages CXF and Karaf (hence the cross-post):
https://github.com/jwcarman/microbule
The idea is to make writing Microservices easy and fun, by providing many
of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
transformation, validation, etc.). There's a README page that explains how
to install/run Microbule in Karaf and how to write your own services. If
you're interested, take it for a spin and let us know what you think.
Thanks,
James
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
FYI, Microbule has now moved:
https://microbule.github.io/microbule/
On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
wrote:
> We've been working on a Microservices framework called "Microbule" which
> leverages CXF and Karaf (hence the cross-post):
>
> https://github.com/jwcarman/microbule
>
> The idea is to make writing Microservices easy and fun, by providing many
> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> transformation, validation, etc.). There's a README page that explains how
> to install/run Microbule in Karaf and how to write your own services. If
> you're interested, take it for a spin and let us know what you think.
>
> Thanks,
>
> James
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
Wow, bootstrapping Meecrowave is pretty simple! Nice work! I think I
might need to bug you guys to beef up my CDI example (and convert it to
OWB)!
On Mon, Nov 21, 2016 at 5:01 PM Romain Manni-Bucau <rm...@gmail.com>
wrote:
> super badly done website (pushed without fixing root context) but raw old
> draft (before renaming mi to mee) was here
> http://people.apache.org/~rmannibucau/microwave-snapshot/
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-11-21 22:49 GMT+01:00 Mark Struberg <st...@yahoo.de.invalid>:
>
> https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/
>
>
> Currently you need to manually compile the CXF 3.1.x-fixes branch first.
>
>
> Usage: just write an Appliaction and @ApplicationScoped @Path bean and add
> the meecrowave-maven-plugin
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.meecrowave</groupId>
> <artifactId>meecrowave-maven-plugin</artifactId>
> <version>${meecrowave.version}</version>
> </plugin>
> </plugins>
> </build>
>
> Then start with
>
> $> mvn clean install meecrowave:run
>
> Will push a sample project soon.
>
> LieGrue,
> strub
>
> > Am 21.11.2016 um 22:41 schrieb James Carman <james@carmanconsulting.com
> >:
> >
> > I couldn't find anything on Meecrowave, but I would be interested in
> seeing the code. Where does it live? I tried googling
> >
> > On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin <sb...@gmail.com>
> wrote:
> > Hi James
> >
> > Looks very promising, and I found the answer to the question I was about
> > to ask in a "What's in a Name" section at the end :-)
> >
> > Microbule, Meecrowave - the massive wave is coming :-)
> >
> > Cheers, Sergey
> >
> >
> > On 21/11/16 18:11, James Carman wrote:
> > > The header names are configurable, so you can use whatever you want.
> You
> > > just need to set up an etc/org.microbule.decorator.tracer.cfg file:
> > >
> > > traceIdHeader=My-Trace-ID
> > > requestIdHeader=My-Request-ID
> > >
> > >
> > >
> > > On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > > wrote:
> > >
> > >> Hi James,
> > >>
> > >> Would it be an option to extract the tracer - at least the names of
> the
> > >> headers - to a "portable" module? With Mark we were on that area as
> well
> > >> for meecrowave (a microprofile server based on CXF too and hosted
> > >> @openwebbeans) and was thinking to add it to sirona since it is the
> > >> monitoring related ASF project. Would be great to make the
> names/format
> > >> uniform accross impl otherwise inteoperability is hard and this
> feature
> > >> loose some of its strength.
> > >>
> > >> wdyt?
> > >>
> > >> PS: sure we can share more but this would at least enable a
> > >> microbule-meecrowave cluster to speak the same language ;)
> > >>
> > >>
> > >>
> > >> Romain Manni-Bucau
> > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > >> <http://rmannibucau.wordpress.com> | Github <
> > >> https://github.com/rmannibucau> |
> > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > >> <https://javaeefactory-rmannibucau.rhcloud.com>
> > >>
> > >> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> > >>
> > >>> We've been working on a Microservices framework called "Microbule"
> which
> > >>> leverages CXF and Karaf (hence the cross-post):
> > >>>
> > >>> https://github.com/jwcarman/microbule
> > >>>
> > >>> The idea is to make writing Microservices easy and fun, by providing
> many
> > >>> of the oft-requested features for you out-of-the-box (CORS, Caching,
> JSON
> > >>> transformation, validation, etc.). There's a README page that
> explains
> > >> how
> > >>> to install/run Microbule in Karaf and how to write your own
> services. If
> > >>> you're interested, take it for a spin and let us know what you think.
> > >>>
> > >>> Thanks,
> > >>>
> > >>> James
> > >>>
> > >>
> > >
> >
>
>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
Wow, bootstrapping Meecrowave is pretty simple! Nice work! I think I
might need to bug you guys to beef up my CDI example (and convert it to
OWB)!
On Mon, Nov 21, 2016 at 5:01 PM Romain Manni-Bucau <rm...@gmail.com>
wrote:
> super badly done website (pushed without fixing root context) but raw old
> draft (before renaming mi to mee) was here
> http://people.apache.org/~rmannibucau/microwave-snapshot/
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-11-21 22:49 GMT+01:00 Mark Struberg <st...@yahoo.de.invalid>:
>
> https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/
>
>
> Currently you need to manually compile the CXF 3.1.x-fixes branch first.
>
>
> Usage: just write an Appliaction and @ApplicationScoped @Path bean and add
> the meecrowave-maven-plugin
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.meecrowave</groupId>
> <artifactId>meecrowave-maven-plugin</artifactId>
> <version>${meecrowave.version}</version>
> </plugin>
> </plugins>
> </build>
>
> Then start with
>
> $> mvn clean install meecrowave:run
>
> Will push a sample project soon.
>
> LieGrue,
> strub
>
> > Am 21.11.2016 um 22:41 schrieb James Carman <james@carmanconsulting.com
> >:
> >
> > I couldn't find anything on Meecrowave, but I would be interested in
> seeing the code. Where does it live? I tried googling
> >
> > On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin <sb...@gmail.com>
> wrote:
> > Hi James
> >
> > Looks very promising, and I found the answer to the question I was about
> > to ask in a "What's in a Name" section at the end :-)
> >
> > Microbule, Meecrowave - the massive wave is coming :-)
> >
> > Cheers, Sergey
> >
> >
> > On 21/11/16 18:11, James Carman wrote:
> > > The header names are configurable, so you can use whatever you want.
> You
> > > just need to set up an etc/org.microbule.decorator.tracer.cfg file:
> > >
> > > traceIdHeader=My-Trace-ID
> > > requestIdHeader=My-Request-ID
> > >
> > >
> > >
> > > On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > > wrote:
> > >
> > >> Hi James,
> > >>
> > >> Would it be an option to extract the tracer - at least the names of
> the
> > >> headers - to a "portable" module? With Mark we were on that area as
> well
> > >> for meecrowave (a microprofile server based on CXF too and hosted
> > >> @openwebbeans) and was thinking to add it to sirona since it is the
> > >> monitoring related ASF project. Would be great to make the
> names/format
> > >> uniform accross impl otherwise inteoperability is hard and this
> feature
> > >> loose some of its strength.
> > >>
> > >> wdyt?
> > >>
> > >> PS: sure we can share more but this would at least enable a
> > >> microbule-meecrowave cluster to speak the same language ;)
> > >>
> > >>
> > >>
> > >> Romain Manni-Bucau
> > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > >> <http://rmannibucau.wordpress.com> | Github <
> > >> https://github.com/rmannibucau> |
> > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > >> <https://javaeefactory-rmannibucau.rhcloud.com>
> > >>
> > >> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> > >>
> > >>> We've been working on a Microservices framework called "Microbule"
> which
> > >>> leverages CXF and Karaf (hence the cross-post):
> > >>>
> > >>> https://github.com/jwcarman/microbule
> > >>>
> > >>> The idea is to make writing Microservices easy and fun, by providing
> many
> > >>> of the oft-requested features for you out-of-the-box (CORS, Caching,
> JSON
> > >>> transformation, validation, etc.). There's a README page that
> explains
> > >> how
> > >>> to install/run Microbule in Karaf and how to write your own
> services. If
> > >>> you're interested, take it for a spin and let us know what you think.
> > >>>
> > >>> Thanks,
> > >>>
> > >>> James
> > >>>
> > >>
> > >
> >
>
>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Romain Manni-Bucau <rm...@gmail.com>.
super badly done website (pushed without fixing root context) but raw old
draft (before renaming mi to mee) was here
http://people.apache.org/~rmannibucau/microwave-snapshot/
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
2016-11-21 22:49 GMT+01:00 Mark Struberg <st...@yahoo.de.invalid>:
> https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/
>
>
> Currently you need to manually compile the CXF 3.1.x-fixes branch first.
>
>
> Usage: just write an Appliaction and @ApplicationScoped @Path bean and add
> the meecrowave-maven-plugin
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.meecrowave</groupId>
> <artifactId>meecrowave-maven-plugin</artifactId>
> <version>${meecrowave.version}</version>
> </plugin>
> </plugins>
> </build>
>
> Then start with
>
> $> mvn clean install meecrowave:run
>
> Will push a sample project soon.
>
> LieGrue,
> strub
>
> > Am 21.11.2016 um 22:41 schrieb James Carman <james@carmanconsulting.com
> >:
> >
> > I couldn't find anything on Meecrowave, but I would be interested in
> seeing the code. Where does it live? I tried googling
> >
> > On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin <sb...@gmail.com>
> wrote:
> > Hi James
> >
> > Looks very promising, and I found the answer to the question I was about
> > to ask in a "What's in a Name" section at the end :-)
> >
> > Microbule, Meecrowave - the massive wave is coming :-)
> >
> > Cheers, Sergey
> >
> >
> > On 21/11/16 18:11, James Carman wrote:
> > > The header names are configurable, so you can use whatever you want.
> You
> > > just need to set up an etc/org.microbule.decorator.tracer.cfg file:
> > >
> > > traceIdHeader=My-Trace-ID
> > > requestIdHeader=My-Request-ID
> > >
> > >
> > >
> > > On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > > wrote:
> > >
> > >> Hi James,
> > >>
> > >> Would it be an option to extract the tracer - at least the names of
> the
> > >> headers - to a "portable" module? With Mark we were on that area as
> well
> > >> for meecrowave (a microprofile server based on CXF too and hosted
> > >> @openwebbeans) and was thinking to add it to sirona since it is the
> > >> monitoring related ASF project. Would be great to make the
> names/format
> > >> uniform accross impl otherwise inteoperability is hard and this
> feature
> > >> loose some of its strength.
> > >>
> > >> wdyt?
> > >>
> > >> PS: sure we can share more but this would at least enable a
> > >> microbule-meecrowave cluster to speak the same language ;)
> > >>
> > >>
> > >>
> > >> Romain Manni-Bucau
> > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > >> <http://rmannibucau.wordpress.com> | Github <
> > >> https://github.com/rmannibucau> |
> > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > >> <https://javaeefactory-rmannibucau.rhcloud.com>
> > >>
> > >> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> > >>
> > >>> We've been working on a Microservices framework called "Microbule"
> which
> > >>> leverages CXF and Karaf (hence the cross-post):
> > >>>
> > >>> https://github.com/jwcarman/microbule
> > >>>
> > >>> The idea is to make writing Microservices easy and fun, by providing
> many
> > >>> of the oft-requested features for you out-of-the-box (CORS, Caching,
> JSON
> > >>> transformation, validation, etc.). There's a README page that
> explains
> > >> how
> > >>> to install/run Microbule in Karaf and how to write your own
> services. If
> > >>> you're interested, take it for a spin and let us know what you think.
> > >>>
> > >>> Thanks,
> > >>>
> > >>> James
> > >>>
> > >>
> > >
> >
>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
Very cool, Mark! I will check it out. Looks like it's focusing on Tomcat
mostly at first glance. Is that right?
On Mon, Nov 21, 2016 at 4:49 PM Mark Struberg <st...@yahoo.de> wrote:
> https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/
>
>
> Currently you need to manually compile the CXF 3.1.x-fixes branch first.
>
>
> Usage: just write an Appliaction and @ApplicationScoped @Path bean and add
> the meecrowave-maven-plugin
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.meecrowave</groupId>
> <artifactId>meecrowave-maven-plugin</artifactId>
> <version>${meecrowave.version}</version>
> </plugin>
> </plugins>
> </build>
>
> Then start with
>
> $> mvn clean install meecrowave:run
>
> Will push a sample project soon.
>
> LieGrue,
> strub
>
> > Am 21.11.2016 um 22:41 schrieb James Carman <james@carmanconsulting.com
> >:
> >
> > I couldn't find anything on Meecrowave, but I would be interested in
> seeing the code. Where does it live? I tried googling
> >
> > On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin <sb...@gmail.com>
> wrote:
> > Hi James
> >
> > Looks very promising, and I found the answer to the question I was about
> > to ask in a "What's in a Name" section at the end :-)
> >
> > Microbule, Meecrowave - the massive wave is coming :-)
> >
> > Cheers, Sergey
> >
> >
> > On 21/11/16 18:11, James Carman wrote:
> > > The header names are configurable, so you can use whatever you want.
> You
> > > just need to set up an etc/org.microbule.decorator.tracer.cfg file:
> > >
> > > traceIdHeader=My-Trace-ID
> > > requestIdHeader=My-Request-ID
> > >
> > >
> > >
> > > On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > > wrote:
> > >
> > >> Hi James,
> > >>
> > >> Would it be an option to extract the tracer - at least the names of
> the
> > >> headers - to a "portable" module? With Mark we were on that area as
> well
> > >> for meecrowave (a microprofile server based on CXF too and hosted
> > >> @openwebbeans) and was thinking to add it to sirona since it is the
> > >> monitoring related ASF project. Would be great to make the
> names/format
> > >> uniform accross impl otherwise inteoperability is hard and this
> feature
> > >> loose some of its strength.
> > >>
> > >> wdyt?
> > >>
> > >> PS: sure we can share more but this would at least enable a
> > >> microbule-meecrowave cluster to speak the same language ;)
> > >>
> > >>
> > >>
> > >> Romain Manni-Bucau
> > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > >> <http://rmannibucau.wordpress.com> | Github <
> > >> https://github.com/rmannibucau> |
> > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > >> <https://javaeefactory-rmannibucau.rhcloud.com>
> > >>
> > >> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> > >>
> > >>> We've been working on a Microservices framework called "Microbule"
> which
> > >>> leverages CXF and Karaf (hence the cross-post):
> > >>>
> > >>> https://github.com/jwcarman/microbule
> > >>>
> > >>> The idea is to make writing Microservices easy and fun, by providing
> many
> > >>> of the oft-requested features for you out-of-the-box (CORS, Caching,
> JSON
> > >>> transformation, validation, etc.). There's a README page that
> explains
> > >> how
> > >>> to install/run Microbule in Karaf and how to write your own
> services. If
> > >>> you're interested, take it for a spin and let us know what you think.
> > >>>
> > >>> Thanks,
> > >>>
> > >>> James
> > >>>
> > >>
> > >
> >
>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Romain Manni-Bucau <rm...@gmail.com>.
super badly done website (pushed without fixing root context) but raw old
draft (before renaming mi to mee) was here
http://people.apache.org/~rmannibucau/microwave-snapshot/
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
2016-11-21 22:49 GMT+01:00 Mark Struberg <st...@yahoo.de.invalid>:
> https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/
>
>
> Currently you need to manually compile the CXF 3.1.x-fixes branch first.
>
>
> Usage: just write an Appliaction and @ApplicationScoped @Path bean and add
> the meecrowave-maven-plugin
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.meecrowave</groupId>
> <artifactId>meecrowave-maven-plugin</artifactId>
> <version>${meecrowave.version}</version>
> </plugin>
> </plugins>
> </build>
>
> Then start with
>
> $> mvn clean install meecrowave:run
>
> Will push a sample project soon.
>
> LieGrue,
> strub
>
> > Am 21.11.2016 um 22:41 schrieb James Carman <james@carmanconsulting.com
> >:
> >
> > I couldn't find anything on Meecrowave, but I would be interested in
> seeing the code. Where does it live? I tried googling
> >
> > On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin <sb...@gmail.com>
> wrote:
> > Hi James
> >
> > Looks very promising, and I found the answer to the question I was about
> > to ask in a "What's in a Name" section at the end :-)
> >
> > Microbule, Meecrowave - the massive wave is coming :-)
> >
> > Cheers, Sergey
> >
> >
> > On 21/11/16 18:11, James Carman wrote:
> > > The header names are configurable, so you can use whatever you want.
> You
> > > just need to set up an etc/org.microbule.decorator.tracer.cfg file:
> > >
> > > traceIdHeader=My-Trace-ID
> > > requestIdHeader=My-Request-ID
> > >
> > >
> > >
> > > On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > > wrote:
> > >
> > >> Hi James,
> > >>
> > >> Would it be an option to extract the tracer - at least the names of
> the
> > >> headers - to a "portable" module? With Mark we were on that area as
> well
> > >> for meecrowave (a microprofile server based on CXF too and hosted
> > >> @openwebbeans) and was thinking to add it to sirona since it is the
> > >> monitoring related ASF project. Would be great to make the
> names/format
> > >> uniform accross impl otherwise inteoperability is hard and this
> feature
> > >> loose some of its strength.
> > >>
> > >> wdyt?
> > >>
> > >> PS: sure we can share more but this would at least enable a
> > >> microbule-meecrowave cluster to speak the same language ;)
> > >>
> > >>
> > >>
> > >> Romain Manni-Bucau
> > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > >> <http://rmannibucau.wordpress.com> | Github <
> > >> https://github.com/rmannibucau> |
> > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > >> <https://javaeefactory-rmannibucau.rhcloud.com>
> > >>
> > >> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> > >>
> > >>> We've been working on a Microservices framework called "Microbule"
> which
> > >>> leverages CXF and Karaf (hence the cross-post):
> > >>>
> > >>> https://github.com/jwcarman/microbule
> > >>>
> > >>> The idea is to make writing Microservices easy and fun, by providing
> many
> > >>> of the oft-requested features for you out-of-the-box (CORS, Caching,
> JSON
> > >>> transformation, validation, etc.). There's a README page that
> explains
> > >> how
> > >>> to install/run Microbule in Karaf and how to write your own
> services. If
> > >>> you're interested, take it for a spin and let us know what you think.
> > >>>
> > >>> Thanks,
> > >>>
> > >>> James
> > >>>
> > >>
> > >
> >
>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
Very cool, Mark! I will check it out. Looks like it's focusing on Tomcat
mostly at first glance. Is that right?
On Mon, Nov 21, 2016 at 4:49 PM Mark Struberg <st...@yahoo.de> wrote:
> https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/
>
>
> Currently you need to manually compile the CXF 3.1.x-fixes branch first.
>
>
> Usage: just write an Appliaction and @ApplicationScoped @Path bean and add
> the meecrowave-maven-plugin
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.meecrowave</groupId>
> <artifactId>meecrowave-maven-plugin</artifactId>
> <version>${meecrowave.version}</version>
> </plugin>
> </plugins>
> </build>
>
> Then start with
>
> $> mvn clean install meecrowave:run
>
> Will push a sample project soon.
>
> LieGrue,
> strub
>
> > Am 21.11.2016 um 22:41 schrieb James Carman <james@carmanconsulting.com
> >:
> >
> > I couldn't find anything on Meecrowave, but I would be interested in
> seeing the code. Where does it live? I tried googling
> >
> > On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin <sb...@gmail.com>
> wrote:
> > Hi James
> >
> > Looks very promising, and I found the answer to the question I was about
> > to ask in a "What's in a Name" section at the end :-)
> >
> > Microbule, Meecrowave - the massive wave is coming :-)
> >
> > Cheers, Sergey
> >
> >
> > On 21/11/16 18:11, James Carman wrote:
> > > The header names are configurable, so you can use whatever you want.
> You
> > > just need to set up an etc/org.microbule.decorator.tracer.cfg file:
> > >
> > > traceIdHeader=My-Trace-ID
> > > requestIdHeader=My-Request-ID
> > >
> > >
> > >
> > > On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > > wrote:
> > >
> > >> Hi James,
> > >>
> > >> Would it be an option to extract the tracer - at least the names of
> the
> > >> headers - to a "portable" module? With Mark we were on that area as
> well
> > >> for meecrowave (a microprofile server based on CXF too and hosted
> > >> @openwebbeans) and was thinking to add it to sirona since it is the
> > >> monitoring related ASF project. Would be great to make the
> names/format
> > >> uniform accross impl otherwise inteoperability is hard and this
> feature
> > >> loose some of its strength.
> > >>
> > >> wdyt?
> > >>
> > >> PS: sure we can share more but this would at least enable a
> > >> microbule-meecrowave cluster to speak the same language ;)
> > >>
> > >>
> > >>
> > >> Romain Manni-Bucau
> > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > >> <http://rmannibucau.wordpress.com> | Github <
> > >> https://github.com/rmannibucau> |
> > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > >> <https://javaeefactory-rmannibucau.rhcloud.com>
> > >>
> > >> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> > >>
> > >>> We've been working on a Microservices framework called "Microbule"
> which
> > >>> leverages CXF and Karaf (hence the cross-post):
> > >>>
> > >>> https://github.com/jwcarman/microbule
> > >>>
> > >>> The idea is to make writing Microservices easy and fun, by providing
> many
> > >>> of the oft-requested features for you out-of-the-box (CORS, Caching,
> JSON
> > >>> transformation, validation, etc.). There's a README page that
> explains
> > >> how
> > >>> to install/run Microbule in Karaf and how to write your own
> services. If
> > >>> you're interested, take it for a spin and let us know what you think.
> > >>>
> > >>> Thanks,
> > >>>
> > >>> James
> > >>>
> > >>
> > >
> >
>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/
Currently you need to manually compile the CXF 3.1.x-fixes branch first.
Usage: just write an Appliaction and @ApplicationScoped @Path bean and add the meecrowave-maven-plugin
<build>
<plugins>
<plugin>
<groupId>org.apache.meecrowave</groupId>
<artifactId>meecrowave-maven-plugin</artifactId>
<version>${meecrowave.version}</version>
</plugin>
</plugins>
</build>
Then start with
$> mvn clean install meecrowave:run
Will push a sample project soon.
LieGrue,
strub
> Am 21.11.2016 um 22:41 schrieb James Carman <ja...@carmanconsulting.com>:
>
> I couldn't find anything on Meecrowave, but I would be interested in seeing the code. Where does it live? I tried googling
>
> On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin <sb...@gmail.com> wrote:
> Hi James
>
> Looks very promising, and I found the answer to the question I was about
> to ask in a "What's in a Name" section at the end :-)
>
> Microbule, Meecrowave - the massive wave is coming :-)
>
> Cheers, Sergey
>
>
> On 21/11/16 18:11, James Carman wrote:
> > The header names are configurable, so you can use whatever you want. You
> > just need to set up an etc/org.microbule.decorator.tracer.cfg file:
> >
> > traceIdHeader=My-Trace-ID
> > requestIdHeader=My-Request-ID
> >
> >
> >
> > On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> >
> >> Hi James,
> >>
> >> Would it be an option to extract the tracer - at least the names of the
> >> headers - to a "portable" module? With Mark we were on that area as well
> >> for meecrowave (a microprofile server based on CXF too and hosted
> >> @openwebbeans) and was thinking to add it to sirona since it is the
> >> monitoring related ASF project. Would be great to make the names/format
> >> uniform accross impl otherwise inteoperability is hard and this feature
> >> loose some of its strength.
> >>
> >> wdyt?
> >>
> >> PS: sure we can share more but this would at least enable a
> >> microbule-meecrowave cluster to speak the same language ;)
> >>
> >>
> >>
> >> Romain Manni-Bucau
> >> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> >> <http://rmannibucau.wordpress.com> | Github <
> >> https://github.com/rmannibucau> |
> >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> >> <https://javaeefactory-rmannibucau.rhcloud.com>
> >>
> >> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> >>
> >>> We've been working on a Microservices framework called "Microbule" which
> >>> leverages CXF and Karaf (hence the cross-post):
> >>>
> >>> https://github.com/jwcarman/microbule
> >>>
> >>> The idea is to make writing Microservices easy and fun, by providing many
> >>> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> >>> transformation, validation, etc.). There's a README page that explains
> >> how
> >>> to install/run Microbule in Karaf and how to write your own services. If
> >>> you're interested, take it for a spin and let us know what you think.
> >>>
> >>> Thanks,
> >>>
> >>> James
> >>>
> >>
> >
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/
Currently you need to manually compile the CXF 3.1.x-fixes branch first.
Usage: just write an Appliaction and @ApplicationScoped @Path bean and add the meecrowave-maven-plugin
<build>
<plugins>
<plugin>
<groupId>org.apache.meecrowave</groupId>
<artifactId>meecrowave-maven-plugin</artifactId>
<version>${meecrowave.version}</version>
</plugin>
</plugins>
</build>
Then start with
$> mvn clean install meecrowave:run
Will push a sample project soon.
LieGrue,
strub
> Am 21.11.2016 um 22:41 schrieb James Carman <ja...@carmanconsulting.com>:
>
> I couldn't find anything on Meecrowave, but I would be interested in seeing the code. Where does it live? I tried googling
>
> On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin <sb...@gmail.com> wrote:
> Hi James
>
> Looks very promising, and I found the answer to the question I was about
> to ask in a "What's in a Name" section at the end :-)
>
> Microbule, Meecrowave - the massive wave is coming :-)
>
> Cheers, Sergey
>
>
> On 21/11/16 18:11, James Carman wrote:
> > The header names are configurable, so you can use whatever you want. You
> > just need to set up an etc/org.microbule.decorator.tracer.cfg file:
> >
> > traceIdHeader=My-Trace-ID
> > requestIdHeader=My-Request-ID
> >
> >
> >
> > On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <rm...@gmail.com>
> > wrote:
> >
> >> Hi James,
> >>
> >> Would it be an option to extract the tracer - at least the names of the
> >> headers - to a "portable" module? With Mark we were on that area as well
> >> for meecrowave (a microprofile server based on CXF too and hosted
> >> @openwebbeans) and was thinking to add it to sirona since it is the
> >> monitoring related ASF project. Would be great to make the names/format
> >> uniform accross impl otherwise inteoperability is hard and this feature
> >> loose some of its strength.
> >>
> >> wdyt?
> >>
> >> PS: sure we can share more but this would at least enable a
> >> microbule-meecrowave cluster to speak the same language ;)
> >>
> >>
> >>
> >> Romain Manni-Bucau
> >> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> >> <http://rmannibucau.wordpress.com> | Github <
> >> https://github.com/rmannibucau> |
> >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> >> <https://javaeefactory-rmannibucau.rhcloud.com>
> >>
> >> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> >>
> >>> We've been working on a Microservices framework called "Microbule" which
> >>> leverages CXF and Karaf (hence the cross-post):
> >>>
> >>> https://github.com/jwcarman/microbule
> >>>
> >>> The idea is to make writing Microservices easy and fun, by providing many
> >>> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> >>> transformation, validation, etc.). There's a README page that explains
> >> how
> >>> to install/run Microbule in Karaf and how to write your own services. If
> >>> you're interested, take it for a spin and let us know what you think.
> >>>
> >>> Thanks,
> >>>
> >>> James
> >>>
> >>
> >
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
I couldn't find anything on Meecrowave, but I would be interested in seeing
the code. Where does it live? I tried googling
On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin <sb...@gmail.com>
wrote:
> Hi James
>
> Looks very promising, and I found the answer to the question I was about
> to ask in a "What's in a Name" section at the end :-)
>
> Microbule, Meecrowave - the massive wave is coming :-)
>
> Cheers, Sergey
>
>
> On 21/11/16 18:11, James Carman wrote:
> > The header names are configurable, so you can use whatever you want. You
> > just need to set up an etc/org.microbule.decorator.tracer.cfg file:
> >
> > traceIdHeader=My-Trace-ID
> > requestIdHeader=My-Request-ID
> >
> >
> >
> > On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > wrote:
> >
> >> Hi James,
> >>
> >> Would it be an option to extract the tracer - at least the names of the
> >> headers - to a "portable" module? With Mark we were on that area as well
> >> for meecrowave (a microprofile server based on CXF too and hosted
> >> @openwebbeans) and was thinking to add it to sirona since it is the
> >> monitoring related ASF project. Would be great to make the names/format
> >> uniform accross impl otherwise inteoperability is hard and this feature
> >> loose some of its strength.
> >>
> >> wdyt?
> >>
> >> PS: sure we can share more but this would at least enable a
> >> microbule-meecrowave cluster to speak the same language ;)
> >>
> >>
> >>
> >> Romain Manni-Bucau
> >> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> >> <http://rmannibucau.wordpress.com> | Github <
> >> https://github.com/rmannibucau> |
> >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> >> <https://javaeefactory-rmannibucau.rhcloud.com>
> >>
> >> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> >>
> >>> We've been working on a Microservices framework called "Microbule"
> which
> >>> leverages CXF and Karaf (hence the cross-post):
> >>>
> >>> https://github.com/jwcarman/microbule
> >>>
> >>> The idea is to make writing Microservices easy and fun, by providing
> many
> >>> of the oft-requested features for you out-of-the-box (CORS, Caching,
> JSON
> >>> transformation, validation, etc.). There's a README page that explains
> >> how
> >>> to install/run Microbule in Karaf and how to write your own services.
> If
> >>> you're interested, take it for a spin and let us know what you think.
> >>>
> >>> Thanks,
> >>>
> >>> James
> >>>
> >>
> >
>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
I couldn't find anything on Meecrowave, but I would be interested in seeing
the code. Where does it live? I tried googling
On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin <sb...@gmail.com>
wrote:
> Hi James
>
> Looks very promising, and I found the answer to the question I was about
> to ask in a "What's in a Name" section at the end :-)
>
> Microbule, Meecrowave - the massive wave is coming :-)
>
> Cheers, Sergey
>
>
> On 21/11/16 18:11, James Carman wrote:
> > The header names are configurable, so you can use whatever you want. You
> > just need to set up an etc/org.microbule.decorator.tracer.cfg file:
> >
> > traceIdHeader=My-Trace-ID
> > requestIdHeader=My-Request-ID
> >
> >
> >
> > On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > wrote:
> >
> >> Hi James,
> >>
> >> Would it be an option to extract the tracer - at least the names of the
> >> headers - to a "portable" module? With Mark we were on that area as well
> >> for meecrowave (a microprofile server based on CXF too and hosted
> >> @openwebbeans) and was thinking to add it to sirona since it is the
> >> monitoring related ASF project. Would be great to make the names/format
> >> uniform accross impl otherwise inteoperability is hard and this feature
> >> loose some of its strength.
> >>
> >> wdyt?
> >>
> >> PS: sure we can share more but this would at least enable a
> >> microbule-meecrowave cluster to speak the same language ;)
> >>
> >>
> >>
> >> Romain Manni-Bucau
> >> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> >> <http://rmannibucau.wordpress.com> | Github <
> >> https://github.com/rmannibucau> |
> >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> >> <https://javaeefactory-rmannibucau.rhcloud.com>
> >>
> >> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> >>
> >>> We've been working on a Microservices framework called "Microbule"
> which
> >>> leverages CXF and Karaf (hence the cross-post):
> >>>
> >>> https://github.com/jwcarman/microbule
> >>>
> >>> The idea is to make writing Microservices easy and fun, by providing
> many
> >>> of the oft-requested features for you out-of-the-box (CORS, Caching,
> JSON
> >>> transformation, validation, etc.). There's a README page that explains
> >> how
> >>> to install/run Microbule in Karaf and how to write your own services.
> If
> >>> you're interested, take it for a spin and let us know what you think.
> >>>
> >>> Thanks,
> >>>
> >>> James
> >>>
> >>
> >
>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi James
Looks very promising, and I found the answer to the question I was about
to ask in a "What's in a Name" section at the end :-)
Microbule, Meecrowave - the massive wave is coming :-)
Cheers, Sergey
On 21/11/16 18:11, James Carman wrote:
> The header names are configurable, so you can use whatever you want. You
> just need to set up an etc/org.microbule.decorator.tracer.cfg file:
>
> traceIdHeader=My-Trace-ID
> requestIdHeader=My-Request-ID
>
>
>
> On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
>> Hi James,
>>
>> Would it be an option to extract the tracer - at least the names of the
>> headers - to a "portable" module? With Mark we were on that area as well
>> for meecrowave (a microprofile server based on CXF too and hosted
>> @openwebbeans) and was thinking to add it to sirona since it is the
>> monitoring related ASF project. Would be great to make the names/format
>> uniform accross impl otherwise inteoperability is hard and this feature
>> loose some of its strength.
>>
>> wdyt?
>>
>> PS: sure we can share more but this would at least enable a
>> microbule-meecrowave cluster to speak the same language ;)
>>
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://blog-rmannibucau.rhcloud.com> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github <
>> https://github.com/rmannibucau> |
>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
>> <https://javaeefactory-rmannibucau.rhcloud.com>
>>
>> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
>>
>>> We've been working on a Microservices framework called "Microbule" which
>>> leverages CXF and Karaf (hence the cross-post):
>>>
>>> https://github.com/jwcarman/microbule
>>>
>>> The idea is to make writing Microservices easy and fun, by providing many
>>> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
>>> transformation, validation, etc.). There's a README page that explains
>> how
>>> to install/run Microbule in Karaf and how to write your own services. If
>>> you're interested, take it for a spin and let us know what you think.
>>>
>>> Thanks,
>>>
>>> James
>>>
>>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi James
Looks very promising, and I found the answer to the question I was about
to ask in a "What's in a Name" section at the end :-)
Microbule, Meecrowave - the massive wave is coming :-)
Cheers, Sergey
On 21/11/16 18:11, James Carman wrote:
> The header names are configurable, so you can use whatever you want. You
> just need to set up an etc/org.microbule.decorator.tracer.cfg file:
>
> traceIdHeader=My-Trace-ID
> requestIdHeader=My-Request-ID
>
>
>
> On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
>> Hi James,
>>
>> Would it be an option to extract the tracer - at least the names of the
>> headers - to a "portable" module? With Mark we were on that area as well
>> for meecrowave (a microprofile server based on CXF too and hosted
>> @openwebbeans) and was thinking to add it to sirona since it is the
>> monitoring related ASF project. Would be great to make the names/format
>> uniform accross impl otherwise inteoperability is hard and this feature
>> loose some of its strength.
>>
>> wdyt?
>>
>> PS: sure we can share more but this would at least enable a
>> microbule-meecrowave cluster to speak the same language ;)
>>
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://blog-rmannibucau.rhcloud.com> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github <
>> https://github.com/rmannibucau> |
>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
>> <https://javaeefactory-rmannibucau.rhcloud.com>
>>
>> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
>>
>>> We've been working on a Microservices framework called "Microbule" which
>>> leverages CXF and Karaf (hence the cross-post):
>>>
>>> https://github.com/jwcarman/microbule
>>>
>>> The idea is to make writing Microservices easy and fun, by providing many
>>> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
>>> transformation, validation, etc.). There's a README page that explains
>> how
>>> to install/run Microbule in Karaf and how to write your own services. If
>>> you're interested, take it for a spin and let us know what you think.
>>>
>>> Thanks,
>>>
>>> James
>>>
>>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
The header names are configurable, so you can use whatever you want. You
just need to set up an etc/org.microbule.decorator.tracer.cfg file:
traceIdHeader=My-Trace-ID
requestIdHeader=My-Request-ID
On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <rm...@gmail.com>
wrote:
> Hi James,
>
> Would it be an option to extract the tracer - at least the names of the
> headers - to a "portable" module? With Mark we were on that area as well
> for meecrowave (a microprofile server based on CXF too and hosted
> @openwebbeans) and was thinking to add it to sirona since it is the
> monitoring related ASF project. Would be great to make the names/format
> uniform accross impl otherwise inteoperability is hard and this feature
> loose some of its strength.
>
> wdyt?
>
> PS: sure we can share more but this would at least enable a
> microbule-meecrowave cluster to speak the same language ;)
>
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
>
> > We've been working on a Microservices framework called "Microbule" which
> > leverages CXF and Karaf (hence the cross-post):
> >
> > https://github.com/jwcarman/microbule
> >
> > The idea is to make writing Microservices easy and fun, by providing many
> > of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> > transformation, validation, etc.). There's a README page that explains
> how
> > to install/run Microbule in Karaf and how to write your own services. If
> > you're interested, take it for a spin and let us know what you think.
> >
> > Thanks,
> >
> > James
> >
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
The header names are configurable, so you can use whatever you want. You
just need to set up an etc/org.microbule.decorator.tracer.cfg file:
traceIdHeader=My-Trace-ID
requestIdHeader=My-Request-ID
On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau <rm...@gmail.com>
wrote:
> Hi James,
>
> Would it be an option to extract the tracer - at least the names of the
> headers - to a "portable" module? With Mark we were on that area as well
> for meecrowave (a microprofile server based on CXF too and hosted
> @openwebbeans) and was thinking to add it to sirona since it is the
> monitoring related ASF project. Would be great to make the names/format
> uniform accross impl otherwise inteoperability is hard and this feature
> loose some of its strength.
>
> wdyt?
>
> PS: sure we can share more but this would at least enable a
> microbule-meecrowave cluster to speak the same language ;)
>
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
>
> > We've been working on a Microservices framework called "Microbule" which
> > leverages CXF and Karaf (hence the cross-post):
> >
> > https://github.com/jwcarman/microbule
> >
> > The idea is to make writing Microservices easy and fun, by providing many
> > of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> > transformation, validation, etc.). There's a README page that explains
> how
> > to install/run Microbule in Karaf and how to write your own services. If
> > you're interested, take it for a spin and let us know what you think.
> >
> > Thanks,
> >
> > James
> >
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi James,
Would it be an option to extract the tracer - at least the names of the
headers - to a "portable" module? With Mark we were on that area as well
for meecrowave (a microprofile server based on CXF too and hosted
@openwebbeans) and was thinking to add it to sirona since it is the
monitoring related ASF project. Would be great to make the names/format
uniform accross impl otherwise inteoperability is hard and this feature
loose some of its strength.
wdyt?
PS: sure we can share more but this would at least enable a
microbule-meecrowave cluster to speak the same language ;)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> We've been working on a Microservices framework called "Microbule" which
> leverages CXF and Karaf (hence the cross-post):
>
> https://github.com/jwcarman/microbule
>
> The idea is to make writing Microservices easy and fun, by providing many
> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> transformation, validation, etc.). There's a README page that explains how
> to install/run Microbule in Karaf and how to write your own services. If
> you're interested, take it for a spin and let us know what you think.
>
> Thanks,
>
> James
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I think blueprint is fine for now as it provides nice feature for microbule. I would evaluate DS\u2063\u200b as Christian suggested.
Regards
JB
On Nov 23, 2016, 13:58, at 13:58, James Carman <ja...@carmanconsulting.com> wrote:
>Yeah, I just used Blueprint because I'm more familiar with it at the
>moment. I want to make the code highly configurable, so I need to play
>with the configuration bits of DS and convert it. Another option is to
>just use BundleActivators to make very vanilla. Right now, Karaf is my
>target, because it has that "build your own container" aspect to it
>that I
>love. Any tips (or example) on converting stuff to DS would be greatly
>welcome! ;)
>
>
>On Wed, Nov 23, 2016 at 7:35 AM Christian Schneider
><ch...@die-schneider.net>
>wrote:
>
>> One thing about the implementation.
>> I noticed that microbule is using blueprint for its own setup.
>> I would switch this rather to DS as it has a smaller footprint.
>>
>> If someone is using microbule with DS then the blueprint overhead is
>> substantial.
>> If someone would use a DS based microbule with blueprint then the DS
>> overhead would be a lot smaller.
>>
>> Christian
>>
>> On 21.11.2016 19:03, James Carman wrote:
>> > We've been working on a Microservices framework called "Microbule"
>which
>> > leverages CXF and Karaf (hence the cross-post):
>> >
>> > https://github.com/jwcarman/microbule
>> >
>> > The idea is to make writing Microservices easy and fun, by
>providing many
>> > of the oft-requested features for you out-of-the-box (CORS,
>Caching, JSON
>> > transformation, validation, etc.). There's a README page that
>explains
>> how
>> > to install/run Microbule in Karaf and how to write your own
>services. If
>> > you're interested, take it for a spin and let us know what you
>think.
>> >
>> > Thanks,
>> >
>> > James
>> >
>>
>>
>> --
>> Christian Schneider
>> http://www.liquid-reality.de
>>
>> Open Source Architect
>> http://www.talend.com
>>
>>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
Yeah, I just used Blueprint because I'm more familiar with it at the
moment. I want to make the code highly configurable, so I need to play
with the configuration bits of DS and convert it. Another option is to
just use BundleActivators to make very vanilla. Right now, Karaf is my
target, because it has that "build your own container" aspect to it that I
love. Any tips (or example) on converting stuff to DS would be greatly
welcome! ;)
On Wed, Nov 23, 2016 at 7:35 AM Christian Schneider <ch...@die-schneider.net>
wrote:
> One thing about the implementation.
> I noticed that microbule is using blueprint for its own setup.
> I would switch this rather to DS as it has a smaller footprint.
>
> If someone is using microbule with DS then the blueprint overhead is
> substantial.
> If someone would use a DS based microbule with blueprint then the DS
> overhead would be a lot smaller.
>
> Christian
>
> On 21.11.2016 19:03, James Carman wrote:
> > We've been working on a Microservices framework called "Microbule" which
> > leverages CXF and Karaf (hence the cross-post):
> >
> > https://github.com/jwcarman/microbule
> >
> > The idea is to make writing Microservices easy and fun, by providing many
> > of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> > transformation, validation, etc.). There's a README page that explains
> how
> > to install/run Microbule in Karaf and how to write your own services. If
> > you're interested, take it for a spin and let us know what you think.
> >
> > Thanks,
> >
> > James
> >
>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Christian Schneider <ch...@die-schneider.net>.
One thing about the implementation.
I noticed that microbule is using blueprint for its own setup.
I would switch this rather to DS as it has a smaller footprint.
If someone is using microbule with DS then the blueprint overhead is
substantial.
If someone would use a DS based microbule with blueprint then the DS
overhead would be a lot smaller.
Christian
On 21.11.2016 19:03, James Carman wrote:
> We've been working on a Microservices framework called "Microbule" which
> leverages CXF and Karaf (hence the cross-post):
>
> https://github.com/jwcarman/microbule
>
> The idea is to make writing Microservices easy and fun, by providing many
> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> transformation, validation, etc.). There's a README page that explains how
> to install/run Microbule in Karaf and how to write your own services. If
> you're interested, take it for a spin and let us know what you think.
>
> Thanks,
>
> James
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
By the way, I should give credit to Benson Margulies for giving me the
"secret sauce" of creating CXF servers on-the-fly! Thanks, Benson!
On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
wrote:
> We've been working on a Microservices framework called "Microbule" which
> leverages CXF and Karaf (hence the cross-post):
>
> https://github.com/jwcarman/microbule
>
> The idea is to make writing Microservices easy and fun, by providing many
> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> transformation, validation, etc.). There's a README page that explains how
> to install/run Microbule in Karaf and how to write your own services. If
> you're interested, take it for a spin and let us know what you think.
>
> Thanks,
>
> James
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
Well, provided the right transport is there, you can use whatever "address"
you want when you create a server. It would just fire it up (as you've
seen in your code) for you. The Karaf version can just use relative
addresses since CXF is already fired up and listening on "/cxf" in the
container. So, if you just used Microbule outside of an OSGi container,
then you could do exactly as you're saying.
On Tue, Nov 22, 2016 at 3:55 PM Benson Margulies <bi...@gmail.com>
wrote:
> A small update with some irony here.
>
> At the job I just finished today, we reached the conclusion that we
> weren't getting much value out of Karaf and pax-web; no criticism
> intended, we just don't dynamically provision, and we don't need any
> HTTP except for CXF services. So, over the last few weeks, we
> refactored the thing to use cxf-rt-transport-http-jetty in the Felix
> container, with our own rather tiny class responsible for launching.
> We lost a bit of flexibility in that we can't create an endpoint
> 'inside' of the namespace of another endpoint, but otherwise it works
> just fine. The code that that I showed James is hardly changed at all.
> The endpoint addresses now look like
> "http://0.0.0.0:nnnnn/base/whatever" instead "/whatever". Maybe some
> day there will be an ultramicrobule that anticipates this mode of
> operation.
>
>
>
>
>
> On Mon, Nov 21, 2016 at 7:13 PM, James Carman
> <ja...@carmanconsulting.com> wrote:
> > Small update. Microbule 0.1.0 release has been cut and will soon be
> > available in Maven Central (awaiting sync from Nexus OSS). Enjoy, folks!
> >
> > On Mon, Nov 21, 2016 at 1:03 PM James Carman <james@carmanconsulting.com
> >
> > wrote:
> >
> >> We've been working on a Microservices framework called "Microbule" which
> >> leverages CXF and Karaf (hence the cross-post):
> >>
> >> https://github.com/jwcarman/microbule
> >>
> >> The idea is to make writing Microservices easy and fun, by providing
> many
> >> of the oft-requested features for you out-of-the-box (CORS, Caching,
> JSON
> >> transformation, validation, etc.). There's a README page that explains
> how
> >> to install/run Microbule in Karaf and how to write your own services.
> If
> >> you're interested, take it for a spin and let us know what you think.
> >>
> >> Thanks,
> >>
> >> James
> >>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Sergey Beryozkin <sb...@gmail.com>.
That is a music to our ears :-). CXF JAXRS is built on the solid core
dome by all of the WS work, ex, Oneway CXF JAX-RS extension which will
become very important going forward IMHO would not be here without WS-RM
work, etc carried out earlier
Sergey
On 23/11/16 14:21, James Carman wrote:
> Well, folks can use Microbule without knowing anything about CXF. The only
> thing you write is pure 100% JAX-RS code! The internals of Microbule are
> somewhat CXF-focused at the moment. Obviously, I could provide other
> implementation-specific (Jersey, RestEasy, etc.) bindings, but for now I'm
> going to focus on CXF since that's what I tend to enjoy using :)
>
>
> On Wed, Nov 23, 2016 at 9:19 AM Sergey Beryozkin <sb...@gmail.com>
> wrote:
>
>> Hi James
>>
>> While I certainly support the idea of having a given framework offering
>> an option for the users to have a 100% portable code, which is a
>> foundation, I also think SpringBoot (I refer to it simply because it was
>> already referred on this thread already :-)) shows why it has become so
>> popular - the last thing they care about is being on some standard line
>> but what they care about is offer the features which will be important
>> for their users and their users are rewarding them back.
>>
>> I've been trying to follow the same path in CXF JAX-RS - offer a solid
>> foundation for people to do 100% portable code, but do try as hard as I
>> can add some extensions - slow at times I guess. I'm def not alone in
>> this approach if we refer to Jersey, RestEasy. I encourage you to do the
>> same with Microbule. Sorry if it sounds a bit controversial, hopefully
>> not too much :-)
>>
>> Cheers, Sergey
>>
>>
>> On 23/11/16 13:00, James Carman wrote:
>>> There have been certain providers in Microbule where I had to dig into
>>> CXF-specific areas in order to implement them (request timeouts that I
>>> wrote last night being one for sure). I'd like to keep it pure JAX-RS as
>>> much as possible, though.
>>>
>>> On Wed, Nov 23, 2016 at 6:21 AM Sergey Beryozkin <sb...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>> One thing which is worth noting that a portability of JAX-RS 2.0
>>>> Features (and indeed other providers) is only achievable if they are
>>>> also implemented in a portable way...
>>>>
>>>
>>
>>
>> --
>> Sergey Beryozkin
>>
>> Talend Community Coders
>> http://coders.talend.com/
>>
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
Well, folks can use Microbule without knowing anything about CXF. The only
thing you write is pure 100% JAX-RS code! The internals of Microbule are
somewhat CXF-focused at the moment. Obviously, I could provide other
implementation-specific (Jersey, RestEasy, etc.) bindings, but for now I'm
going to focus on CXF since that's what I tend to enjoy using :)
On Wed, Nov 23, 2016 at 9:19 AM Sergey Beryozkin <sb...@gmail.com>
wrote:
> Hi James
>
> While I certainly support the idea of having a given framework offering
> an option for the users to have a 100% portable code, which is a
> foundation, I also think SpringBoot (I refer to it simply because it was
> already referred on this thread already :-)) shows why it has become so
> popular - the last thing they care about is being on some standard line
> but what they care about is offer the features which will be important
> for their users and their users are rewarding them back.
>
> I've been trying to follow the same path in CXF JAX-RS - offer a solid
> foundation for people to do 100% portable code, but do try as hard as I
> can add some extensions - slow at times I guess. I'm def not alone in
> this approach if we refer to Jersey, RestEasy. I encourage you to do the
> same with Microbule. Sorry if it sounds a bit controversial, hopefully
> not too much :-)
>
> Cheers, Sergey
>
>
> On 23/11/16 13:00, James Carman wrote:
> > There have been certain providers in Microbule where I had to dig into
> > CXF-specific areas in order to implement them (request timeouts that I
> > wrote last night being one for sure). I'd like to keep it pure JAX-RS as
> > much as possible, though.
> >
> > On Wed, Nov 23, 2016 at 6:21 AM Sergey Beryozkin <sb...@gmail.com>
> > wrote:
> >
> >> Hi,
> >> One thing which is worth noting that a portability of JAX-RS 2.0
> >> Features (and indeed other providers) is only achievable if they are
> >> also implemented in a portable way...
> >>
> >
>
>
> --
> Sergey Beryozkin
>
> Talend Community Coders
> http://coders.talend.com/
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi James
While I certainly support the idea of having a given framework offering
an option for the users to have a 100% portable code, which is a
foundation, I also think SpringBoot (I refer to it simply because it was
already referred on this thread already :-)) shows why it has become so
popular - the last thing they care about is being on some standard line
but what they care about is offer the features which will be important
for their users and their users are rewarding them back.
I've been trying to follow the same path in CXF JAX-RS - offer a solid
foundation for people to do 100% portable code, but do try as hard as I
can add some extensions - slow at times I guess. I'm def not alone in
this approach if we refer to Jersey, RestEasy. I encourage you to do the
same with Microbule. Sorry if it sounds a bit controversial, hopefully
not too much :-)
Cheers, Sergey
On 23/11/16 13:00, James Carman wrote:
> There have been certain providers in Microbule where I had to dig into
> CXF-specific areas in order to implement them (request timeouts that I
> wrote last night being one for sure). I'd like to keep it pure JAX-RS as
> much as possible, though.
>
> On Wed, Nov 23, 2016 at 6:21 AM Sergey Beryozkin <sb...@gmail.com>
> wrote:
>
>> Hi,
>> One thing which is worth noting that a portability of JAX-RS 2.0
>> Features (and indeed other providers) is only achievable if they are
>> also implemented in a portable way...
>>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
There have been certain providers in Microbule where I had to dig into
CXF-specific areas in order to implement them (request timeouts that I
wrote last night being one for sure). I'd like to keep it pure JAX-RS as
much as possible, though.
On Wed, Nov 23, 2016 at 6:21 AM Sergey Beryozkin <sb...@gmail.com>
wrote:
> Hi,
> One thing which is worth noting that a portability of JAX-RS 2.0
> Features (and indeed other providers) is only achievable if they are
> also implemented in a portable way...
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi,
One thing which is worth noting that a portability of JAX-RS 2.0
Features (and indeed other providers) is only achievable if they are
also implemented in a portable way...
Cheers, Sergey
On 23/11/16 08:53, Christian Schneider wrote:
> I really like the microbule project scope. We really need a project that
> can bring mircoservice development on CXF and OSGi to the same level as
> spring boot.
> I am only concerned that many different projects seem to cover parts of
> this at the moment. So if we are not careful we again will have too many
> separate efforts inside the already small OSGi space.
>
> Some things you might want to look into:
>
> In the CXF-DOSGi samples I have bndrun that shows how to package cxf and
> the felix http service.
> https://github.com/apache/cxf-dosgi/blob/master/samples/soap/soap.bndrun
> I used the /myservice addresses and it works quite well. Felix http
> service is a a lot simpler to deploy than pax web. As CXF-DOSGi just
> uses the HttpService it is easy to use pax-web when deployed in karaf
> and felix http service for microservice like deployments.
>
> Another project to look into is the Aries JAX-RS-whiteboard. It is
> implementing the JAX-RS Whiteboard OSGi spec in Aries. Your project
> should have a big overlap with CXF-DOSGi and JAX-RS-whiteboard. I wonder
> if we could combine these efforts. One possible solution would be to
> concentrate the efforts of exporting REST services in JAX-RS whiteboard.
> Then your framework could concentrate on the remaining aspects of
> microservices like circuit breaker, discovery and packaging. The Aries
> JAX-RS whiteboard project is currently in a very early stage. So I think
> this should provide a great opportunity to get your ideas into the project.
>
> Another interesting part of JAX-RS whiteboard is that it can provide
> OSGi enabled JAX-RS ClientBuilder instances. So that could be used to
> create clients without depending on CXF in the user code.
>
> CXF-DOSGi on the other hand can provide fully transparent type safe
> clients as OSGi services which could also provide some value.
>
> I am also working on getting zipkin and brave tracing working inside
> OSGi. See https://github.com/cschneider/brave-osgi-example
> Brave already offers JAX-RS interceptors for logging and I added a PR to
> offer a jax-rs Feature. That will make it really easy to add tracing to
> CXF and any other JAX-RS 2 impl.
>
> Before that I was not aware that JAX-RS has such a nice portable Feature
> interface. So I think a lot of the microservice features like circuit
> breaker could be created in a portable way. This would give the user the
> free choice of the JAX-RS impl.
>
> I also had pretty good experiences using bndtools to create the
> packaging into a runnable jar. The result is a lot smaller than karaf
> (~9mb for a full REST example) and matches the docker concepts better.
>
> Sorry for this highly uncohesive list but I just wanted to give you some
> ideas to pursue :-)
>
> Christian
>
>
>
> On 22.11.2016 21:55, Benson Margulies wrote:
>> A small update with some irony here.
>>
>> At the job I just finished today, we reached the conclusion that we
>> weren't getting much value out of Karaf and pax-web; no criticism
>> intended, we just don't dynamically provision, and we don't need any
>> HTTP except for CXF services. So, over the last few weeks, we
>> refactored the thing to use cxf-rt-transport-http-jetty in the Felix
>> container, with our own rather tiny class responsible for launching.
>> We lost a bit of flexibility in that we can't create an endpoint
>> 'inside' of the namespace of another endpoint, but otherwise it works
>> just fine. The code that that I showed James is hardly changed at all.
>> The endpoint addresses now look like
>> "http://0.0.0.0:nnnnn/base/whatever" instead "/whatever". Maybe some
>> day there will be an ultramicrobule that anticipates this mode of
>> operation.
>>
>>
>>
>>
>>
>> On Mon, Nov 21, 2016 at 7:13 PM, James Carman
>> <ja...@carmanconsulting.com> wrote:
>>> Small update. Microbule 0.1.0 release has been cut and will soon be
>>> available in Maven Central (awaiting sync from Nexus OSS). Enjoy,
>>> folks!
>>>
>>> On Mon, Nov 21, 2016 at 1:03 PM James Carman
>>> <ja...@carmanconsulting.com>
>>> wrote:
>>>
>>>> We've been working on a Microservices framework called "Microbule"
>>>> which
>>>> leverages CXF and Karaf (hence the cross-post):
>>>>
>>>> https://github.com/jwcarman/microbule
>>>>
>>>> The idea is to make writing Microservices easy and fun, by providing
>>>> many
>>>> of the oft-requested features for you out-of-the-box (CORS, Caching,
>>>> JSON
>>>> transformation, validation, etc.). There's a README page that
>>>> explains how
>>>> to install/run Microbule in Karaf and how to write your own
>>>> services. If
>>>> you're interested, take it for a spin and let us know what you think.
>>>>
>>>> Thanks,
>>>>
>>>> James
>>>>
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Re: [ANNOUNCE] Introducing Microbule...
Posted by Christian Schneider <ch...@die-schneider.net>.
I really like the microbule project scope. We really need a project that
can bring mircoservice development on CXF and OSGi to the same level as
spring boot.
I am only concerned that many different projects seem to cover parts of
this at the moment. So if we are not careful we again will have too many
separate efforts inside the already small OSGi space.
Some things you might want to look into:
In the CXF-DOSGi samples I have bndrun that shows how to package cxf and
the felix http service.
https://github.com/apache/cxf-dosgi/blob/master/samples/soap/soap.bndrun
I used the /myservice addresses and it works quite well. Felix http
service is a a lot simpler to deploy than pax web. As CXF-DOSGi just
uses the HttpService it is easy to use pax-web when deployed in karaf
and felix http service for microservice like deployments.
Another project to look into is the Aries JAX-RS-whiteboard. It is
implementing the JAX-RS Whiteboard OSGi spec in Aries. Your project
should have a big overlap with CXF-DOSGi and JAX-RS-whiteboard. I wonder
if we could combine these efforts. One possible solution would be to
concentrate the efforts of exporting REST services in JAX-RS whiteboard.
Then your framework could concentrate on the remaining aspects of
microservices like circuit breaker, discovery and packaging. The Aries
JAX-RS whiteboard project is currently in a very early stage. So I think
this should provide a great opportunity to get your ideas into the project.
Another interesting part of JAX-RS whiteboard is that it can provide
OSGi enabled JAX-RS ClientBuilder instances. So that could be used to
create clients without depending on CXF in the user code.
CXF-DOSGi on the other hand can provide fully transparent type safe
clients as OSGi services which could also provide some value.
I am also working on getting zipkin and brave tracing working inside
OSGi. See https://github.com/cschneider/brave-osgi-example
Brave already offers JAX-RS interceptors for logging and I added a PR to
offer a jax-rs Feature. That will make it really easy to add tracing to
CXF and any other JAX-RS 2 impl.
Before that I was not aware that JAX-RS has such a nice portable Feature
interface. So I think a lot of the microservice features like circuit
breaker could be created in a portable way. This would give the user the
free choice of the JAX-RS impl.
I also had pretty good experiences using bndtools to create the
packaging into a runnable jar. The result is a lot smaller than karaf
(~9mb for a full REST example) and matches the docker concepts better.
Sorry for this highly uncohesive list but I just wanted to give you some
ideas to pursue :-)
Christian
On 22.11.2016 21:55, Benson Margulies wrote:
> A small update with some irony here.
>
> At the job I just finished today, we reached the conclusion that we
> weren't getting much value out of Karaf and pax-web; no criticism
> intended, we just don't dynamically provision, and we don't need any
> HTTP except for CXF services. So, over the last few weeks, we
> refactored the thing to use cxf-rt-transport-http-jetty in the Felix
> container, with our own rather tiny class responsible for launching.
> We lost a bit of flexibility in that we can't create an endpoint
> 'inside' of the namespace of another endpoint, but otherwise it works
> just fine. The code that that I showed James is hardly changed at all.
> The endpoint addresses now look like
> "http://0.0.0.0:nnnnn/base/whatever" instead "/whatever". Maybe some
> day there will be an ultramicrobule that anticipates this mode of
> operation.
>
>
>
>
>
> On Mon, Nov 21, 2016 at 7:13 PM, James Carman
> <ja...@carmanconsulting.com> wrote:
>> Small update. Microbule 0.1.0 release has been cut and will soon be
>> available in Maven Central (awaiting sync from Nexus OSS). Enjoy, folks!
>>
>> On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
>> wrote:
>>
>>> We've been working on a Microservices framework called "Microbule" which
>>> leverages CXF and Karaf (hence the cross-post):
>>>
>>> https://github.com/jwcarman/microbule
>>>
>>> The idea is to make writing Microservices easy and fun, by providing many
>>> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
>>> transformation, validation, etc.). There's a README page that explains how
>>> to install/run Microbule in Karaf and how to write your own services. If
>>> you're interested, take it for a spin and let us know what you think.
>>>
>>> Thanks,
>>>
>>> James
>>>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [ANNOUNCE] Introducing Microbule...
Posted by Benson Margulies <bi...@gmail.com>.
A small update with some irony here.
At the job I just finished today, we reached the conclusion that we
weren't getting much value out of Karaf and pax-web; no criticism
intended, we just don't dynamically provision, and we don't need any
HTTP except for CXF services. So, over the last few weeks, we
refactored the thing to use cxf-rt-transport-http-jetty in the Felix
container, with our own rather tiny class responsible for launching.
We lost a bit of flexibility in that we can't create an endpoint
'inside' of the namespace of another endpoint, but otherwise it works
just fine. The code that that I showed James is hardly changed at all.
The endpoint addresses now look like
"http://0.0.0.0:nnnnn/base/whatever" instead "/whatever". Maybe some
day there will be an ultramicrobule that anticipates this mode of
operation.
On Mon, Nov 21, 2016 at 7:13 PM, James Carman
<ja...@carmanconsulting.com> wrote:
> Small update. Microbule 0.1.0 release has been cut and will soon be
> available in Maven Central (awaiting sync from Nexus OSS). Enjoy, folks!
>
> On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
> wrote:
>
>> We've been working on a Microservices framework called "Microbule" which
>> leverages CXF and Karaf (hence the cross-post):
>>
>> https://github.com/jwcarman/microbule
>>
>> The idea is to make writing Microservices easy and fun, by providing many
>> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
>> transformation, validation, etc.). There's a README page that explains how
>> to install/run Microbule in Karaf and how to write your own services. If
>> you're interested, take it for a spin and let us know what you think.
>>
>> Thanks,
>>
>> James
>>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
Small update. Microbule 0.1.0 release has been cut and will soon be
available in Maven Central (awaiting sync from Nexus OSS). Enjoy, folks!
On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
wrote:
> We've been working on a Microservices framework called "Microbule" which
> leverages CXF and Karaf (hence the cross-post):
>
> https://github.com/jwcarman/microbule
>
> The idea is to make writing Microservices easy and fun, by providing many
> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> transformation, validation, etc.). There's a README page that explains how
> to install/run Microbule in Karaf and how to write your own services. If
> you're interested, take it for a spin and let us know what you think.
>
> Thanks,
>
> James
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
FYI, Microbule has now moved:
https://microbule.github.io/microbule/
On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
wrote:
> We've been working on a Microservices framework called "Microbule" which
> leverages CXF and Karaf (hence the cross-post):
>
> https://github.com/jwcarman/microbule
>
> The idea is to make writing Microservices easy and fun, by providing many
> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> transformation, validation, etc.). There's a README page that explains how
> to install/run Microbule in Karaf and how to write your own services. If
> you're interested, take it for a spin and let us know what you think.
>
> Thanks,
>
> James
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
By the way, I should give credit to Benson Margulies for giving me the
"secret sauce" of creating CXF servers on-the-fly! Thanks, Benson!
On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
wrote:
> We've been working on a Microservices framework called "Microbule" which
> leverages CXF and Karaf (hence the cross-post):
>
> https://github.com/jwcarman/microbule
>
> The idea is to make writing Microservices easy and fun, by providing many
> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> transformation, validation, etc.). There's a README page that explains how
> to install/run Microbule in Karaf and how to write your own services. If
> you're interested, take it for a spin and let us know what you think.
>
> Thanks,
>
> James
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi James,
Would it be an option to extract the tracer - at least the names of the
headers - to a "portable" module? With Mark we were on that area as well
for meecrowave (a microprofile server based on CXF too and hosted
@openwebbeans) and was thinking to add it to sirona since it is the
monitoring related ASF project. Would be great to make the names/format
uniform accross impl otherwise inteoperability is hard and this feature
loose some of its strength.
wdyt?
PS: sure we can share more but this would at least enable a
microbule-meecrowave cluster to speak the same language ;)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
2016-11-21 19:03 GMT+01:00 James Carman <ja...@carmanconsulting.com>:
> We've been working on a Microservices framework called "Microbule" which
> leverages CXF and Karaf (hence the cross-post):
>
> https://github.com/jwcarman/microbule
>
> The idea is to make writing Microservices easy and fun, by providing many
> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> transformation, validation, etc.). There's a README page that explains how
> to install/run Microbule in Karaf and how to write your own services. If
> you're interested, take it for a spin and let us know what you think.
>
> Thanks,
>
> James
>
Re: [ANNOUNCE] Introducing Microbule...
Posted by James Carman <ja...@carmanconsulting.com>.
Small update. Microbule 0.1.0 release has been cut and will soon be
available in Maven Central (awaiting sync from Nexus OSS). Enjoy, folks!
On Mon, Nov 21, 2016 at 1:03 PM James Carman <ja...@carmanconsulting.com>
wrote:
> We've been working on a Microservices framework called "Microbule" which
> leverages CXF and Karaf (hence the cross-post):
>
> https://github.com/jwcarman/microbule
>
> The idea is to make writing Microservices easy and fun, by providing many
> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON
> transformation, validation, etc.). There's a README page that explains how
> to install/run Microbule in Karaf and how to write your own services. If
> you're interested, take it for a spin and let us know what you think.
>
> Thanks,
>
> James
>