facebook

Dependent Deployment

  1. MyEclipse IDE
  2.  > 
  3. Feature Requests
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #300707 Reply

    Tony Herstell
    Participant

    When are we going to have the ability to
    “click in”
    and
    “click out”
    for a package/directory etc.

    I need to include/exclude packages (e.g. test, Mocks) etc. when I create an EAR.

    e.g.
    [ ] Exploded Deployment [ ] Packaged Deployment

    Scheme \/
    with mocks
    with tests
    etc.

    where my
    “with mocks” =
    [ ] include */mock/* [Add Include] [Add Remove]
    [ ] remove */bling/bong/*

    etc.

    This is getting very tiresome as it been promised for over a year!

    #300718 Reply

    support-joy
    Member

    balanceofpower,

    I have escalated this to the management and added this to our features tracker list. Thank you for posting your feature request.

    #300722 Reply

    Tony Herstell
    Participant

    Thanks…
    But this was promised a year ago.
    🙁

    Can this be expedited (this is probably quite easy!)

    #300723 Reply

    support-joy
    Member

    balanceofpower,

    The features that get added to the builds are a management decision. Questions such as – when, which release, etc are governed by feature requests per user and assigned priority. I have already escalated your request to the management.

    #320787 Reply

    Tony Herstell
    Participant

    Any movement on this?

    #320878 Reply

    Tony Herstell
    Participant

    From J6EE CDI Doco…
    This is what I was referring to in the other post…
    You wanted the thread to continue here.

    2.1.4. Alternatives
    We’ve already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation.

    public @Alternative
    class MockPaymentProcessor extends PaymentProcessorImpl { … }

    We normally annotate a bean @Alternative only when there is some other implementation of an interface it implements (or of any of its bean types). We can choose between alternatives at deployment time by selecting an alternative in the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module that uses it.

    Different modules can specify that they use different alternatives.

    We cover alternatives in more detail in Section 4.7, “Alternatives”.

    (Taken from CDI Weld doco – JBoss – Attached)

    I can see that a dependent deployment COULD:

      set the alternative in the beans.xml OR
      substitute complete packages in what is deployed (as the container would be happy as long as it find ONLY ONE possible injectable bean)

    Your Thoughts?

    Attachments:
    You must be logged in to view attached files.
    #320934 Reply

    support-joy
    Member

    balanceofpower,

    I shall investigate and get back to you on this.

Viewing 7 posts - 1 through 7 (of 7 total)
Reply To: Dependent Deployment

You must be logged in to post in the forum log in