From ggastald at redhat.com Fri Jul 21 01:10:07 2017 From: ggastald at redhat.com (George Gastaldi) Date: Fri, 21 Jul 2017 02:10:07 -0300 Subject: [forge-dev] Running Furnace (Forge container) in a flat classloader Message-ID: Hey all! For those interested in running Forge in a flat classloader, using CDI in its full potential (including Interceptors and Decorators), I created a project that may help you[1]. It is basically an implementation of the Furnace API that exposes the services provided by addons that use the simple-container using a CDI extension. Addons that depend on the CDI container are already CDI-friendly, so expect no changes in this project when loading those addons. It may save you some memory by not starting several Weld instances and it's really fast. Give it a try if you like! [1] https://github.com/gastaldi/furnace-embedded Best Regards, George Gastaldi Principal Software Engineer Red Hat Remote Joinville - Santa Catarina ggastald at redhat.com M: +55-47-99711-1000 TRIED. TESTED. TRUSTED. @redhatnews Red Hat Red Hat From ivan.st.ivanov at gmail.com Fri Jul 21 05:07:22 2017 From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov) Date: Fri, 21 Jul 2017 12:07:22 +0300 Subject: [forge-dev] Running Furnace (Forge container) in a flat classloader In-Reply-To: References: Message-ID: Hi George, If I got it right, that's really awesome! No, no, let me put it in another way: that's amazing!!! :) Let me try and explain what I got. If I add dependency in my project to furnace-embedded and to Forge BOM (or whichever project that exports maven addons, i.e. commands), I will be able to call those addons/commands programmatically form my project. That is, I can use the simple container to look up e.g. the create project command and run it, configuring it with the "input" like the UI does. And this will create a new project for me without running Forge as a separate process. Right? Cheers, Ivan On Fri, Jul 21, 2017 at 8:10 AM, George Gastaldi wrote: > Hey all! > > For those interested in running Forge in a flat classloader, using CDI in > its full potential (including Interceptors and Decorators), I created a > project that may help you[1]. > > It is basically an implementation of the Furnace API that exposes the > services provided by addons that use the simple-container using a CDI > extension. Addons that depend on the CDI container are already > CDI-friendly, so expect no changes in this project when loading those > addons. > > It may save you some memory by not starting several Weld instances and > it's really fast. Give it a try if you like! > > [1] https://github.com/gastaldi/furnace-embedded > > Best Regards, > > > > George Gastaldi > > Principal Software Engineer > > Red Hat > > Remote > > Joinville - Santa Catarina > > ggastald at redhat.com M: +55-47-99711-1000 > > TRIED. TESTED. TRUSTED. > @redhatnews Red Hat > Red Hat > > > From ggastald at redhat.com Fri Jul 21 10:40:42 2017 From: ggastald at redhat.com (George Gastaldi) Date: Fri, 21 Jul 2017 11:40:42 -0300 Subject: [forge-dev] Running Furnace (Forge container) in a flat classloader In-Reply-To: References: Message-ID: Hi Ivan, You can already do that with https://github.com/forge/forge-service. Forge doesn't fork into another process (since Forge 2.0.0.Final was released :)) The only difference is that furnace-embedded will run in a single Weld instance, which may be a good thing when you run Forge inside a WAR or when you don't need a modular classpath. Em 21 de jul de 2017 06:07, "Ivan St. Ivanov" escreveu: Hi George, If I got it right, that's really awesome! No, no, let me put it in another way: that's amazing!!! :) Let me try and explain what I got. If I add dependency in my project to furnace-embedded and to Forge BOM (or whichever project that exports maven addons, i.e. commands), I will be able to call those addons/commands programmatically form my project. That is, I can use the simple container to look up e.g. the create project command and run it, configuring it with the "input" like the UI does. And this will create a new project for me without running Forge as a separate process. Right? Cheers, Ivan On Fri, Jul 21, 2017 at 8:10 AM, George Gastaldi wrote: > Hey all! > > For those interested in running Forge in a flat classloader, using CDI in > its full potential (including Interceptors and Decorators), I created a > project that may help you[1]. > > It is basically an implementation of the Furnace API that exposes the > services provided by addons that use the simple-container using a CDI > extension. Addons that depend on the CDI container are already > CDI-friendly, so expect no changes in this project when loading those > addons. > > It may save you some memory by not starting several Weld instances and > it's really fast. Give it a try if you like! > > [1] https://github.com/gastaldi/furnace-embedded > > Best Regards, > > > > George Gastaldi > > Principal Software Engineer > > Red Hat > > Remote > > Joinville - Santa Catarina > > ggastald at redhat.com M: +55-47-99711-1000 > > TRIED. TESTED. TRUSTED. > @redhatnews Red Hat > Red Hat > > > _______________________________________________ forge-dev mailing list forge-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev From ivan.st.ivanov at gmail.com Fri Jul 21 13:08:16 2017 From: ivan.st.ivanov at gmail.com (Ivan St. Ivanov) Date: Fri, 21 Jul 2017 20:08:16 +0300 Subject: [forge-dev] Running Furnace (Forge container) in a flat classloader In-Reply-To: References: Message-ID: Hi George, I already tried the service. And still there I need to run it as a separate application (by e.g. launching Wildfly Swarm). So I think I got it right that furnace embedded does that, but inside your own monolith ;) Awesome! Great work! Cheers, Ivan On Fri, Jul 21, 2017 at 5:40 PM, George Gastaldi wrote: > Hi Ivan, > > You can already do that with https://github.com/forge/forge-service. Forge > doesn't fork into another process (since Forge 2.0.0.Final was released :)) > > The only difference is that furnace-embedded will run in a single Weld > instance, which may be a good thing when you run Forge inside a WAR or when > you don't need a modular classpath. > > > Em 21 de jul de 2017 06:07, "Ivan St. Ivanov" > escreveu: > > Hi George, > > If I got it right, that's really awesome! No, no, let me put it in another > way: that's amazing!!! :) > > Let me try and explain what I got. > > If I add dependency in my project to furnace-embedded and to Forge BOM (or > whichever project that exports maven addons, i.e. commands), I will be able > to call those addons/commands programmatically form my project. > > That is, I can use the simple container to look up e.g. the create project > command and run it, configuring it with the "input" like the UI does. And > this will create a new project for me without running Forge as a separate > process. Right? > > Cheers, > Ivan > > On Fri, Jul 21, 2017 at 8:10 AM, George Gastaldi > wrote: > > > Hey all! > > > > For those interested in running Forge in a flat classloader, using CDI in > > its full potential (including Interceptors and Decorators), I created a > > project that may help you[1]. > > > > It is basically an implementation of the Furnace API that exposes the > > services provided by addons that use the simple-container using a CDI > > extension. Addons that depend on the CDI container are already > > CDI-friendly, so expect no changes in this project when loading those > > addons. > > > > It may save you some memory by not starting several Weld instances and > > it's really fast. Give it a try if you like! > > > > [1] https://github.com/gastaldi/furnace-embedded > > > > Best Regards, > > > > > > > > George Gastaldi > > > > Principal Software Engineer > > > > Red Hat > > > > Remote > > > > Joinville - Santa Catarina > > > > ggastald at redhat.com M: +55-47-99711-1000 > > > > TRIED. TESTED. TRUSTED. > > @redhatnews Red Hat > > Red Hat > > > > > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > From lincolnbaxter at gmail.com Thu Jul 27 17:08:26 2017 From: lincolnbaxter at gmail.com (Lincoln Baxter, III) Date: Thu, 27 Jul 2017 17:08:26 -0400 Subject: [forge-dev] Running Furnace (Forge container) in a flat classloader In-Reply-To: References: Message-ID: This is really awesome, George! Definitely another milestone in Forge's "write once, run everywhere" philosophy! You are amazing :) Lincoln Baxter, III http://ocpsoft.org "Simpler is better." On Fri, Jul 21, 2017 at 1:08 PM, Ivan St. Ivanov wrote: > Hi George, > > I already tried the service. And still there I need to run it as a separate > application (by e.g. launching Wildfly Swarm). > > So I think I got it right that furnace embedded does that, but inside your > own monolith ;) > > Awesome! Great work! > > Cheers, > Ivan > > On Fri, Jul 21, 2017 at 5:40 PM, George Gastaldi > wrote: > > > Hi Ivan, > > > > You can already do that with https://github.com/forge/forge-service. > Forge > > doesn't fork into another process (since Forge 2.0.0.Final was released > :)) > > > > The only difference is that furnace-embedded will run in a single Weld > > instance, which may be a good thing when you run Forge inside a WAR or > when > > you don't need a modular classpath. > > > > > > Em 21 de jul de 2017 06:07, "Ivan St. Ivanov" > > escreveu: > > > > Hi George, > > > > If I got it right, that's really awesome! No, no, let me put it in > another > > way: that's amazing!!! :) > > > > Let me try and explain what I got. > > > > If I add dependency in my project to furnace-embedded and to Forge BOM > (or > > whichever project that exports maven addons, i.e. commands), I will be > able > > to call those addons/commands programmatically form my project. > > > > That is, I can use the simple container to look up e.g. the create > project > > command and run it, configuring it with the "input" like the UI does. And > > this will create a new project for me without running Forge as a separate > > process. Right? > > > > Cheers, > > Ivan > > > > On Fri, Jul 21, 2017 at 8:10 AM, George Gastaldi > > wrote: > > > > > Hey all! > > > > > > For those interested in running Forge in a flat classloader, using CDI > in > > > its full potential (including Interceptors and Decorators), I created a > > > project that may help you[1]. > > > > > > It is basically an implementation of the Furnace API that exposes the > > > services provided by addons that use the simple-container using a CDI > > > extension. Addons that depend on the CDI container are already > > > CDI-friendly, so expect no changes in this project when loading those > > > addons. > > > > > > It may save you some memory by not starting several Weld instances and > > > it's really fast. Give it a try if you like! > > > > > > [1] https://github.com/gastaldi/furnace-embedded > > > > > > Best Regards, > > > > > > > > > > > > George Gastaldi > > > > > > Principal Software Engineer > > > > > > Red Hat > > > > > > Remote > > > > > > Joinville - Santa Catarina > > > > > > ggastald at redhat.com M: +55-47-99711-1000 > > > > > > TRIED. TESTED. TRUSTED. > > > @redhatnews Red Hat > > > Red Hat > > > > > > > > > > > _______________________________________________ > > forge-dev mailing list > > forge-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/forge-dev > > _______________________________________________ > > forge-dev mailing list > > forge-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > From alr at redhat.com Thu Jul 27 23:40:00 2017 From: alr at redhat.com (Andrew Lee Rubinger) Date: Thu, 27 Jul 2017 23:40:00 -0400 Subject: [forge-dev] Running Furnace (Forge container) in a flat classloader In-Reply-To: References: Message-ID: On Thu, Jul 27, 2017 at 5:08 PM, Lincoln Baxter, III < lincolnbaxter at gmail.com> wrote: > This is really awesome, George! Definitely another milestone in Forge's > "write once, run everywhere" philosophy! You are amazing :) > Oh my gosh, George woke a ghost. That's how awesome he is. S, ALR > > Lincoln Baxter, III > http://ocpsoft.org > "Simpler is better." > > On Fri, Jul 21, 2017 at 1:08 PM, Ivan St. Ivanov > > wrote: > > > Hi George, > > > > I already tried the service. And still there I need to run it as a > separate > > application (by e.g. launching Wildfly Swarm). > > > > So I think I got it right that furnace embedded does that, but inside > your > > own monolith ;) > > > > Awesome! Great work! > > > > Cheers, > > Ivan > > > > On Fri, Jul 21, 2017 at 5:40 PM, George Gastaldi > > wrote: > > > > > Hi Ivan, > > > > > > You can already do that with https://github.com/forge/forge-service. > > Forge > > > doesn't fork into another process (since Forge 2.0.0.Final was released > > :)) > > > > > > The only difference is that furnace-embedded will run in a single Weld > > > instance, which may be a good thing when you run Forge inside a WAR or > > when > > > you don't need a modular classpath. > > > > > > > > > Em 21 de jul de 2017 06:07, "Ivan St. Ivanov" < > ivan.st.ivanov at gmail.com> > > > escreveu: > > > > > > Hi George, > > > > > > If I got it right, that's really awesome! No, no, let me put it in > > another > > > way: that's amazing!!! :) > > > > > > Let me try and explain what I got. > > > > > > If I add dependency in my project to furnace-embedded and to Forge BOM > > (or > > > whichever project that exports maven addons, i.e. commands), I will be > > able > > > to call those addons/commands programmatically form my project. > > > > > > That is, I can use the simple container to look up e.g. the create > > project > > > command and run it, configuring it with the "input" like the UI does. > And > > > this will create a new project for me without running Forge as a > separate > > > process. Right? > > > > > > Cheers, > > > Ivan > > > > > > On Fri, Jul 21, 2017 at 8:10 AM, George Gastaldi > > > wrote: > > > > > > > Hey all! > > > > > > > > For those interested in running Forge in a flat classloader, using > CDI > > in > > > > its full potential (including Interceptors and Decorators), I > created a > > > > project that may help you[1]. > > > > > > > > It is basically an implementation of the Furnace API that exposes the > > > > services provided by addons that use the simple-container using a CDI > > > > extension. Addons that depend on the CDI container are already > > > > CDI-friendly, so expect no changes in this project when loading those > > > > addons. > > > > > > > > It may save you some memory by not starting several Weld instances > and > > > > it's really fast. Give it a try if you like! > > > > > > > > [1] https://github.com/gastaldi/furnace-embedded > > > > > > > > Best Regards, > > > > > > > > > > > > > > > > George Gastaldi > > > > > > > > Principal Software Engineer > > > > > > > > Red Hat > > > > > > > > Remote > > > > > > > > Joinville - Santa Catarina > > > > > > > > ggastald at redhat.com M: +55-47-99711-1000 > > > > > > > > TRIED. TESTED. TRUSTED. > > > > @redhatnews Red Hat > > > > Red Hat > > > > > > > > > > > > > > > _______________________________________________ > > > forge-dev mailing list > > > forge-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > > > forge-dev mailing list > > > forge-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/forge-dev > > > > > _______________________________________________ > > forge-dev mailing list > > forge-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > -- Twitter: @ALRubinger From ggastald at redhat.com Fri Jul 28 00:01:16 2017 From: ggastald at redhat.com (George Gastaldi) Date: Fri, 28 Jul 2017 01:01:16 -0300 Subject: [forge-dev] Running Furnace (Forge container) in a flat classloader In-Reply-To: References: Message-ID: Thanks! And I have released a 1.0.0.Alpha1 in maven central, so people can try it right away :) Best Regards, George Gastaldi Principal Software Engineer Red Hat Remote Joinville - Santa Catarina ggastald at redhat.com M: +55-47-99711-1000 TRIED. TESTED. TRUSTED. @redhatnews Red Hat Red Hat On Thu, Jul 27, 2017 at 6:08 PM, Lincoln Baxter, III < lincolnbaxter at gmail.com> wrote: > This is really awesome, George! Definitely another milestone in Forge's > "write once, run everywhere" philosophy! You are amazing :) > > Lincoln Baxter, III > http://ocpsoft.org > "Simpler is better." > > On Fri, Jul 21, 2017 at 1:08 PM, Ivan St. Ivanov > > wrote: > > > Hi George, > > > > I already tried the service. And still there I need to run it as a > separate > > application (by e.g. launching Wildfly Swarm). > > > > So I think I got it right that furnace embedded does that, but inside > your > > own monolith ;) > > > > Awesome! Great work! > > > > Cheers, > > Ivan > > > > On Fri, Jul 21, 2017 at 5:40 PM, George Gastaldi > > wrote: > > > > > Hi Ivan, > > > > > > You can already do that with https://github.com/forge/forge-service. > > Forge > > > doesn't fork into another process (since Forge 2.0.0.Final was released > > :)) > > > > > > The only difference is that furnace-embedded will run in a single Weld > > > instance, which may be a good thing when you run Forge inside a WAR or > > when > > > you don't need a modular classpath. > > > > > > > > > Em 21 de jul de 2017 06:07, "Ivan St. Ivanov" < > ivan.st.ivanov at gmail.com> > > > escreveu: > > > > > > Hi George, > > > > > > If I got it right, that's really awesome! No, no, let me put it in > > another > > > way: that's amazing!!! :) > > > > > > Let me try and explain what I got. > > > > > > If I add dependency in my project to furnace-embedded and to Forge BOM > > (or > > > whichever project that exports maven addons, i.e. commands), I will be > > able > > > to call those addons/commands programmatically form my project. > > > > > > That is, I can use the simple container to look up e.g. the create > > project > > > command and run it, configuring it with the "input" like the UI does. > And > > > this will create a new project for me without running Forge as a > separate > > > process. Right? > > > > > > Cheers, > > > Ivan > > > > > > On Fri, Jul 21, 2017 at 8:10 AM, George Gastaldi > > > wrote: > > > > > > > Hey all! > > > > > > > > For those interested in running Forge in a flat classloader, using > CDI > > in > > > > its full potential (including Interceptors and Decorators), I > created a > > > > project that may help you[1]. > > > > > > > > It is basically an implementation of the Furnace API that exposes the > > > > services provided by addons that use the simple-container using a CDI > > > > extension. Addons that depend on the CDI container are already > > > > CDI-friendly, so expect no changes in this project when loading those > > > > addons. > > > > > > > > It may save you some memory by not starting several Weld instances > and > > > > it's really fast. Give it a try if you like! > > > > > > > > [1] https://github.com/gastaldi/furnace-embedded > > > > > > > > Best Regards, > > > > > > > > > > > > > > > > George Gastaldi > > > > > > > > Principal Software Engineer > > > > > > > > Red Hat > > > > > > > > Remote > > > > > > > > Joinville - Santa Catarina > > > > > > > > ggastald at redhat.com M: +55-47-99711-1000 > > > > > > > > TRIED. TESTED. TRUSTED. > > > > @redhatnews Red Hat > > > > Red Hat > > > > > > > > > > > > > > > _______________________________________________ > > > forge-dev mailing list > > > forge-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > > > forge-dev mailing list > > > forge-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/forge-dev > > > > > _______________________________________________ > > forge-dev mailing list > > forge-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > From jsightle at redhat.com Fri Jul 28 14:14:03 2017 From: jsightle at redhat.com (Jess Sightler) Date: Fri, 28 Jul 2017 14:14:03 -0400 Subject: [forge-dev] Running Furnace (Forge container) in a flat classloader In-Reply-To: References: Message-ID: That is great news. I look forward to trying it with the Windup project. On Fri, Jul 21, 2017 at 1:10 AM, George Gastaldi wrote: > Hey all! > > For those interested in running Forge in a flat classloader, using CDI in > its full potential (including Interceptors and Decorators), I created a > project that may help you[1]. > > It is basically an implementation of the Furnace API that exposes the > services provided by addons that use the simple-container using a CDI > extension. Addons that depend on the CDI container are already > CDI-friendly, so expect no changes in this project when loading those > addons. > > It may save you some memory by not starting several Weld instances and it's > really fast. Give it a try if you like! > > [1] https://github.com/gastaldi/furnace-embedded > > Best Regards, > > > > George Gastaldi > > Principal Software Engineer > > Red Hat > > Remote > > Joinville - Santa Catarina > > ggastald at redhat.com M: +55-47-99711-1000 > > TRIED. TESTED. TRUSTED. > @redhatnews Red Hat > Red Hat > > _______________________________________________ > forge-dev mailing list > forge-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev >