Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'd use a dynamic producer, using a <code>Qualifier</code> to identify the desired environment</p> <pre><code>// The qualifier for the production/qa/unit test @Qualifier @Retention(RetentionPolicy.RUNTIME) @Target({ElementType.TYPE, ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER}) public @interface Stage { String value() default "production"; } // The interface for the stage-dependant service public interface Greeting{ public String sayHello(); } // The production service @Stage("production") public class ProductionGreeting implements Greeting{ public String sayHello(){return "Hello customer"; } } // The QA service @Stage("qa") public class QAGreeting implements Greeting{ public String sayHello(){return "Hello tester"; } } // The common code wich uses the service @Stateless public class Salutation{ @Inject Greeting greeting; public String sayHello(){ return greeting.sayHello(); }; } // The dynamic producer public class GreetingFactory{ @Inject @Any Instance&lt;Greeting&gt; greetings; public String getEnvironment(){ return System.getProperty("deployenv"); } @Produces public Greeting getGreeting(){ Instance&lt;Greeting&gt; found=greetings.select( new StageQualifier(getEnvironment())); if (!found.isUnsatisfied() &amp;&amp; !found.isAmbiguous()){ return found.get(); } throw new RuntimeException("Error ..."); } public static class StageQualifier extends AnnotationLiteral&lt;Stage&gt; implements Stage { private String value; public StageQualifier(String value){ this.value=value; } public String value() { return value; } } } </code></pre> <p>So here the container injects all available <code>Greeting</code> implementations into <code>GreetingFactory</code>, which in turn serves as <code>@Producer</code> for the intended one, basing the decision on the system property 'deployenv'.</p>
    singulars
    1. This table or related slice is empty.
    1. POMultiple CDI configuration profiles (devel, beta, qa, production) in one war?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USCarlo Pellegrini
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMultiple CDI configuration profiles (devel, beta, qa, production) in one war?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the example source code. It's an interesing example for @Produces, it seems I would have to write a Factory for every class that exists in multiple variations and that could be a few. It would also get messy if I have a dozend "@Inject String password" variables as I would have to use qualifiers to differentiate the several String types. So it does not seem to scale for for big applications, or?
      singulars
      1. PO
      1. USlathspell
    2. COWell, it's the price to pay to type safeness... Besides, the `@Stage` qualifier could be used for all your configurable types, the same could be said for the `GreetingFactory` which could produce all the dynamically injectable beans. As for the `@Inject String password`, you could introduce a single qualifier, defining the origin property as in `@Inject @Config("db.password") String password`. Another (more drastic) approach could be leveraging the portable extension API.
      singulars
      1. PO
      1. USCarlo Pellegrini
    3. COHow do you switch between stages in your code? In other words, where is the stage defined/configured and what file does the maven build need to change?
      singulars
      1. PO
      1. USWeb Devie
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload