[
https://issues.apache.org/jira/browse/JAMES-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier reopened JAMES-2578:
-----------------------------------
While working on https://issues.apache.org/jira/browse/JAMES-3431 I discovered
that JMS & File mailqueue do still rely on serialization.
This is what motivates the re-open of this ticket.
Here are the options we have:
- Accept DSN feature do not work on tese implementations (not my prefered at
all!)
- Re-implement DSNParameters attribute mapping to not use collection
attributeValues. This work around the main issue for this specific use case of
attribute values. (I feel okay with that)
- Try to fix collection attributeValue java serialization is likely hard to
do, but also keeps java serialization around for longer in the code base.
Likely a dead-end.
- No longer rely on Java serialization for "JMS" & "File" mail queues. This
means either smart fallback code, or at worst an upgrade path with an empty
mail queue. That is by far my preferred option, and I will start community
discussions in that direction.
> MQs should not rely on Serializable
> -----------------------------------
>
> Key: JAMES-2578
> URL: https://issues.apache.org/jira/browse/JAMES-2578
> Project: James Server
> Issue Type: Improvement
> Reporter: Gautier DI FOLCO
> Priority: Major
> Fix For: 3.4.0
>
>
> Mail interface allows people to insert any Serializable object as an
> attribute.
> For now, we then relied on java serialization when putting Mail object into a
> MQ.
> Now that we try to write a new MailQueue on top of RabbitMQ, it makes sense
> to try to avoid this use of Serializable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
