[
https://issues.apache.org/jira/browse/SCB-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujimin updated SCB-589:
------------------------
Description:
1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge
2.consumer microserviceMeta will not save in microserviceMetaManager any more,
just like edge, use appManager
3.allow consumer schema set or method set bigger than contract
4.protobuf dynamic class created in microservice classloader
5.seems that can delete MicroserviceMetaManager
6.change consumer default versionRule from latest to all
7.edge remains task should be finished:
https://issues.apache.org/jira/browse/SCB-279
how jackson to process same name class but belongs to different classloader, if
classloader unloaded, will jackson still hold the classes?
was:
1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge
2.consumer microserviceMeta will not save in microserviceMetaManager any more,
just like edge, use appManager
3.allow consumer schema set or method set bigger than contract
4.protobuf dynamic class created in microservice classloader
5.seems that can delete MicroserviceMetaManager
6.edge remains task should be finished:
https://issues.apache.org/jira/browse/SCB-279
how jackson to process same name class but belongs to different classloader, if
classloader unloaded, will jackson still hold the classes?
> allow consumer upgrade before producer
> --------------------------------------
>
> Key: SCB-589
> URL: https://issues.apache.org/jira/browse/SCB-589
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Java-Chassis
> Reporter: wujimin
> Assignee: wujimin
> Priority: Major
>
> 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge
> 2.consumer microserviceMeta will not save in microserviceMetaManager any
> more, just like edge, use appManager
> 3.allow consumer schema set or method set bigger than contract
> 4.protobuf dynamic class created in microservice classloader
> 5.seems that can delete MicroserviceMetaManager
> 6.change consumer default versionRule from latest to all
> 7.edge remains task should be finished:
> https://issues.apache.org/jira/browse/SCB-279
>
> how jackson to process same name class but belongs to different classloader,
> if classloader unloaded, will jackson still hold the classes?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
