You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "André Dietisheim (JIRA)" <ji...@apache.org> on 2010/06/04 12:44:55 UTC

[jira] Updated: (CLEREZZA-224) eed the "current language information" in the widget.

     [ https://issues.apache.org/jira/browse/CLEREZZA-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

André Dietisheim updated CLEREZZA-224:
--------------------------------------

    Comment: was deleted

(was: File: bundle://85.0:1/org/apache/clerezza/web/resources/style/headed-page-template.ssp

			
			

			
		

		

Description:

				

java.lang.RuntimeException: no renderer could be created for <http://localhost:8080/news/2010/06/04/AEOEUEaoeue> (in [<http://localhost:8080/news/2010/06/04/AEOEUEaoeue> <http://clerezza.org/2009/04/digitalassetmanager#hasResourcePicker> org.apache.clerezza.rdf.core.BNode@1c8638a., <http://localhost:8080/news/2010/06/04/AEOEUEaoeue> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://clerezza.org/2009/08/platform#HeadedPage>., org.apache.clerezza.rdf.core.BNode@1c8638a <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://clerezza.org/2009/04/digitalassetmanager#ResourcePicker>.]), edit-naked,[application/xhtml+xml]

		
		

Stack trace:

java.lang.RuntimeException: no renderer could be created for <http://localhost:8080/news/2010/06/04/AEOEUEaoeue> (in [<http://localhost:8080/news/2010/06/04/AEOEUEaoeue> <http://clerezza.org/2009/04/digitalassetmanager#hasResourcePicker> org.apache.clerezza.rdf.core.BNode@1c8638a., <http://localhost:8080/news/2010/06/04/AEOEUEaoeue> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://clerezza.org/2009/08/platform#HeadedPage>., org.apache.clerezza.rdf.core.BNode@1c8638a <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://clerezza.org/2009/04/digitalassetmanager#ResourcePicker>.]), edit-naked,[application/xhtml+xml]
	at org.apache.clerezza.platform.typerendering.CallbackRendererImpl.render(CallbackRendererImpl.java:46)
	at headed_page_templateef9efe8ecb94c7900ccca3a7da7b1d4e$.render$1(headed_page_templateef9efe8ecb94c7900ccca3a7da7b1d4e:65529)
	at headed_page_templateef9efe8ecb94c7900ccca3a7da7b1d4e$.run$1(headed_page_templateef9efe8ecb94c7900ccca3a7da7b1d4e:49)
	at headed_page_templateef9efe8ecb94c7900ccca3a7da7b1d4e$$anonfun$main$1$$anonfun$apply$1.apply(headed_page_templateef9efe8ecb94c7900ccca3a7da7b1d4e:59)
	at scala.util.DynamicVariable.withValue(DynamicVariable.scala:73)
	at scala.Console$.withOut(Console.scala:84)
	at scala.Console$.withOut(Console.scala:102)

Any idea what's the reason?)

> eed the "current language information" in the widget. 
> ------------------------------------------------------
>
>                 Key: CLEREZZA-224
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-224
>             Project: Clerezza
>          Issue Type: New Feature
>            Reporter: Oliver Strässer
>            Priority: Critical
>
> Hi all
> I'll need the "current language Information" in the widget.
> Use Case 1:
> I create an App which contains information about animals in different languages. I have implemented a template widget called "display-pet" which is language independed. This widget is from RDF type "PetWidget" and has a property wwfch:describePet, which points to a description of a pet. Corresponding to the current language of the page the description of the animal should be displayed.
> How can I propagte the language information from the page to my widget?
> Use Case 2:
> I display an interactive flash content. This flash content requests an xml with all pet information.  This flash needs the current language information of the page too. - to request the correct language and display all labels in the correct language.
> 1 . approach : the graphnode, that i receive in the ssp file (wich renders the pet or include the flash content), has an triple which holds the language information of the page.
> 2 . approach : the individual language is added to the context graphnode.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.