Hey Ricky,
Great question. Just to add to this list, for PHP web application
developers there is also the recently added 'cas-browser' module in the
Balance component (trunk/balance/modules/cas-browser).
These front ends have evolved on independent time lines to meet
different needs in different environments. There are probably other
folks who can better talk to 1-3, but (4) and (5) are related in that
the Wicket web app in (4) is a module that encapsulates functionality
for interacting with the File Manager in the context of the OODT PCS
Operator Interface (OpsUI) (5). The OpsUI (5) provides a high-level
"operational" perspective of a data management pipeline consisting of
one or more of the File Manager, Resource Manager, and Workflow Manager
components.
-Andrew.
On 4/23/12 11:58 AM, Nguyen, Ricky wrote:
Seems like there are many different front ends for the file manager.
1) app/fmbrowser - a Swing application
2) webapp/fmprod - a REST service
3) webapp/fmbrowser - wicket web app, not sure what this is?
4) webapp/components - wicket web app, not sure what this is?
5) pcs/opsui - wicket web app, demo'd at apachecon '11, what can it do for
filemgr?
3, 4 and 5 all appear to have "product browsing" capabilities (what I'm
guessing from looking at the java class names). What are the differences between these
apps? Do they work together or have different roles? Are some deprecated in favor of
others?
Thanks,
Ricky
---------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain confidential
or legally privileged information. Any unauthorized review, use, disclosure
or distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of this original
message.
---------------------------------------------------------------------
--
Andrew F. Hart
http://people.apache.org/~ahart
