Hey Lincoln,
Thanks for asking!
I was planning to highlight WildFly's native module system
capabilities instead of building something on it. But if I do then
would certainly look at Forge Addon service mechanism.
Arun
On Sun, Feb 23, 2014 at 10:07 PM, Lincoln Baxter, III
<lincolnbaxter(a)gmail.com> wrote:
Hey Arun,
Are you trynig to do this using standalone JBoss Modules? If so... why not
look at the work we've done with Furnace -
https://github.com/forge/furnace
It's basically CDI-light, and is what we use to power the Forge Addon
service mechanism. I'd be happy to share more details if this is something
you're interested in.
If you're trying to use Wilfly's native module system and service container
for this, then I can't be of much help :) But thought I'd ask.
~Lincoln
On Tue, Feb 18, 2014 at 8:36 PM, Arun Gupta <arun.gupta(a)gmail.com> wrote:
>
> Adding beans.xml in the implementation module solved the issue.
>
> I updated the implementation module and copied the JAR file over to
> org/samples/greet/main directory but had to restart the application
> server in order to pick up the new implementation.
>
> Are the modules not dynamically loaded ? Can this behavior be enabled ?
>
> I'm trying to figure out if I can implement something like OSGi
> service using JBoss Modules.
>
> Arun
>
>
>
> On Tue, Feb 18, 2014 at 2:07 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com>
> wrote:
> > We found inital issue, it was typo in modules.xml instead of module.xml
> >
> > But there are different issues :)
> >
> >
> > On Tue, Feb 18, 2014 at 10:38 PM, David M. Lloyd
> > <david.lloyd(a)redhat.com>
> > wrote:
> >>
> >> On 02/18/2014 02:29 PM, Arun Gupta wrote:
> >> > On Tue, Feb 18, 2014 at 2:05 AM, Tomaž Cerar
<tomaz.cerar(a)gmail.com>
> >> > wrote:
> >> >> What do you mean resolution of service?
> >> >> you have some service registered via ServiceLoader pattern?
> >> > Yes, the API, Impl, and and application module are defined at:
> >> >
> >> >
> >> >
https://github.com/arun-gupta/wildfly-samples/tree/master/jboss-modules
> >> >
> >> >>
> >> >> in that case you need to import also services when you are
> >> >> "importing"
> >> >> module to your application.
> >> > OK, I'm missing this step.
> >> >
> >> > How can this be done ?
> >> >
> >> >>
> >> >> as for logging goes, you can set org.jboss.modules to TRACE
> >> > I enabled TRACE logging but saw no additional log entries. Here is
> >> > how
> >> > I enabled it:
> >> >
> >> > /subsystem=logging/logger=org.jboss.modules:add
> >> >
> >> >
> >> >
/subsystem=logging/logger=org.jboss.modules:write-attribute(name="level",
> >> > value="TRACE")
> >>
> >> The corresponding handler (console or file or whatever) has to be
> >> enabled at TRACE as well.
> >>
> >> --
> >> - DML
> >> _______________________________________________
> >> wildfly-dev mailing list
> >> wildfly-dev(a)lists.jboss.org
> >>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
> >
> >
> >
> > _______________________________________________
> > wildfly-dev mailing list
> > wildfly-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
> --
>
http://blog.arungupta.me
>
http://twitter.com/arungupta
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."