Keep in mind that an extension can define more than one subsystem, and a
module can define more than one extension.
As an example of the latter, org.jboss.as.connector:main uses 3 lines in
the META-INF/services/org.jboss.as.controller.Extension file to define 3
extension impls. Each of those registers a single subsystem.
That same thing could have been done differently by having a single
Extension impl that registered 3 subsystems. If that had been done, the
extension impl would not fit nicely in an org.wildfly.subsystem.<blah>
package.
On 4/29/13 9:18 AM, David M. Lloyd wrote:
I guess. Keeping in mind that eventually extensions will (possibly)
be
loaded by assembled module name, so they may have to change again at
some point.
On 04/29/2013 09:16 AM, Tomaž Cerar wrote:
> probably same should also apply to module names.
>
> so we would have org.wildfly.subsystem.<name>
>
>
> On Mon, Apr 29, 2013 at 4:09 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com
> <mailto:tomaz.cerar@gmail.com>> wrote:
>
> Sounds ok,
>
> probably having org.wildfly.extension.<>
>
> that would too much :)
>
>
>
> On Mon, Apr 29, 2013 at 4:07 PM, David M. Lloyd
> <david.lloyd(a)redhat.com <mailto:david.lloyd@redhat.com>> wrote:
>
> Maybe do:
>
> org.wildfly.subsystem.<blah>
>
> because there will be wildfly stuff which isn't subsystems and which
> might have names that conflict. I'd even suggest
> "org.wildfly.as.subsystem..." but that might be too much.
>
> On 04/29/2013 08:58 AM, Tomaž Cerar wrote:
> > Hi,
> >
> > What should be package name for new stuff being added to WildFly?
> >
> > org.wildfly.<subsystem-name>
> > or
> > org.wildfly.as <
http://org.wildfly.as>
> <
http://org.wildfly.as>.<subsystem-name>
> > or something else?
> >
> > I would go for org.wildfly.<subsystem-name>
> >
> >
> >
> > this mostly applies to new subsystems and as we agreed we
> won't rename
> > packages for existing code until it break compatibility.
> >
> >
> >
> > --
> > tomaz
> >
> >
> > _______________________________________________
> > wildfly-dev mailing list
> > wildfly-dev(a)lists.jboss.org
<mailto:wildfly-dev@lists.jboss.org>
> >
https://lists.jboss.org/mailman/listinfo/wildfly-dev
> >
>
>
> --
> - DML
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat