Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: error (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <1427363676518-5764818.post@n5.nabble.com>
References: 
 <CAJ9TCvoY=JSSRTH=DCSoXAr3oTyNXLF7kS6c8bQ8sB-TwssVwA@mail.gmail.com>
 <1427361321880-5764817.post@n5.nabble.com>
 <1427363676518-5764818.post@n5.nabble.com>
From: Jakub Kotowski <jakub@sindicetech.com>
Date: Fri, 27 Mar 2015 14:57:04 +0000
Message-ID: 
 <CAJ9TCvrscqu_+yrzuAdP1jT=CBEZEdufEEhLtoTkoW5aj+t=Qw@mail.gmail.com>
Subject: Re: Setting up CamelContext with Guice
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=001a1141c7b4a9d1df0512465949

--001a1141c7b4a9d1df0512465949
Content-Type: text/plain; charset=UTF-8

Thanks for the replies.

After studying the code, I solved it independently like Willem Jiang
suggests:

public class MyCamelContext extends GuiceCamelContext {
  @Inject
  public MyCamelContext(Injector injector) {
    super(injector);
  }

  @PostConstruct
  public void start() {
    setTracing(true);

    // etc.

    super.start();
  }
}


But then I immediately got stuck with a new problem. I wanted to configure
my application from command line arguments and that seems impossible to do
cleanly with the Camel Guice Main.

In the end, I found an ugly hack which is however quite localized:

public class MyMain extends Main {

  // this is the ugly hack - a static variable that can be accessed
from a Guice Module

  // Guice doesn't run until main.run(args) is called so it's safe

  public static MainArgs mainArgs;


  public MyMain(String args[]) throws InterruptedException {
    mainArgs = new MainArgs();
    mainArgs.setArgs(args);

    addOption(new ParameterOption("c", "conf", "Path to the
application.conf configuration file.", "filePath") {
      @Override
      protected void doProcess(String arg, String parameter,
LinkedList<String> remainingArgs) {
        mainArgs.setConfFile(parameter);
        mainArgs.loadAndValidateConf();
      }
    });
  }

  public static void main(String args[]) throws Exception {
    Main main = new MyMain(args);

    main.enableHangupSupport();
    main.run(args);
  }
}


Then I have MainArgsModule which provides MainArgs via normal dependency
injections - this way I can restrict the ugly static access to this one
class while the rest of the app can use dependency injection as usual.

public class MainArgsModule extends AbstractModule {
  @Override
  protected void configure() {
  }

  @Provides
  public MainArgs createMainArgs() {
    return MainFlowGuice.mainArgs;
  }
}

jndi.properties:

java.naming.factory.initial =
org.apache.camel.guice.jndi.GuiceInitialContextFactory
org.guiceyfruit.modules = com.myapp.ApplicationModule com.myapp.MainArgsModule


I guess that really not many people use Guice with Camel when there are
such basic issues using it? I am wondering how much more friction there
will be and whether it wouldn't make more sense to simply use Spring as
most do (even though Spring is not my first choice otherwise).

Later I could of course write my own Main for Guice, etc. but I was
hoping to get started rather quickly.


Jakub


On Thu, Mar 26, 2015 at 9:54 AM, dermoritz <tanteanni@hotmail.com> wrote:

> i just created an ticket with a suggestion:
> https://issues.apache.org/jira/browse/CAMEL-8555
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Setting-up-CamelContext-with-Guice-tp5764709p5764818.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

--001a1141c7b4a9d1df0512465949--