Yes  OfbizdemoUiLabels created as expected with contents ok as far as I can 
see.  Looks like the plugin creation has a problem.  I am checking the 
component against one created in 15.12.


Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Jacques Le Roux<mailto:[email protected]>
Sent: 18 February 2017 19:06
To: [email protected]<mailto:[email protected]>
Subject: Re: createComponent task not in ofbiz16.11

Mike,

It seems you created an Ofbizdemo component and it is missing en_GB 
OfbizdemoUiLabels. But this should normally default (for all languages) to en.

Please check that you have a OfbizdemoUiLabels.xml in your component (normally 
created by plugin creation)

Jacques


Le 18/02/2017 à 18:35, mike Butler a écrit :
> Thank Jacques
>
> Created plugin OK.
> Ran gradlew  cleanAll loadDefault
> Ran gradlew ofbiz
>
> All OK however when running https://localhost:8443/ofbizdemo/control/main I 
> get error:
>
> org.apache.ofbiz.widget.renderer.ScreenRenderException: Error rendering 
> screen [component://common/widget/CommonScreens.xml#login]: 
> org.apache.ofbiz.widget.renderer.ScreenRenderException: Error rendering 
> screen [component://ofbizdemo/widget/CommonScreens.xml#main-decorator]: 
> java.lang.IllegalArgumentException: Could not find resource bundle 
> [OfbizdemoUiLabels] in the locale [en_GB] (Could not find resource bundle 
> [OfbizdemoUiLabels] in the locale [en_GB]) (Error rendering screen 
> [component://ofbizdemo/widget/CommonScreens.xml#main-decorator]: 
> java.lang.IllegalArgumentException: Could not find resource bundle 
> [OfbizdemoUiLabels] in the locale [en_GB] (Could not find resource bundle 
> [OfbizdemoUiLabels] in the locale [en_GB]))
>
> Any ideas how to fix?
>
>
>
>
> Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>
> From: Jacques Le Roux<mailto:[email protected]>
> Sent: 18 February 2017 13:23
> To: [email protected]<mailto:[email protected]>
> Subject: Re: createComponent task not in ofbiz16.11
>
> There is also this wiki page mostly based on the main README.md but with some 
> migration advices and such
>
> https://cwiki.apache.org/confluence/display/OFBIZ/From+Ant+to+Gradle
>
> Jacques
>
>
> Le 18/02/2017 à 12:45, mike Butler a écrit :
>> Great. Thanks
>>
>>
>> Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>>
>> From: Taher Alkhateeb<mailto:[email protected]>
>> Sent: 18 February 2017 12:35
>> To: [email protected]<mailto:[email protected]>
>> Subject: Re: createComponent task not in ofbiz16.11
>>
>> Yeah the plugins should probably replace hot-deploy but in your release.
>> This is still on-going in trunk.
>>
>> The detailed documentation that you need is available in README.md at the
>> top level directory.
>>
>> On Sat, Feb 18, 2017 at 2:27 PM, mike Butler <[email protected]>
>> wrote:
>>
>>> Thanks for prompt reply
>>>
>>> Are plugins intended to replace hot-deploy components or will
>>> createComponent be reintroduced.
>>>
>>> What is the format for createPlugin task.  Nothing found in user
>>> documentation!
>>>
>>>
>>>
>>> Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for
>>> Windows 10
>>>
>>> From: Taher Alkhateeb<mailto:[email protected]>
>>> Sent: 18 February 2017 12:08
>>> To: [email protected]<mailto:[email protected]>
>>> Subject: Re: createComponent task not in ofbiz16.11
>>>
>>> Hello mike. Yeah the alternative is to call the task createPlugin. It would
>>> do the same thing but create the component in /specialpurpose and add it to
>>> component-load.xml. This was due to the transitional switch to plugins
>>> (long story)
>>>
>>> On Sat, Feb 18, 2017 at 2:05 PM, mike Butler <[email protected]>
>>> wrote:
>>>
>>>> I have installed Ofbiz16.11 and want to use the createComponent task but
>>> I
>>>> get 'createComponent' not found in root project 'ofbiz' and when I
>>> ‘gradlew
>>>> tasks’ or gradlew tasks –all, createComponent it is not in the list
>>>> returned.
>>>>
>>>> I cannot find anything in the archives about this.
>>>> Has the command been removed?
>>>>
>>>>
>>
>

Reply via email to