3 Replies Latest reply on Oct 6, 2006 7:17 PM by Pete Muir

    Default namming strategy for components

    Sebastián Fiorentini Newbie

      Exists a default naming strategy for components?
      I have the following situation:

      I'm starting to build a large-scale app which will contain about 800+ components. I really need the "name" attribute of @Name annotation to be optional. If no "name" is specified, the name will be the className.

      Example

      package a.b;

      @Name
      @Stateful
      public class C{
      ..
      }

      then, component C will be named a.b.C (equals to assign name="a.b.C" in the @Name annotation).

      My intention is to use @In in a seamless way, because with a huge number of components, that would become a knighmare to detect errors (at runtime)

      Regards,
      Sebastian