[
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.protobuf dynamic class created in microservice classloader
4.edge remains task should be finished:
https://issues.apache.org/jira/browse/SCB-279
5.seems that can delete MicroserviceMetaManager
how jackson to process same name class but belongs to different classloader, if
classloader unloaded, will jackson still reference 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.protobuf dynamic class created in microservice classloader
4.edge remains task should be finished:
https://issues.apache.org/jira/browse/SCB-279
5.seems that can delete MicroserviceMetaManager
> 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.protobuf dynamic class created in microservice classloader
> 4.edge remains task should be finished:
> https://issues.apache.org/jira/browse/SCB-279
> 5.seems that can delete MicroserviceMetaManager
>
> how jackson to process same name class but belongs to different classloader,
> if classloader unloaded, will jackson still reference the classes?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
