How to organise your classes

Posted: 9 June 2009 in Components, CSSDK, External, Java, SitePublisher, Teamsite, URLExternalTask, Worfklow models, Workflows

Supposing you work for a company called Acme, you would do well to organise your classes using the following structure:

customer_src/
    src/
        com/
            acme/
                workflow/    (for your URLExternalTask classes)
                datasources/ (for your datasources)
                utils/       (for your common teamsite classes)
                resourcebundles/ (for localisation)
                    AcmeResourceBundle.java (default language)
                    AcmeResourceBundle_fr.java (French version)
                    AcmeResourceBundle_jp.java (Japanese version)

livesite_customer_src
    src/
        com/
            acme/
                components/ (for your external components)
                utils/      (for your common livesite classes)

I’m sure there are other folders that could come to mind but this structure suits me just fine until now.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s