On Tue, Apr 8, 2008 at 9:42 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ... I'm wondering if JcrDefaultResourceTypeProvider is a good name for an
> interface :)...
+1 to renaming, brain fart of mine here ;-)
-Bertrand
+1
Regards
Felix
Am Dienstag, den 08.04.2008, 21:42 +0200 schrieb Carsten Ziegeler:
> Hi,
>
> I'm wondering if JcrDefaultResourceTypeProvider is a good name for an
> interface :)
> Something with "default" in the name always reminds me of an
> implementation
Hi,
I'm wondering if JcrDefaultResourceTypeProvider is a good name for an
interface :)
Something with "default" in the name always reminds me of an
implementation, so I suggest to simply call the interface
JcrResourceTypeProvider.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
;foo".
> Use a JcrDefaultResourceTypeProvider for path-based resource types
> --
>
> Key: SLING-340
> URL: https://issues.apache.org/jira/browse/SLING-340
> Project: Sl
On Tue, Mar 25, 2008 at 11:09 AM, Bertrand Delacretaz
<[EMAIL PROTECTED]> wrote:
> ...I'll create a first implementation today...
see https://issues.apache.org/jira/browse/SLING-340
-Bertrand
Use a JcrDefaultResourceTypeProvider for path-based resource types
--
Key: SLING-340
URL: https://issues.apache.org/jira/browse/SLING-340
Project: Sling
Issue Type: Improvement
adding a
JcrDefaultResourceTypeProvider interface (in o.a.s.jcr.resource), with
a getResourceTypeForItem(Item) method.
JcrDefaultResourceTypeProvider can then be used as an OSGi service, to
define the resourceType of a JCR Item being loaded, as follows:
1) Use the sling:resourceType if provided