[
https://issues.apache.org/jira/browse/ARTEMIS-4167?focusedWorklogId=849025&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-849025
]
ASF GitHub Bot logged work on ARTEMIS-4167:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Mar/23 18:29
Start Date: 03/Mar/23 18:29
Worklog Time Spent: 10m
Work Description: swerner0 commented on PR #4368:
URL:
https://github.com/apache/activemq-artemis/pull/4368#issuecomment-1453928943
This was my original ask on the mailing list:
https://lists.apache.org/thread/0zktnksnxvnpdqwp1wp2tojw3rtq2wz6
Setting the object is much more convenient but breaks everything else as the
properties are serialized in some form, this would be the first outlier to that.
Agreed on enhancing the docs.
Issue Time Tracking
-------------------
Worklog Id: (was: 849025)
Time Spent: 50m (was: 40m)
> Enhance deserialization filter beyond black/whitelist functionality
> -------------------------------------------------------------------
>
> Key: ARTEMIS-4167
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4167
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Scott Werner
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Now that Artemis is Java 11+ compatible, there is now the ability to set an
> ObjectInputFilter on an ObjectInputStream. There are also built in methods to
> generate filters similar to the current syntax and offers many other features
> out of the box. A global jvm property (jdk.serialFilter) can be set, but this
> is quite restrictive. I suggest adding a new serial filter pattern and class
> name of an ObjectInputFilter implementation, everywhere blacklist/whitelist
> exist today. In time we can look into converting the existing black/whitelist
> to the new format or just deprecating as the semantics are a bit different
> and may not be able to make it 100% compatible.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
