DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36273>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36273





------- Additional Comments From [EMAIL PROTECTED]  2005-08-19 16:43 -------
(In reply to comment #5)
> > First, I tried to use the jcr 'publet' for the import/export functionality.
> > Unfortunately, it was neither possible to add an admin tab
> 
> Good point. I already thought a lot about this and didn't find a reasonable
> solution. But IMO the issue should be addressed separately.
> 
> > nor to access a
> > publet's sitemap through the browser indepentently of a publication
> > for data generation.
> 
> What do you mean with "through the browser"?

Usually, publets are embedded in publication's and may use the publication URL
space, but a 'stand-alone' publet is not and needs some way to access its own
sitemap. E.g.

http://localhost:8888/publet/jcr/test.xml

But may be a (download) usecase can be used for that, too.

> BTW, I didn't find any JX templates
> in your patch, maybe that would clarify this ...
> 

It comes with the new classes, zipped.

> 
> > Additionally, I see some problems with access rights, as a
> > repository export/import should be reserved to administrators.
> > How are accessrights managed on the (standalone) publet level?
> 
> That's handled at usecase level for each publication (UsecasePolicyManager)
> 
> 
> > After it has proven impossible (at least to me) to code the import/export
> > functionality as a publet, I decided to start moving the import/export to 
> > the
> > core. It seems to me that the core is the right place for such a fundamental
> > operation as a repository export/import is.
> 
> OK, but that's another discussion. The decision to put functionality in a 
> module
> should not depend on the capabilites of the usecase framework. Modules should 
> be
> able to provide usecases like this one. If they aren't, the architecture has 
> to
> be improved.
> 

+1


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to