Thanks for report Skip, 

So we lost a functionality, would you mind opening a Jira for that?

Thanks

Jacques

From: "Skip" <s...@thedevers.org>
> view-entity used to be able to be extended.  I used it in several places in
> 9.x.  They are supposed to be extendable currently in entitymodel.xsd.
> 
> However, if you extend one, you get a runtime error about the base
> view-entity not existing even when the base entity and the extended one are
> in the same file.
> 
> Not a big deal as I just modified your view, but I like to keep my changes
> in hot-deploy to make upgrading easier.
> 
> Skip
> 
> -----Original Message-----
> From: Jacques Le Roux [mailto:jacques.le.r...@les7arts.com]
> Sent: Saturday, June 01, 2013 2:29 PM
> To: user@ofbiz.apache.org
> Subject: Re: But in CategoryTree.groovy
> 
> 
> Adrian said it's possible, since there are no OOTB examples I'm not so sure
> (I never tried IIRW)
> Here are 3 years old answers which might help
> 
> http://markmail.org/message/4d3gjql3xkuifmrg
> 
> Jacques
> 
> From: "Skip" <s...@thedevers.org>
>> BTW
>>
>> There is still another bug.  I am probably the only one that uses it, but
>> you cannot extend a view entity.  Give it a try.  I detailed it pretty
>> thoroughly in a previous email.  It is repeated here:
>>
>> As a test, I extended OrderHeaderAndItems in a different module in exactly
>> the same way and got the same error.
>>
>> Here is the extend that is causing the error.  It is exactly the same as
> my
>> 9.x version which works fine:
>>    <extend-entity entity-name="WorkEffortAndPartyAssign">
>>        <relation type="one-nofk" title="Current"
>> rel-entity-name="StatusItem">
>>            <key-map field-name="currentStatusId"
>> rel-field-name="statusId"/>
>>        </relation>
>>        <relation type="one-nofk" rel-entity-name="WorkEffortType">
>>            <key-map field-name="workEffortTypeId"/>
>>        </relation>
>>        <relation type="one-nofk" rel-entity-name="WorkEffortPurposeType">
>>            <key-map field-name="workEffortPurposeTypeId"/>
>>        </relation>
>>    </extend-entity>
>>
>> As a further test, I commented these out from jobshop and I copied this
>> extend-entity into the same entitymodel_view.xml file as the the
> definition
>> for WorkEffortAndPartyAssign in the workeffort project and got exactly the
>> same error.
>>
>>
>> -----Original Message-----
>> From: Jacques Le Roux [mailto:jacques.le.r...@les7arts.com]
>> Sent: Thursday, May 30, 2013 6:38 AM
>> To: user@ofbiz.apache.org
>> Subject: Re: But in CategoryTree.groovy
>>
>>
>> Thanks for report Skip,
>>
>> BTW you must have missed something, findAll does not exist anymore for 3
>> years ;)
>> http://svn.apache.org/viewvc?view=revision&revision=938947
>>
>> Using
>> prodCatalogs = delegator.findList("ProdCatalog", null, null, null, null,
>> false);
>> Should be the way. Could you please confirm before I commit?
>>
>> Thanks
>>
>> Jacques
>>
>> From: "Skip" <s...@thedevers.org>
>>> There is a line at 50 that sez:
>>>
>>> prodCatalogs = delegator.findByAnd("ProdCatalog");
>>>
>>> This causes a groovy ambiguious error when you go to the catalog screen
> in
>>> 12.04.
>>>
>>> Changing this to:
>>> prodCatalogs = delegator.findAll("ProdCatalog");
>>>
>>> Fixes the problem.
>>>
>>> I expect you guys already did this, there here it is for any others like
>> me
>>> that just download the zip file.
>>>
>>> Skip
>>>
>>
>

Reply via email to