Re: [jira] Commented: (PIVOT-578) create an annotation to check at compile time bxml files

[Sandro Martini <sa...@gmail.com>]

Hi Chris,
thanks for your comments ...

Personally I don't like too much the idea of an Ant task wrapper, because in
my projects usually I use Maven or other products, but I'm not against this
:-) , I only think it's not so general .

So, the idea to have another (mainly related to development environment)
serializer extending the standard BXMLSerializer, and try to handle this
type of warnings directly in it (in the hope to not have to change too much
in the base class, if not little things) ?
Maybe using the standard Java logging facilities (that's not the best, Ok,
but to avoid other dependencies could be enough ...) and depending on the
logging level write more or less warnings ?
But have this data in log is Ok but not enough, because in unit tests I
could also make some assertions on "I'm expecting no errors in the bxml
file", "no warnings", etc ...
Also in this case we'll have this feature only at runtime, but maybe also in
unit tests this feature could be used simply.

Greg (and others), comments ?

Bye,
Sandro

-- 
View this message in context: http://apache-pivot-developers.417237.n3.nabble.com/jira-Created-PIVOT-578-create-an-annotation-to-check-at-compile-time-bxml-files-tp986885p990044.html
Sent from the Apache Pivot - Developers mailing list archive at Nabble.com.

Re: [jira] Commented: (PIVOT-578) create an annotation to check at compile time bxml files

[Greg Brown <gk...@mac.com>]

BXMLSerializer already generates exceptions and warnings, so I'm not sure how much value a subclass would offer. Also, it would be kind of a pain to have to rewrite your application code to take advantage of the "debug version". So I don't think this would be the best approach.

On Jul 23, 2010, at 11:28 AM, Sandro Martini wrote:

> 
> Hi Chris,
> thanks for your comments ...
> 
> Personally I don't like too much the idea of an Ant task wrapper, because in
> my projects usually I use Maven or other products, but I'm not against this
> :-) , I only think it's not so general .
> 
> So, the idea to have another (mainly related to development environment)
> serializer extending the standard BXMLSerializer, and try to handle this
> type of warnings directly in it (in the hope to not have to change too much
> in the base class, if not little things) ?
> Maybe using the standard Java logging facilities (that's not the best, Ok,
> but to avoid other dependencies could be enough ...) and depending on the
> logging level write more or less warnings ?
> But have this data in log is Ok but not enough, because in unit tests I
> could also make some assertions on "I'm expecting no errors in the bxml
> file", "no warnings", etc ...
> Also in this case we'll have this feature only at runtime, but maybe also in
> unit tests this feature could be used simply.
> 
> Greg (and others), comments ?
> 
> Bye,
> Sandro
> 
> -- 
> View this message in context: http://apache-pivot-developers.417237.n3.nabble.com/jira-Created-PIVOT-578-create-an-annotation-to-check-at-compile-time-bxml-files-tp986885p990044.html
> Sent from the Apache Pivot - Developers mailing list archive at Nabble.com.