[Yanel-dev] Setting XSL for a resource's view

Balz Schreier balz.schreier at gmail.com
Wed Oct 13 11:36:41 CEST 2010


That looks like very much what I was looking for. This would actually be
ideal for all resources, not that every resource has another protocol...

I'll have a look at it too, once I have time for this.

Cheers
Balz

On Wed, Oct 13, 2010 at 11:00 AM, simon <simon at 333.ch> wrote:

> Balz Schreier schrieb:
>
>  Thanks,
>>
>> so there are no standard prefixes defined in order to tell the resource =
in
>> which repository to look it up?
>>
>>
> this should be possible via the right protocol. see
> http://yanel.org/en/documentation/basic-xml-resource-type.html#xsltprotoc=
ol
> yanelrepo:REALM_ID:REPO_ID should do the trick. but i'm not sure if this
> correctly implemented. i've never tested this.
>
> cheers
> simon
>
>
>  Cheers
>> Balz
>>
>> On Wed, Oct 13, 2010 at 10:28 AM, simon <simon at 333.ch> wrote:
>>
>>
>>
>>> Michael Wechner schrieb:
>>>
>>>  On 10/7/10 7:31 PM, Balz Schreier wrote:
>>>
>>>
>>>> I actually meant any kind of resource type.
>>>>> I would like to know what prefixes are allowed in the resource.xml fi=
le
>>>>> in the section below.
>>>>>
>>>>>
>>>>>
>>>> You can do anything within
>>>>
>>>> <yanel:custom-config>
>>>> ...
>>>> </yanel:custom-config>
>>>>
>>>> and access it with
>>>>
>>>>
>>>> src/core/java/org/wyona/yanel/core/ResourceConfiguration.java#getCusto=
mConfiguration()
>>>>
>>>>
>>>> Cheers
>>>>
>>>> Michael
>>>>
>>>>
>>>>
>>> hi balz
>>>
>>> as michail said, custom-config can be anything. but in case of the
>>> usecase-resource see:
>>> http://yanel.org/en/documentation/executable-usecase-resource.html for
>>> the
>>> possible options.
>>>
>>> HTH
>>> simon
>>>
>>>
>>>
>>>> Cheers
>>>>> Balz
>>>>>
>>>>>
>>>>> On Thu, Oct 7, 2010 at 6:20 PM, Michael Wechner <
>>>>> michael.wechner at wyona.com <mailto:michael.wechner at wyona.com>> wrote:
>>>>>
>>>>>   On 10/7/10 1:13 PM, basZero wrote:
>>>>>
>>>>>
>>>>>
>>>>>>   hi,
>>>>>>
>>>>>>   can somebody tell me what prefixes
>>>>>>
>>>>>>
>>>>>>
>>>>>   you mean the protocols/schemes? (like rthtdocs, ...)
>>>>>
>>>>>
>>>>>    are allowed withing the custom-config section in a resource.xml?
>>>>>
>>>>>
>>>>>>   <yanel:custom-config>
>>>>>>   <views>
>>>>>>   <view id=3D"default" type=3D"XML">
>>>>>>   * <xslt>rthtdocs:/registration.xsl</xslt>*
>>>>>>   * <xslt>yanelhtdocs:/html.xslt</xslt>*
>>>>>>   * <xslt>*
>>>>>>
>>>>>>   yanelrepo:<myrealmname>:app
>>>>>>
>>>>>>   **:/app/html.xslt</xslt>**
>>>>>>   <mime-type>application/xhtml+xml</mime-type>
>>>>>>   </view>
>>>>>>   <view id=3D"xml" type=3D"XML">
>>>>>>   <mime-type>application/xml</mime-type>
>>>>>>   </view>
>>>>>>   </views>
>>>>>>   </yanel:custom-config>
>>>>>>
>>>>>>   I only know that the third option (starting with yanelrepo) is
>>>>>>   working.
>>>>>>   But as I would be interested in hosting the XSLs in the htdocs
>>>>>>   folder,
>>>>>>
>>>>>>
>>>>>>
>>>>>   which htdocs folder? The one of the resource type?
>>>>>
>>>>>   I guess you are using the XML resource type which extends the
>>>>>   BasicXMLResource, right?
>>>>>
>>>>>   Cheers
>>>>>
>>>>>   Michael
>>>>>
>>>>>    I would like to know the syntax for other allowed configurations.
>>>>>
>>>>>
>>>>>>   Thanks
>>>>>>   Cheers
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>   --
>>>>>   Yanel-development mailing list Yanel-development at wyona.com
>>>>>   <mailto:Yanel-development at wyona.com>
>>>>>
>>>>>   http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>> --
>>> Yanel-development mailing list Yanel-development at wyona.com
>>> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>>
>>>
>>>
>>
>>
>>
>
> --
> Yanel-development mailing list Yanel-development at wyona.com
> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wyona.org/pipermail/yanel-development/attachments/2010101=
3/3f5c7504/attachment-0001.htm


More information about the Yanel-development mailing list