Hi Steve,
I'm not entirely sure that I understand where your questions
lie. But here's some info.
For FDS using the Java Adapter alone you would write a Java
assembler class whose purpose is to respond to messages that
request fills (for which you could have many different options),
get single items by identity and data updates.
Your fill methods can load up data lists in any manner which
you see fit and with any params that you need. There are two ways
to accomplish this:
- extend the AbstractAssembler class and just check the arg
list that gets passed into your fill method via reflection to
determine how the fill should be serviced
- do not extend AbstractAssembler but instead specify all of
your fill method variations in your destination definiition.
As for the schema - you probably want to take advantage of
nested collections / relationships and lazy loading. I picture the
Java version of your objects looking something like this:
Order
-----
order_no
date
total
Customer
Warehouse
Customer
--------
customer_no
customer_name
customer_phone
...
Warehouse
---------
warehouse_no
warehouse_name
warehouse_phone
...
Your destinations might look like this (not using
AbstractAssembler):
<destination adapter="java-adapter" id="Orders">
<properties>
<source>foo.bar.OrderAssembler</source>
<item-class>foo.bar.Order</item-class>
<scope>application</scope>
<metadata>
<identity property="order_no"/>
<many-to-one destination="Customers" property="customer"
lazy="true" />
<many-to-one destination="Warehouses"
property="warehouse" lazy="true" />
</metadata>
<server>
<fill-method>
<name>getOrders</name>
</fill-method>
<fill-method>
<name>getOrdersByCustomerNumber</name>
<params>int</params>
</fill-method>
<sync-method>
<name>syncPlayers</name>
</sync-method>
<get-method>
<name>getOrder</name>
</get-method>
<count-method>
<!-- Count all -->
<name>count</name>
</count-method>
<count-method>
<!-- Count by customer number -->
<name>count</name>
<params>int</params>
</count-method>
</server>
</properties>
</destination>
<destination adapter="java-adapter" id="Customers">
<properties>
<source>foo.bar.CustomerAssembler</source>
<item-class>foo.bar.Customer</item-class>
<scope>application</scope>
<metadata>
<identity property="customer_no"/>
</metadata>
....
</properties>
</destination>
<destination adapter="java-adapter" id="Warehouses">
<properties>
<source>foo.bar.WarehouseAssembler</source>
<item-class>foo.bar.Warehouse</item-class>
<scope>application</scope>
<metadata>
<identity property="warehouse_no"/>
</metadata>
....
</properties>
</destination>
Now the fill method(s) of the OrderAssembler would be
responsible for building the list of orders with the required
warehouse and customer info but then any updates would be routed to
their respective destination and pushed to anybody with fills that
include them either directly from their destinations or via the
OrderAssembler.
Does any of this help?
