tag:blogger.com,1999:blog-637417304187784899.post4199533778380743531..comments2024-01-04T09:04:42.121+00:00Comments on James Strachan's Blog: Apache Camel goes top level!James Strachanhttp://www.blogger.com/profile/12591119339035350067noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-637417304187784899.post-84841795941085301442009-01-26T12:09:00.000+00:002009-01-26T12:09:00.000+00:00Since its all new code and not so much patching ex...Since its all new code and not so much patching existing code, attaching a tarball / zip to a JIRA is probably the easiest thing to do. Remember to tick the 'grant to the ASF as Apache Licensed code' checkbox when adding your attachmentJames Strachanhttps://www.blogger.com/profile/12591119339035350067noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-49304883016930024942009-01-26T12:03:00.000+00:002009-01-26T12:03:00.000+00:00Now I see the reason behind your Guice ml posts. :...Now I see the reason behind your Guice ml posts. :-)<BR/><BR/>Thinking about the patch.<BR/>Since I'll be just adding a simple file + modifying a few pom.xml's.<BR/><BR/>I guess the easiest way would be if the Camel + MC paths already existed.<BR/>Then a simple 'svn diff' would do it.<BR/><BR/>Or how else do you patch newly created paths (directories)?<BR/><BR/>The path that I added:<BR/>C:\projects\camel\components\camel-jbossmc\src\main\java\org\apache\camel\jbossmc\registry\ControllerRegistry.java<BR/>+ the normal mvn structure (src/test & src/main/resources - currently not used)Ales Justinhttps://www.blogger.com/profile/12192475150339948029noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-74767764697773361202009-01-26T11:48:00.000+00:002009-01-26T11:48:00.000+00:00FWIW by default we tend to use GuiceyFruit's JNDI ...FWIW by default we tend to use GuiceyFruit's JNDI provider when working with Camel; so that its easy to use Guice to IoC components and endpoints and expose them into JNDI so they are easily used by URI or endpoint name in CamelJames Strachanhttps://www.blogger.com/profile/12591119339035350067noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-42308543268384834512009-01-26T11:38:00.000+00:002009-01-26T11:38:00.000+00:00OK, I'll prepare a patch.This is the last post her...OK, I'll prepare a patch.<BR/><BR/>This is the last post here,<BR/>I'll move future discussion to the dev forum.<BR/><BR/>Yeah, there are only 2 Registry impls (OK, now three :-)).<BR/>JNDI and Spring's AppContext.<BR/><BR/>I guess Guice doesn't have one,<BR/>since handling Guice's beans by name, is not exactly why Guice was created in the first place.Ales Justinhttps://www.blogger.com/profile/12192475150339948029noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-14674064184643698832009-01-26T11:29:00.000+00:002009-01-26T11:29:00.000+00:00Yes please - we love contributions & patches. ...Yes please - we love contributions & patches. See the <A HREF="http://camel.apache.org/contributing.html" REL="nofollow">sections on creating and submitting patches</A>.<BR/><BR/>It might be easier to continue this conversation on the <A HREF="http://camel.apache.org/discussion-forums.html" REL="nofollow">Camel developer forum</A> as I'm sure other camel riders are interested.<BR/><BR/>In summary - Camel tries to abstract the IoC container so its kinda IoC agnostic; working nicely with Guice or Spring or anything else -e.g. JBossMC.<BR/><BR/>The main interface for hooking into the IoC container is the <A HREF="http://camel.apache.org/registry.html" REL="nofollow">Registry</A> which is lazily created by the CamelContext which is then used to lookup components, endpoints, beans by name.<BR/><BR/>When using Spring, this is the ApplicationContext - otherwise it defaults to JNDIJames Strachanhttps://www.blogger.com/profile/12591119339035350067noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-47489888566780232502009-01-21T17:01:00.000+00:002009-01-21T17:01:00.000+00:00I've (locally) added camel-jbossmc to components (...I've (locally) added camel-jbossmc to components (and fixed all necessary pom.xml's).<BR/>How to get this in? Patch?<BR/><BR/>My Registry impl is trivial.<BR/>Is that really it?<BR/><BR/>What's the purpose of all the Guice or Spring glue code then?<BR/>If you could just point me to some docs, or should I look at the code?Ales Justinhttps://www.blogger.com/profile/12192475150339948029noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-91007616523794486762009-01-21T15:43:00.000+00:002009-01-21T15:43:00.000+00:00OK, thanks for the info.I was finally able to buil...OK, thanks for the info.<BR/><BR/>I was finally able to build the Camel project (heap space problems), so I'll have a look asap.Ales Justinhttps://www.blogger.com/profile/12192475150339948029noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-14893809417764993772009-01-21T15:33:00.000+00:002009-01-21T15:33:00.000+00:00Sure! Am sure JBoss Microcontainer users who want ...Sure! Am sure JBoss Microcontainer users who want to use Camel will find it handy.<BR/><BR/>It should be relatively easy - the default Registry uses the current JNDI context.<BR/>http://camel.apache.org/registry.html<BR/><BR/>if there's some other kind of way of looking up configured endpoints / components / beans in JBoss Microcontainer you might wanna expose that in a custom Registry implementation; that should mostly be it I thinkJames Strachanhttps://www.blogger.com/profile/12591119339035350067noreply@blogger.comtag:blogger.com,1999:blog-637417304187784899.post-56531775445912172652009-01-21T08:24:00.000+00:002009-01-21T08:24:00.000+00:00Any interest in integrating Camel with JBoss Micro...Any interest in integrating Camel with JBoss Microcontainer (same way as you do Guice or Spring)?<BR/><BR/>ps: I'm just building the project to have a quick peek at how it's done - the Guice partAles Justinhttps://www.blogger.com/profile/12192475150339948029noreply@blogger.com