You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "David Jencks (JIRA)" <je...@portals.apache.org> on 2007/10/24 10:00:54 UTC
[jira] Updated: (JS2-794) Use xbean-spring to provide a
component-specific schema for spring bean configuration
[ https://issues.apache.org/jira/browse/JS2-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated JS2-794:
-----------------------------
Attachment: JS2-794.patch
schema generation project, some "annotated" components, and a few converted spring config files. I left the original spring xml in place, commented out, for handy reference in case we can determine if this breaks stuff.
> Use xbean-spring to provide a component-specific schema for spring bean configuration
> -------------------------------------------------------------------------------------
>
> Key: JS2-794
> URL: https://issues.apache.org/jira/browse/JS2-794
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Other
> Affects Versions: 2.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: JS2-794.patch
>
>
> I suggested that using xbean-spring to generate a component-specific schema for spring configuration would make configuring jetspeed easier, and this idea got some agreement on the dev list. I've done a little work in this direction but don't know if it actually works since 2.2 doesn't seem to build a functioning portal at the moment. I'm opening this issue to track work on this idea. So far I've added a schema generation project and added the javadoc "annotations" to get components into the schema for components mentioned in the administration and security-* spring config files. Committiing everything except the spring config files poses very little risk to functionality since the xbean context falls back to the normal spring context behavior when you aren't using the generated schema. Committing the spring config file changes might be riskier until we can more easily tell if they work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org