Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Two possibilities I can think of.</p> <p>1) Set a static reference. (A static variable, although typically frowned upon, is OK in this case, because there can only be 1 command line invocation). </p> <pre><code>public class MyApp { public static String[] ARGS; public static void main(String[] args) { ARGS = args; // create context } } </code></pre> <p>You can then reference the command line arguments in Spring via:</p> <pre><code>&lt;util:constant static-field="MyApp.ARGS"/&gt; </code></pre> <p>Alternatively (if you are completely opposed to static variables), you can:</p> <p>2) Programmatically add the args to the application context:</p> <pre><code> public class MyApp2 { public static void main(String[] args) { DefaultListableBeanFactory beanFactory = new DefaultListableBeanFactory(); // Define a bean and register it BeanDefinition beanDefinition = BeanDefinitionBuilder. rootBeanDefinition(Arrays.class, "asList") .addConstructorArgValue(args).getBeanDefinition(); beanFactory.registerBeanDefinition("args", beanDefinition); GenericApplicationContext cmdArgCxt = new GenericApplicationContext(beanFactory); // Must call refresh to initialize context cmdArgCxt.refresh(); // Create application context, passing command line context as parent ApplicationContext mainContext = new ClassPathXmlApplicationContext(CONFIG_LOCATIONS, cmdArgCxt); // See if it's in the context System.out.println("Args: " + mainContext.getBean("args")); } private static String[] CONFIG_LOCATIONS = new String[] { "applicationContext.xml" }; } </code></pre> <p>Parsing the command line arguments is left as an exercise to the reader. </p>
    singulars
    1. This table or related slice is empty.
    1. PODealing with command line arguments and Spring
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJustin Wrobel
    1. USflicken
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODealing with command line arguments and Spring
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 for the static reference. 6 lines of code are better than 20.
      singulars
      1. PO
      1. USLeonel
    2. COI liked very lot this solution and found this kinky way to solve the exercise:System.out.println("Args: " + mainContext.getBean("args")); String[] arg1 = (String[]) ((Collection)mainContext.getBean("args")).toArray(new String[0]); String o = arg1[0]; System.out.println(o);
      singulars
      1. PO
      1. UShephestos
 

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