[
https://issues.jboss.org/browse/WFLY-670?page=com.atlassian.jira.plugin.s...
]
Darryl Miles commented on WFLY-670:
-----------------------------------
Is this behavior by specification? Can you cite the chapter/section (so it is clear to
others what they are doing wrong) ?
If not mandated by specification, please get it put into the specification, or better:
Surely when injecting a primitive or a well-known immutable type, the setter should be
skipped on undeployment, since no memory leak can occur.
What if @NotNull is annotated for the property ? Does it obey validation requirements ?
Even better liaise with the JMX specification and use annotation @PreDestroy for any
actions on undeploy, where no @PreDestroy exists have some default behaviour mandated by
specification, if @PreDestroy exists the container does not call any setter during
undeploy ?
Using "attribute" tag causes injection of null values
-----------------------------------------------------
Key: WFLY-670
URL:
https://issues.jboss.org/browse/WFLY-670
Project: WildFly
Issue Type: Bug
Components: JMX
Reporter: Anders Welen
Assignee: Tomasz Adamski
Priority: Minor
Fix For: Awaiting Volunteers
Using "attribute" tag in "jboss-service.xml" in a SAR archive causes
injection of null values. Even if your code can handle this it makes it impossible to use
primitive datatypes.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)