Hi All,
The current structure and the design is something we agreed and implemented
sometimes back. I have discussed this issue with Registry team today and
tried following fix within the Lifecycle executor to avoid caching problem.
ArtifactCache artifactCache =
ArtifactCacheManager.getCacheManager().getTenantArtifactCache(CurrentSession.getTenantId());
if(artifactCache != null){
artifactCache.invalidateArtifact(resourcePath);
}
But still same issue appears after ArtifactCache invalidation.
Appreciate your feedback on this issue.
On Mon, Apr 29, 2013 at 10:58 PM, Ajanthan Balachandran
<[email protected]>wrote:
>
>
>
> On Fri, Apr 5, 2013 at 3:25 PM, Ashansa Perera <[email protected]> wrote:
>
>> Hi all,
>>
>> In an appfactory review held on end of last year, a suggestion had been
>> made to use a flip property for a resource than moving the resource from
>> one path to another when we are changing the LC ( promoting the app )
>> (thread subjected to "Updated Invitation: Review App Factory BPEL and
>> appfactory.xml @ Fri Nov 16 3:30pm - 4:30pm")
>>
>> The current implementation is we store appversion.rxt under the relevant
>> LC stage (Development/Test/etc : image-1 ) and when an app promotion
>> happens we move the rxt from the current stage to the next stage (image-2
>> ). But Greg cache the resource for some time even after moving the resource
>> to the new stage and we have intermittently faced issues like [1] due to
>> this (image-3 : version 2.0.0 is in both Development and Testing).
>>
>> If the flip property mechanism is implemented, the registry resource
>> structure for AF will change and this should be followed by modifying most
>> of the logic related referring to app versions. ( This is the main reason
>> for us to hold the flip property implementation )
>>
> I don't understand why we need this flip property.If it only to identify
> lifecycle status of Rxt,There should a way to get the lifecycle status of
> the rxt(In App Factory management console if you list the app version rxts
> there is a column to display lc status).
>
>> Since there are inconsistencies with resource move we are thinking of
>> implementing the flipping property mechanism for GA.
>> Are there any other recommended ways of solving this issue?
>>
>> Thoughts are welcome.
>>
>> [1] https://wso2.org/jira/browse/APPFAC-830
>>
>> --
>> Thanks & Regards,
>>
>> Ashansa Perera
>> Software Engineer
>> WSO2, Inc
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> ajanthan
> --
> Ajanthan Balachandiran
> Software Engineer; WSO2, Inc.; http://wso2.com/
> email: ajanthan <http://goog_595075977>@wso2.com; cell: +94775581497
> blog: http://bkayts.blogspot.com/
>
> Lean . Enterprise . Middleware
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
Thank You.
Ranga.
--
Ranga Siriwardena
Software Engineer
Mobile: +94779808031
WSO2 Inc.
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
