Back to bug 1326806
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Marco Rietveld | 2016-04-13 12:49:01 UTC | Priority | unspecified | urgent |
| Status | NEW | ASSIGNED | ||
| CC | kverlaen | |||
| QA Contact | lpetrovi | tlivora | ||
| Lukáš Petrovický | 2016-04-14 15:44:46 UTC | CC | lpetrovi | |
| Alessandro Lazarotti | 2016-04-14 22:46:00 UTC | CC | alazarot | |
| Alessandro Lazarotti | 2016-04-14 22:47:35 UTC | CC | tradej | |
| Flags | needinfo?(tradej) | |||
| Tomas 'Sheldon' Radej | 2016-04-15 11:07:19 UTC | Link ID | JBoss Issue Tracker BXMSDOC-270 | |
| Flags | needinfo?(tradej) | |||
| Marek Czernek | 2016-04-19 10:40:32 UTC | CC | mczernek | |
| Marco Rietveld | 2016-04-19 19:21:19 UTC | Summary | Serialization problems on websphere as a result of BZ-1310739 | [QA] (6.2.z)Serialization problems on websphere as a result of BZ-1310739 |
| Marco Rietveld | 2016-04-20 11:37:50 UTC | Doc Text | Cause: The use of the Apache Wink framework in Webspher. Consequence: User-defined classes in deployments will be incorrectly deserialized and serialized when using the REST API. Fix: When setting up the application in websphere, it's important to add the following (custom) JVM property: property: org.apache.wink.jaxbcontextcache value: off This property makes sure that the websphere apache wink framework does not cache JAXBContext instances, which are responsible for serialization and deserialization of classes to XML. Otherwise, if these JAXBContext instances are cached, de/serialization of user-defined classes can fail or be incorrectly performed. (Furthermore, caching JAXBContext instances is unnecessary for performance since the BxMS (REPLACE!) framework is already doing this.) Result: User-defined classes in deployments will be incorrectly deserialized and serialized when using the REST API. |
|
| Tomas 'Sheldon' Radej | 2016-04-25 11:56:37 UTC | Docs Contact | tradej | |
| Doc Text | Cause: The use of the Apache Wink framework in Webspher. Consequence: User-defined classes in deployments will be incorrectly deserialized and serialized when using the REST API. Fix: When setting up the application in websphere, it's important to add the following (custom) JVM property: property: org.apache.wink.jaxbcontextcache value: off This property makes sure that the websphere apache wink framework does not cache JAXBContext instances, which are responsible for serialization and deserialization of classes to XML. Otherwise, if these JAXBContext instances are cached, de/serialization of user-defined classes can fail or be incorrectly performed. (Furthermore, caching JAXBContext instances is unnecessary for performance since the BxMS (REPLACE!) framework is already doing this.) Result: User-defined classes in deployments will be incorrectly deserialized and serialized when using the REST API. | When Business Central is installed on IBM WebSphere, direct REST calls involving user-defined classes fail due to a serialization issue. The only workaround is using the Java REST client (if possible). | ||
| Alessandro Lazarotti | 2016-04-25 16:01:46 UTC | Status | ASSIGNED | MODIFIED |
| Blocks | 1327765, 1327763 | |||
| Ryan Zhang | 2016-05-01 22:48:07 UTC | Status | MODIFIED | ON_QA |
| Target Release | --- | 6.2.3 | ||
| Target Milestone | --- | CR1 | ||
| Tomas Livora | 2016-05-09 09:45:08 UTC | Status | ON_QA | VERIFIED |
| John Skeoch | 2016-09-20 05:06:43 UTC | CC | smcgowan | |
| John Skeoch | 2016-09-20 05:15:06 UTC | Assignee | mrietvel | smcgowan |
| PnT Account Manager | 2018-01-31 04:43:59 UTC | QA Contact | tlivora | lpetrovi |
| Alasdair Kergon | 2020-03-27 19:45:44 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | EOL | ||
| Last Closed | 2020-03-27 19:45:44 UTC |
Back to bug 1326806