Difference between "group" and "component" in QuickFIX/J

From the FIXWiki for Components:

Component blocks are sets of related data fields grouped together and are referenced by the component block name in messages that they are used in. Sometimes they are referred to as "Groups".

Component blocks are practical to be defined, and then reused in different message types. Sometimes a repeating group is just for one particular message and then it is not defined as a Component block.

View a component block as a reusable definition of fields. Such a component block may or may not contain a repeating group of fields.

For instance take the Parties component block which is used in many different messages types (see "Used In" on that page). Easy to define once and use in many definitions of messages.

Components aren't really... things. They're like macros in the FIX DataDictionary (DD). Many messages need the same set of fields, so instead of specifying the same fields in every message, the DD defines a component that other messages can include.

A Group, on the other hand, is a very real thing. It's a repeating sequence of fields that will appear 0 or more times in a message.

QuickFIX's (QF) programming interface largely ignores components as a concept. You can't extract a component from a message because a component isn't a concept in QF; you just extract the fields like any other field.

A hypothetical example: The following two message definitions are exactly the same.

1. With a component

   <message name="Automobile" msgtype="X" msgcat="app">
     <field name="Wheel" required="Y"/>
     <field name="Bumper" required="Y"/>
     <component name="Dashboard" required="Y"/>
   </message>
   
   <component name="Dashboard">
     <field name="Radio" required="Y"/>
     <field name="AirConditioner" required="Y"/>
     <field name="Heater" required="Y"/>
   </component>
   

2. Without a component

   <message name="Automobile" msgtype="X" msgcat="app">
     <field name="Wheel" required="Y"/>
     <field name="Bumper" required="Y"/>
     <field name="Radio" required="Y"/>
     <field name="AirConditioner" required="Y"/>
     <field name="Heater" required="Y"/>
   </message>
   

See? A component is pretty much just a macro.

Either way it's defined, you just end up calling msg.GetHeater() (or whatever).

Just going to add some information since the accepted answer is missing this information (probably due to the fact that it is about five years old now).

In QuickFIX/J you are actually able to get and set components. So you can for example simply copy the Instrument component from one message to another.

    @Test
    public void testComponent() throws Exception {
        final Instrument instrument = new Instrument();
        instrument.set(new Symbol("DELL"));
        instrument.set(new CountryOfIssue("USA"));
        instrument.set(new SecurityType(SecurityType.COMMON_STOCK));

        final quickfix.fix44.NewOrderSingle newOrderSingle = new quickfix.fix44.NewOrderSingle();
        newOrderSingle.set(instrument);

        final quickfix.fix44.ExecutionReport executionReport = new quickfix.fix44.ExecutionReport();
        executionReport.setComponent(newOrderSingle.getInstrument());

        System.out.println("NOS: " + newOrderSingle.toString().replace('\001', '|'));
        System.out.println("ER:  " + executionReport.toString().replace('\001', '|'));
    }

Output:

NOS: 8=FIX.4.4|9=28|35=D|55=DELL|167=CS|470=USA|10=233|
ER:  8=FIX.4.4|9=28|35=8|55=DELL|167=CS|470=USA|10=221|

Maybe this is also possible in the other QuickFIX language variants.