There is a JIRA that I started on, but had to move off of due to a bug
in the annotation processor,
https://issues.jboss.org/browse/WFLY-230.
Essentially I'm just going to add a @ValidIdRange annotation and give it
the valid range for the subsystem. The bug is now fixed in the
processor, so I can get working on this next week actually.
On 07/03/2013 02:56 AM, Darran Lofthouse wrote:
Hi all,
Recently we have had some issues reported where logging IDs are
suspected to be duplicates.
Can I suggest that one thing we do need is to update the page tracking
the reserved ID's to make it easier to identify what block is available
next?
https://community.jboss.org/wiki/LoggingIds
Would it would be easier if the ranges column was sequential, if a
subsystem takes multiple allocations then it should just appear in the
list more than once. At the moment to find a free block you need to
scan up and down the page to check the subsequent allocations.
Regards,
Darran Lofthouse.
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
James R. Perkins
Red Hat JBoss Middleware