[
https://issues.apache.org/jira/browse/PIVOT-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891629#action_12891629
]
Sandro Martini commented on PIVOT-578:
--------------------------------------
My problem here is mainly to have (but only when desired) something that during
development can help to check that what is written inside bxml files is right,
without waiting at runtime (and have to test it manually) ... it's like many
people prefers to use Spring via annotations (checked by the compiler, for some
things) instead xml files ... but this is another story :-) .
With a visual editor probably the need for this features could become less
important.
I think that this type of features could help newbies to have a faster startup
with Pivot.
I understand that maybe the annotation could not be the best, but I don't think
that a specific build task (ant or maven) could be enough general.
Another option (probably better of previous) instead could be a class to use in
development environment (but only in unit tests), maybe using the
BXMLSerializer or an extension of it (in the no more existing tools subproject
or something like this).
And it could give more log on not-matched properties/styles, etc ...
So the problem in this case could be how to use it instead of the usual
(standard) BXMLSerializer ... via injection or by hand, ok, but how in a simple
way at least for the unit test domain ?
What do you think ?
Bye
> create an annotation to check at compile time bxml files
> --------------------------------------------------------
>
> Key: PIVOT-578
> URL: https://issues.apache.org/jira/browse/PIVOT-578
> Project: Pivot
> Issue Type: New Feature
> Reporter: Sandro Martini
> Assignee: Sandro Martini
> Priority: Minor
>
> In some cases could be useful to have an optional annotation to check (but at
> compile time) bxml files, so when application grows, less tests should be
> done by hand. This could be a great plus.
> For example checks could be more, ranging from existence of the resource
> file, to check for a well-formed structure, to a well-formed contents (if
> possible) ...
> At the moment this is only an experimental (optional) feature.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
