[
https://issues.apache.org/jira/browse/RAVE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106638#comment-13106638
]
Marlon Pierce commented on RAVE-171:
------------------------------------
Here's a list of common use cases that I can think of that involve a developer
who would make a lot of local customizations. I assume this developer would
create a Maven project structure and depend upon the above jars, wars, and poms
(following the template in the SVN sandbox and
http://incubator.apache.org/rave/documentation/index.html). I think Ate's
organization will support these, but it is a good idea to enumerate the cases
as a sanity check.
1) Developer needs to override default authentication by extending existing
Rave User and other classes. This developer would depend upon
rave-security.jar and override rave-portal-resources.war. For example, the
developer may want to use LDAP.
2) Override, customize home.jsp and other "view" pages, CSS, javascript, etc.
This developer would override rave-portal-web and rave-portal-resources (?).
3) Override default lightweight DB with a production quality one.
4) Add additional fields to the User object and customize the backend DB.
5) Populate the portal with a large initial set of users.
6) Use only some part of Rave, such as user management, but develop all web
interfaces as standard web apps (ie no gadgets or widgets).
> Reorganize project to support better extension
> ----------------------------------------------
>
> Key: RAVE-171
> URL: https://issues.apache.org/jira/browse/RAVE-171
> Project: Rave
> Issue Type: Sub-task
> Reporter: Marlon Pierce
> Fix For: 0.4-INCUBATING
>
>
> Extension codes not in rave-portal src tree will need to be able to compile
> against that code. This can be done by modifying rave-portal/pom.xml so that
> it makes both a war and a jar and installs both in the local repository. The
> extension code should then have the appropriate dependency in its pom.xml
> Re-organize rave project in the following manner to support simpler extension
> by downstream integrators:
> Rave Project:
> |
> |__rave- components
> | |
> | |__rave-commons (Generic & common code that is usable in many
> different contexts, modules and projects)
> | |
> | |__rave-core (Core Model, Service& Repository classes that are used
> by multiple applications) [Widget, Person& related Classes]
> | |
> | |__rave-security (Security related classes) [User extends Person,
> Security Utilities, etc]
> |
> |__rave-providers
> | |
> | |__rave-opensocial (OpenSocial provider classes)
> | |
> | |__rave-w3c (W3C provider classes)
> |
> |__rave-portal (Core portal& webapp related features) [Regions, Pages,
> controllers, etc]
> |
> |__rave-shindig
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
