simple-support — General user and support issues

Re: [Simple-support] Is this project still alive?

[Mihael S. <msc...@sg...>]

Perhaps it ain't meant to be for him.

I have been using first CVS then SVN, now Git and Mercurial (and sf.net 
supports all these) and I must say that the source code versioning is 
the least of my worries when developing my side projects.

Niall, you are doing a great job. Great library. Thanx.

Mihael

On 18.12.2013 15:46, Robbie Brown wrote:
> Ok, now, that’s getting a little rude: “But if somebody can’t know
> it….”. Looking at this project, I’m pretty sure he can. I like Git. I
> use Git for all my repositories, but I also appreciate this incredible
> library that Niall Gallagher has written. SimpleXML has saved me an
> unbelievable amount of work. I don’t care if he distributes it in a ZIP
> file. Just keep it open and available. Thanks, Niall.
>
> —Robert Brown
>
>
> From: Tomáš Procházka <tom...@at...
> <mailto:tom...@at...>>
> Date: Wednesday, December 18, 2013 at 6:30 AM
> To: Mihael Schmidt <msc...@sg... <mailto:msc...@sg...>>
> Cc: "sim...@li...
> <mailto:sim...@li...>"
> <sim...@li...
> <mailto:sim...@li...>>
> Subject: Re: [Simple-support] Is this project still alive?
>
> Many project live only from contribution, like
> https://github.com/jayway/maven-android-plugin. And I think that it is
> not top 10 project. Or our small project
> https://github.com/inmite/android-styled-dialogs have 5 merged pull
> requests already.
>
> And GIT/Hq is also many times better than SVN.
>
> But if somebody can't know it....
>
> --
> Ing. Tomáš Procházka
>
>
> 2013/12/18 Mihael Schmidt <msc...@sg... <mailto:msc...@sg...>>
>
>     github may have this nice feature but it offers almost nothing else and
>     you are also tied to git.
>
>     and who does a fork and contributes back to the project? i would say
>     that if your project is not one of the top ten projects than it wouldn't
>     get even one fork/contribution in a year.
>
>     sf.net <http://sf.net> may not provide your favored development
>     workflow but it is one
>     of the top sites for open source projects and has many options for all
>     types of projects and development styles.
>
>     my 2 cents
>
>     mihael
>
>
>     On 18.12.2013 00:42, Tomáš Procházka wrote:
>     >  Main problem of sourceForge is absence of fork/pull mechanism.
>     >  Everyone can by one click make fork, fix any bug and pull changes back
>     >  to you by Pull Request, which you can check and accept by one click.
>     >  It's extremely easy and all forks are still at the one place.
>     >  Now If someone decide to fix some problem is extremely complicated to
>     >  send you some patch back.
>     >
>     >  And this is not one benefit
>     >  GIT has also integrated bugtracker with GIT and with Integration
>     server.
>     >  When someone send you pull request with some change it will be
>     >  automatically run build on CI server and result will be write to the
>     >  comment in the bugtracker, you intermediately know, if changes broken
>     >  any tests.
>     >
>     >  And some other great function like code review, etc.
>     >  SourceForge is now only for historical and already dead projects.
>     >
>     >  --
>     >  Ing. Tomáš Procházka
>     >
>     >
>     >  2013/12/17 Niall Gallagher - Yieldbroker
>     >  <Nia...@yi...
>     <mailto:Nia...@yi...>
>     <mailto:Nia...@yi...
>     <mailto:Nia...@yi...>>>
>     >
>     >  Hi,____
>     >
>     >  __ __
>     >
>     >  Yes it is still alive. I am happy with sourceforge right now and
>     >  have no intention of moving at the moment.____
>     >
>     >  __ __
>     >
>     >  Thanks,____
>     >
>     >  Niall____
>     >
>     >  __ __
>     >
>     >  *From:*Tomáš Procházka [mailto:tom...@at...
>     <mailto:tom...@at...>
>     >  <mailto:tom...@at...
>     <mailto:tom...@at...>>]
>     >  *Sent:* 18 December 2013 06:11
>     >  *To:* sim...@li...
>     <mailto:sim...@li...>
>     >  <mailto:sim...@li...
>     <mailto:sim...@li...>>
>     >  *Subject:* [Simple-support] Is this project still alive?____
>     >
>     >  __ __
>     >
>     >  Is this project still alive?____
>     >
>     >  What about migrate project to some modern project hosting like
>     >  github.com <http://github.com> <http://github.com>?____
>     >
>     >  It is much more usable for development :-(____
>     >
>     >
>     >  ____
>     >
>     >  --
>     >  Tomáš Procházka____
>     >
>     >
>     >
>     >
>     >
>     ------------------------------------------------------------------------------
>     >  Rapidly troubleshoot problems before they affect your business.
>     Most IT
>     >  organizations don't have a clear picture of how application
>     performance
>     >  affects their revenue. With AppDynamics, you get 100% visibility
>     into your
>     >  Java,.NET,& PHP application. Start your 15-day FREE TRIAL of
>     AppDynamics Pro!
>     >
>     http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
>     <http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk>
>     >
>     >
>     >
>     >  _______________________________________________
>     >  Simple-support mailing list
>     >  Sim...@li...
>     <mailto:Sim...@li...>
>     >  https://lists.sourceforge.net/lists/listinfo/simple-support
>
>     --
>
>     Schulz Gebäudeservice GmbH & Co. KG
>     Dr.-Max-Ilgner-Straße 17
>     32339 Espelkamp
>     Persönlich haftende Gesellschafterin:
>     Gebäudereinigung Joachim Schulz
>     Verwaltungsgesellschaft mbH
>     Telefon: +49 5772 9100 0 <tel:%2B49%205772%209100%200>
>     Telefax: +49 5772 9100 11 <tel:%2B49%205772%209100%2011>
>     Email: zen...@sg... <mailto:zen...@sg...>
>     Internet: www.sgbs.de <http://www.sgbs.de>
>     Geschäftsführer: Joachim und Dirk Schulz, Norbert Kosica
>     Handelsregister Bad Oeynhausen: HRA 5902, HRB 8591
>     UST-Id-Nr.: DE 125752702
>
>     ------------------------------------------------------------------------------
>     Rapidly troubleshoot problems before they affect your business. Most IT
>     organizations don't have a clear picture of how application performance
>     affects their revenue. With AppDynamics, you get 100% visibility
>     into your
>     Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
>     AppDynamics Pro!
>     http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
>     <http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk>
>     _______________________________________________
>     Simple-support mailing list
>     Sim...@li...
>     <mailto:Sim...@li...>
>     https://lists.sourceforge.net/lists/listinfo/simple-support
>
>

-- 

Schulz Gebäudeservice GmbH & Co. KG
Dr.-Max-Ilgner-Straße 17
32339 Espelkamp
Persönlich haftende Gesellschafterin:
Gebäudereinigung Joachim Schulz
Verwaltungsgesellschaft mbH
Telefon: +49 5772 9100 0
Telefax: +49 5772 9100 11
Email: zen...@sg...
Internet: www.sgbs.de
Geschäftsführer: Joachim und Dirk Schulz, Norbert Kosica
Handelsregister Bad Oeynhausen: HRA 5902, HRB 8591
UST-Id-Nr.: DE 125752702

Re: [Simple-support] Is this project still alive?

[Tomáš P. <tom...@at...>]

Many project live only from contribution, like
https://github.com/jayway/maven-android-plugin. And I think that it is not
top 10 project. Or our small project
https://github.com/inmite/android-styled-dialogs have 5 merged pull
requests already.

And GIT/Hq is also many times better than SVN.

But if somebody can't know it....

-- 
Ing. Tomáš Procházka


2013/12/18 Mihael Schmidt <msc...@sg...>

> github may have this nice feature but it offers almost nothing else and
> you are also tied to git.
>
> and who does a fork and contributes back to the project? i would say
> that if your project is not one of the top ten projects than it wouldn't
> get even one fork/contribution in a year.
>
> sf.net may not provide your favored development workflow but it is one
> of the top sites for open source projects and has many options for all
> types of projects and development styles.
>
> my 2 cents
>
> mihael
>
>
> On 18.12.2013 00:42, Tomáš Procházka wrote:
> > Main problem of sourceForge is absence of fork/pull mechanism.
> > Everyone can by one click make fork, fix any bug and pull changes back
> > to you by Pull Request, which you can check and accept by one click.
> > It's extremely easy and all forks are still at the one place.
> > Now If someone decide to fix some problem is extremely complicated to
> > send you some patch back.
> >
> > And this is not one benefit
> > GIT has also integrated bugtracker with GIT and with Integration server.
> > When someone send you pull request with some change it will be
> > automatically run build on CI server and result will be write to the
> > comment in the bugtracker, you intermediately know, if changes broken
> > any tests.
> >
> > And some other great function like code review, etc.
> > SourceForge is now only for historical and already dead projects.
> >
> > --
> > Ing. Tomáš Procházka
> >
> >
> > 2013/12/17 Niall Gallagher - Yieldbroker
> > <Nia...@yi... <mailto:Nia...@yi...
> >>
> >
> >     Hi,____
> >
> >     __ __
> >
> >     Yes it is still alive. I am happy with sourceforge right now and
> >     have no intention of moving at the moment.____
> >
> >     __ __
> >
> >     Thanks,____
> >
> >     Niall____
> >
> >     __ __
> >
> >     *From:*Tomáš Procházka [mailto:tom...@at...
> >     <mailto:tom...@at...>]
> >     *Sent:* 18 December 2013 06:11
> >     *To:* sim...@li...
> >     <mailto:sim...@li...>
> >     *Subject:* [Simple-support] Is this project still alive?____
> >
> >     __ __
> >
> >     Is this project still alive?____
> >
> >     What about migrate project to some modern project hosting like
> >     github.com <http://github.com>?____
> >
> >     It is much more usable for development :-(____
> >
> >
> >     ____
> >
> >     --
> >     Tomáš Procházka____
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Rapidly troubleshoot problems before they affect your business. Most IT
> > organizations don't have a clear picture of how application performance
> > affects their revenue. With AppDynamics, you get 100% visibility into
> your
> > Java,.NET,&  PHP application. Start your 15-day FREE TRIAL of
> AppDynamics Pro!
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> >
> >
> >
> > _______________________________________________
> > Simple-support mailing list
> > Sim...@li...
> > https://lists.sourceforge.net/lists/listinfo/simple-support
>
> --
>
> Schulz Gebäudeservice GmbH & Co. KG
> Dr.-Max-Ilgner-Straße 17
> 32339 Espelkamp
> Persönlich haftende Gesellschafterin:
> Gebäudereinigung Joachim Schulz
> Verwaltungsgesellschaft mbH
> Telefon: +49 5772 9100 0
> Telefax: +49 5772 9100 11
> Email: zen...@sg...
> Internet: www.sgbs.de
> Geschäftsführer: Joachim und Dirk Schulz, Norbert Kosica
> Handelsregister Bad Oeynhausen: HRA 5902, HRB 8591
> UST-Id-Nr.: DE 125752702
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Simple-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simple-support
>

Re: [Simple-support] Is this project still alive?

[Timo R. <tim...@di...>]

Hi all,

and my 2 other cents:

Migrating everything is a huge load of work. I for one would rather see
Niall continuing to support us at this mailing list and working on the
Simple framework instead of putting his time into the migration.

Github is nice, but not just for every project on this planet (beware:
hype-meter on! ;) ).


Best Regards,
Timo


-----Ursprüngliche Nachricht-----
Von: Mihael Schmidt [mailto:msc...@sg...] 
Gesendet: Mittwoch, 18. Dezember 2013 08:51
An: sim...@li...
Betreff: Re: [Simple-support] Is this project still alive?

github may have this nice feature but it offers almost nothing else and you
are also tied to git.

and who does a fork and contributes back to the project? i would say that if
your project is not one of the top ten projects than it wouldn't get even
one fork/contribution in a year.

sf.net may not provide your favored development workflow but it is one of
the top sites for open source projects and has many options for all types of
projects and development styles.

my 2 cents

mihael


On 18.12.2013 00:42, Tomáš Procházka wrote:
> Main problem of sourceForge is absence of fork/pull mechanism.
> Everyone can by one click make fork, fix any bug and pull changes back 
> to you by Pull Request, which you can check and accept by one click.
> It's extremely easy and all forks are still at the one place.
> Now If someone decide to fix some problem is extremely complicated to 
> send you some patch back.
>
> And this is not one benefit
> GIT has also integrated bugtracker with GIT and with Integration server.
> When someone send you pull request with some change it will be 
> automatically run build on CI server and result will be write to the 
> comment in the bugtracker, you intermediately know, if changes broken 
> any tests.
>
> And some other great function like code review, etc.
> SourceForge is now only for historical and already dead projects.
>
> --
> Ing. Tomáš Procházka
>
>
> 2013/12/17 Niall Gallagher - Yieldbroker 
> <Nia...@yi... 
> <mailto:Nia...@yi...>>
>
>     Hi,____
>
>     __ __
>
>     Yes it is still alive. I am happy with sourceforge right now and
>     have no intention of moving at the moment.____
>
>     __ __
>
>     Thanks,____
>
>     Niall____
>
>     __ __
>
>     *From:*Tomáš Procházka [mailto:tom...@at...
>     <mailto:tom...@at...>]
>     *Sent:* 18 December 2013 06:11
>     *To:* sim...@li...
>     <mailto:sim...@li...>
>     *Subject:* [Simple-support] Is this project still alive?____
>
>     __ __
>
>     Is this project still alive?____
>
>     What about migrate project to some modern project hosting like
>     github.com <http://github.com>?____
>
>     It is much more usable for development :-(____
>
>
>     ____
>
>     --
>     Tomáš Procházka____
>
>
>
>
> ----------------------------------------------------------------------
> -------- Rapidly troubleshoot problems before they affect your 
> business. Most IT organizations don't have a clear picture of how 
> application performance affects their revenue. With AppDynamics, you 
> get 100% visibility into your Java,.NET,&  PHP application. Start your 
> 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.c
> lktrk
>
>
>
> _______________________________________________
> Simple-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simple-support

-- 

Schulz Gebäudeservice GmbH & Co. KG
Dr.-Max-Ilgner-Straße 17
32339 Espelkamp
Persönlich haftende Gesellschafterin:
Gebäudereinigung Joachim Schulz
Verwaltungsgesellschaft mbH
Telefon: +49 5772 9100 0
Telefax: +49 5772 9100 11
Email: zen...@sg...
Internet: www.sgbs.de
Geschäftsführer: Joachim und Dirk Schulz, Norbert Kosica Handelsregister Bad
Oeynhausen: HRA 5902, HRB 8591
UST-Id-Nr.: DE 125752702

----------------------------------------------------------------------------
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

Re: [Simple-support] Is this project still alive?

[Mihael S. <msc...@sg...>]

github may have this nice feature but it offers almost nothing else and 
you are also tied to git.

and who does a fork and contributes back to the project? i would say 
that if your project is not one of the top ten projects than it wouldn't 
get even one fork/contribution in a year.

sf.net may not provide your favored development workflow but it is one 
of the top sites for open source projects and has many options for all 
types of projects and development styles.

my 2 cents

mihael


On 18.12.2013 00:42, Tomáš Procházka wrote:
> Main problem of sourceForge is absence of fork/pull mechanism.
> Everyone can by one click make fork, fix any bug and pull changes back
> to you by Pull Request, which you can check and accept by one click.
> It's extremely easy and all forks are still at the one place.
> Now If someone decide to fix some problem is extremely complicated to
> send you some patch back.
>
> And this is not one benefit
> GIT has also integrated bugtracker with GIT and with Integration server.
> When someone send you pull request with some change it will be
> automatically run build on CI server and result will be write to the
> comment in the bugtracker, you intermediately know, if changes broken
> any tests.
>
> And some other great function like code review, etc.
> SourceForge is now only for historical and already dead projects.
>
> --
> Ing. Tomáš Procházka
>
>
> 2013/12/17 Niall Gallagher - Yieldbroker
> <Nia...@yi... <mailto:Nia...@yi...>>
>
>     Hi,____
>
>     __ __
>
>     Yes it is still alive. I am happy with sourceforge right now and
>     have no intention of moving at the moment.____
>
>     __ __
>
>     Thanks,____
>
>     Niall____
>
>     __ __
>
>     *From:*Tomáš Procházka [mailto:tom...@at...
>     <mailto:tom...@at...>]
>     *Sent:* 18 December 2013 06:11
>     *To:* sim...@li...
>     <mailto:sim...@li...>
>     *Subject:* [Simple-support] Is this project still alive?____
>
>     __ __
>
>     Is this project still alive?____
>
>     What about migrate project to some modern project hosting like
>     github.com <http://github.com>?____
>
>     It is much more usable for development :-(____
>
>
>     ____
>
>     --
>     Tomáš Procházka____
>
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET,&  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Simple-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simple-support

-- 

Schulz Gebäudeservice GmbH & Co. KG
Dr.-Max-Ilgner-Straße 17
32339 Espelkamp
Persönlich haftende Gesellschafterin:
Gebäudereinigung Joachim Schulz
Verwaltungsgesellschaft mbH
Telefon: +49 5772 9100 0
Telefax: +49 5772 9100 11
Email: zen...@sg...
Internet: www.sgbs.de
Geschäftsführer: Joachim und Dirk Schulz, Norbert Kosica
Handelsregister Bad Oeynhausen: HRA 5902, HRB 8591
UST-Id-Nr.: DE 125752702

Re: [Simple-support] Is this project still alive?

[Niall G. - Y. <Nia...@yi...>]

Perhaps when I get an opportunity I will take a look at it, sourceforge.net offers some things that github just did not have last time I checked. Like hosting my own project website under my own specific domain name. Maybe this has changed if so then I might consider moving it.

From: Tomáš Procházka [mailto:tom...@at...]
Sent: 18 December 2013 10:42
To: Niall Gallagher - Yieldbroker
Cc: sim...@li...
Subject: Re: [Simple-support] Is this project still alive?

Main problem of sourceForge is absence of fork/pull mechanism.
Everyone can by one click make fork, fix any bug and pull changes back to you by Pull Request, which you can check and accept by one click.
It's extremely easy and all forks are still at the one place.
Now If someone decide to fix some problem is extremely complicated to send you some patch back.

And this is not one benefit
GIT has also integrated bugtracker with GIT and with Integration server.
When someone send you pull request with some change it will be automatically run build on CI server and result will be write to the comment in the bugtracker, you intermediately know, if changes broken any tests.

And some other great function like code review, etc.
SourceForge is now only for historical and already dead projects.

--
Ing. Tomáš Procházka

2013/12/17 Niall Gallagher - Yieldbroker <Nia...@yi...<mailto:Nia...@yi...>>
Hi,

Yes it is still alive. I am happy with sourceforge right now and have no intention of moving at the moment.

Thanks,
Niall

From: Tomáš Procházka [mailto:tom...@at...<mailto:tom...@at...>]
Sent: 18 December 2013 06:11
To: sim...@li...<mailto:sim...@li...>
Subject: [Simple-support] Is this project still alive?

Is this project still alive?
What about migrate project to some modern project hosting like github.com<http://github.com>?
It is much more usable for development :-(

--
Tomáš Procházka

Re: [Simple-support] Is this project still alive?

[Tomáš P. <tom...@at...>]

Main problem of sourceForge is absence of fork/pull mechanism.
Everyone can by one click make fork, fix any bug and pull changes back to
you by Pull Request, which you can check and accept by one click.
It's extremely easy and all forks are still at the one place.
Now If someone decide to fix some problem is extremely complicated to send
you some patch back.

And this is not one benefit
GIT has also integrated bugtracker with GIT and with Integration server.
When someone send you pull request with some change it will be
automatically run build on CI server and result will be write to the
comment in the bugtracker, you intermediately know, if changes broken any
tests.

And some other great function like code review, etc.
SourceForge is now only for historical and already dead projects.

-- 
Ing. Tomáš Procházka


2013/12/17 Niall Gallagher - Yieldbroker <Nia...@yi...>

>  Hi,
>
>
>
> Yes it is still alive. I am happy with sourceforge right now and have no
> intention of moving at the moment.
>
>
>
> Thanks,
>
> Niall
>
>
>
> *From:* Tomáš Procházka [mailto:tom...@at...]
> *Sent:* 18 December 2013 06:11
> *To:* sim...@li...
> *Subject:* [Simple-support] Is this project still alive?
>
>
>
> Is this project still alive?
>
> What about migrate project to some modern project hosting like github.com?
>
> It is much more usable for development :-(
>
>
>  --
> Tomáš Procházka
>

Re: [Simple-support] Is this project still alive?

[Niall G. - Y. <Nia...@yi...>]

Hi,

Yes it is still alive. I am happy with sourceforge right now and have no intention of moving at the moment.

Thanks,
Niall

From: Tomáš Procházka [mailto:tom...@at...]
Sent: 18 December 2013 06:11
To: sim...@li...
Subject: [Simple-support] Is this project still alive?

Is this project still alive?
What about migrate project to some modern project hosting like github.com<http://github.com>?
It is much more usable for development :-(

--
Tomáš Procházka

[Simple-support] Is this project still alive?

[Tomáš P. <tom...@at...>]

Is this project still alive?
What about migrate project to some modern project hosting like github.com?
It is much more usable for development :-(

-- 
Tomáš Procházka

[Simple-support] XML attribute empty value

[Tomáš P. <tom...@at...>]

I have this in my POJO

 @Attribute(required = false, empty = "")
 protected Date birthDate;

I want to generate birthDate="" to the XML if date is null, but it doesn't
work.

But this:

 @Attribute(required = false, empty = "empty")
 protected Date birthDate;

will be generate birthDate="empty"

I think that "" should be also possible to use as empty value
Why not?
I checked that you use "" as default value , maybe will be better use some
other value and allou to use "" as custom variant.

I think that default value mean hide the attribute.




-- 
Ing. Tomáš Procházka

Re: [Simple-support] Support for EXI encoding? (Efficient XML Interchange)?

[Niall G. <gal...@ya...>]

Hi,

I have never tried it with Simple, however it seems like yet another bad idea. XML is not a silver bullet that should be used for absolutely all scenarios. If you need a concise and highly performant format that does not require the various benefits of XML then I would say don't use XML. 

I have not used Protocol Buffers or other such libraries as Thrift much, however I have heard they are reasonable. 

Niall





On Wednesday, 30 October 2013 2:10 AM, Niall Gallagher <ni...@np...> wrote:
 
Hi,

Has anyone tried Simple with EXI (Efficient XML Interchange)? 

EXI is a W3C standard for encoding XML documents in a binary format instead of plaintext. It integrates into standard XML stacks and provides the same APIs to applications (SAX, StAX 
etc).  As part of the standardization process, the W3C ran benchmarks on EXI in 2009 here, their findings were compelling. It was standardized in 2011, and there are now a few open source libraries to parse/write it via standard XML interfaces. 

In our internal tests, we also found EXI compelling - it blew JSON out of the water in compactness 
and CPU efficiency, and was competitive with Google Protocol Buffers 
(in compactness, but not efficiency). We are interested in serving EXI instead of plaintext XML to Android handsets where it might be more battery-friendly and reduce bandwidth requirements.

Just putting the feelers out at this stage - has anyone tried this with Simple? Any gotchas?

Many thanks,
Niall

------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

[Simple-support] Support for EXI encoding? (Efficient XML Interchange)?

[Niall G. <ni...@np...>]

Hi,

Has anyone tried Simple with EXI (Efficient XML Interchange)?

EXI is a W3C standard<http://en.wikipedia.org/wiki/Efficient_XML_Interchange>for
encoding XML documents in a binary format instead of plaintext. It
integrates into standard XML stacks and provides the same APIs to
applications (SAX, StAX etc).  As part of the standardization process, the
W3C ran benchmarks on EXI in 2009 here<http://www.w3.org/TR/exi-evaluation/>,
their findings were compelling. It was standardized in 2011, and there are
now a few open source libraries to parse/write it via standard XML
interfaces.

In our internal tests, we also found EXI compelling - it blew JSON out of
the water in compactness and CPU efficiency, and was competitive with
Google Protocol Buffers (in compactness, but not efficiency). We are
interested in serving EXI instead of plaintext XML to Android handsets
where it might be more battery-friendly and reduce bandwidth requirements.

Just putting the feelers out at this stage - has anyone tried this with
Simple? Any gotchas?

Many thanks,
Niall

[Simple-support] Fwd: Support for EXI encoding? (Efficient XML Interchange)?

[Niall G. <ni...@np...>]

BTW coincidentally my name is also Niall Gallagher :)
But I'm not the Niall Gallagher author of Simple, I'm a different Niall
Gallagher!
But I have questions about Simple. This could be confusing!

---------- Forwarded message ----------
From: Niall Gallagher <ni...@np...>
Date: 29 October 2013 14:39
Subject: Support for EXI encoding? (Efficient XML Interchange)?
To: sim...@li...


Hi,

Has anyone tried Simple with EXI (Efficient XML Interchange)?

EXI is a W3C standard<http://en.wikipedia.org/wiki/Efficient_XML_Interchange>for
encoding XML documents in a binary format instead of plaintext. It
integrates into standard XML stacks and provides the same APIs to
applications (SAX, StAX etc).  As part of the standardization process, the
W3C ran benchmarks on EXI in 2009 here<http://www.w3.org/TR/exi-evaluation/>,
their findings were compelling. It was standardized in 2011, and there are
now a few open source libraries to parse/write it via standard XML
interfaces.

In our internal tests, we also found EXI compelling - it blew JSON out of
the water in compactness and CPU efficiency, and was competitive with
Google Protocol Buffers (in compactness, but not efficiency). We are
interested in serving EXI instead of plaintext XML to Android handsets
where it might be more battery-friendly and reduce bandwidth requirements.

Just putting the feelers out at this stage - has anyone tried this with
Simple? Any gotchas?

Many thanks,
Niall

Re: [Simple-support] Howto deserialize XML Tree

[Niall G. - Y. <Nia...@yi...>]

Can you provide the annotated class?

________________________________
From: Ola...@Em... [Ola...@Em...]
Sent: 29 October 2013 00:59
To: sim...@li...
Subject: [Simple-support] Howto deserialize XML Tree

Hey,

I have an XML-File with a structure that looks in principal like this and I have no idea how to annote my code.
I always getting : Element '…' is already used with @org.simpleframework.xml.ElementList

The structure looks like this (simplified):

<Tree>
  <abc> </abc>
  <xyz> </xyz>

  <Tree>
   <abc> </abc>
   <xyz> </xyz>
 </Tree>
  <Tree>
   <abc> </abc>
   <xyz> </xyz>
   <Tree>
   </Tree>
  </Tree>
</Tree>


Who can help ?

[Simple-support] Howto deserialize XML Tree

[<Ola...@Em...>]

Hey,

I have an XML-File with a structure that looks in principal like this and I have no idea how to annote my code.
I always getting : Element '...' is already used with @org.simpleframework.xml.ElementList

The structure looks like this (simplified):

<Tree>
  <abc> </abc>
  <xyz> </xyz>

  <Tree>
   <abc> </abc>
   <xyz> </xyz>
 </Tree>
  <Tree>
   <abc> </abc>
   <xyz> </xyz>
   <Tree>
   </Tree>
  </Tree>
</Tree>


Who can help ?

[Simple-support] Simple External Entity injection

[Adam Z. <ad...@ma...>]

Hello,

I'm using Simple framework in the implementation of client application
to our NDS2(http://blog.psnc.pl/tnc2013/en/nds2/) service. Our security
department conducted penetration tests of the application and they found
a security bug related to how XML external entities are proceeding in
Simple. This is so called XXE:
https://www.owasp.org/index.php/XML_External_Entity_%28XXE%29_Processing
The usual fix in such a case is to turn EE parsing off within the
parser. Unfortunately I can not find any option in Simple to do that.
Could you please help me with this issue?

If Simple does not provide such an option it should be considered as a security flaw in Simple itself.

Kind regards,
Adam Zawada

-- 
Adam Zawada
Poznan Supercomputing and Networking Center
Supercomputing Department

http://rose.man.poznan.pl/~adam/
phone (+48 61) 858 21 93

Re: [Simple-support] Duplicate element error parsing rss and atom

[Niall G. - Y. <Nia...@yi...>]

I think you should easily be able to try this yourself, however a Converter can also deserialize as well as serialize. I may consider adding something that would pair an @Namespace with an @Element to extract a prefixed/qualified element.

-----Original Message-----
From: terry turner [mailto:tn...@na...] 
Sent: Thursday, 29 August 2013 9:19 AM
To: Niall Gallagher
Cc: sim...@li...
Subject: Re: [Simple-support] Duplicate element error parsing rss and atom

the converter looks like it can only be used for serialization. my problem is deserialization.

although that is how the xml spec is defined the problem for a xml-object mapping library is that we need a way to map these elements to different fields in the object based on the namespace they are part of.

with most xml i've worked with the parties communicating work closely together and these sorts of namespace issues can be avoided. in the case of rss it is a free for all. the people producing the xml do on a 'take it or leave it' basis and those parsing are left to figure out how to do it.

my choice is to preprocess the xml or charge the library so that it'll handle these collisions. if you think a novice (to the library) could modify the library source to handle this i'm happy to give it a try.

thanks,
terry

On 08/28/2013 01:17 AM, Niall Gallagher wrote:
> One thing to note, is that namespaces do not form part of the document 
> structure according to the XML specification so <x:link> <y:link> 
> <z:link> are all just <link> the namespace only qualifies it. Use an 
> @ElementList with inline=true and it will pick up both links, you can 
> then use the one that you want. Alternatively you can parse it 
> yourself with a Converter.
>
> ----------------------------------------------------------------------
> --
> *From:* terry turner <tn...@na...>
> *To:* sim...@li...
> *Sent:* Wednesday, 28 August 2013 5:47 PM
> *Subject:* [Simple-support] Duplicate element error parsing rss and 
> atom
>
> this is a well designed api but i'm having what seems to be a common 
> problem deserializing xml that contains elements with the same name 
> but in different name spaces. the usual example is
>
> <rss >
>    <channel>
> ...
>      <link>some value</link>
> ...
>      <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom"
>      rel="self"
>      type="application/rss+xml"
>      href="http://feeds.feedburner.com/..."/>
>
> the 'link' in <atom:link> collides with <link>
>
> first question: is there any way to parse this with the current 
> version of simpleXml?
>
> as no one that has asked this question has received an answer i'm 
> assuming there is no way to do it now. that leads to my second question:
> how hard is this to support? is it something that an above average 
> java developer (that's me) could get done relatively quickly?
>
> or is it a big design change to support these name space name collisions?
>
> thanks,
> terry
>
> ----------------------------------------------------------------------
> -------- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 
> 2012, more!
> Discover the easy way to master current and previous Microsoft 
> technologies and advance your career. Get an incredible 1,500+ hours 
> of step-by-step tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.c
> lktrk _______________________________________________
> Simple-support mailing list
> Sim...@li...
> <mailto:Sim...@li...>
> https://lists.sourceforge.net/lists/listinfo/simple-support
>
>

------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

Re: [Simple-support] Duplicate element error parsing rss and atom

[terry t. <tn...@na...>]

the converter looks like it can only be used for serialization. my 
problem is deserialization.

although that is how the xml spec is defined the problem for a 
xml-object mapping library is that we need a way to map these elements 
to different fields in the object based on the namespace they are part of.

with most xml i've worked with the parties communicating work closely 
together and these sorts of namespace issues can be avoided. in the case 
of rss it is a free for all. the people producing the xml do on a 'take 
it or leave it' basis and those parsing are left to figure out how to do it.

my choice is to preprocess the xml or charge the library so that it'll 
handle these collisions. if you think a novice (to the library) could 
modify the library source to handle this i'm happy to give it a try.

thanks,
terry

On 08/28/2013 01:17 AM, Niall Gallagher wrote:
> One thing to note, is that namespaces do not form part of the document
> structure according to the XML specification so <x:link> <y:link>
> <z:link> are all just <link> the namespace only qualifies it. Use an
> @ElementList with inline=true and it will pick up both links, you can
> then use the one that you want. Alternatively you can parse it yourself
> with a Converter.
>
> ------------------------------------------------------------------------
> *From:* terry turner <tn...@na...>
> *To:* sim...@li...
> *Sent:* Wednesday, 28 August 2013 5:47 PM
> *Subject:* [Simple-support] Duplicate element error parsing rss and atom
>
> this is a well designed api but i'm having what seems to be a common
> problem deserializing xml that contains elements with the same name but
> in different name spaces. the usual example is
>
> <rss >
>    <channel>
> ...
>      <link>some value</link>
> ...
>      <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom"
>      rel="self"
>      type="application/rss+xml"
>      href="http://feeds.feedburner.com/..."/>
>
> the 'link' in <atom:link> collides with <link>
>
> first question: is there any way to parse this with the current version
> of simpleXml?
>
> as no one that has asked this question has received an answer i'm
> assuming there is no way to do it now. that leads to my second question:
> how hard is this to support? is it something that an above average java
> developer (that's me) could get done relatively quickly?
>
> or is it a big design change to support these name space name collisions?
>
> thanks,
> terry
>
> ------------------------------------------------------------------------------
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Discover the easy way to master current and previous Microsoft technologies
> and advance your career. Get an incredible 1,500+ hours of step-by-step
> tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
> _______________________________________________
> Simple-support mailing list
> Sim...@li...
> <mailto:Sim...@li...>
> https://lists.sourceforge.net/lists/listinfo/simple-support
>
>

Re: [Simple-support] Duplicate element error parsing rss and atom

[Niall G. <gal...@ya...>]

One thing to note, is that namespaces do not form part of the document structure according to the XML specification so <x:link> <y:link> <z:link> are all just <link> the namespace only qualifies it. Use an @ElementList with inline=true and it will pick up both links, you can then use the one that you want. Alternatively you can parse it yourself with a Converter.


________________________________
 From: terry turner <tn...@na...>
To: sim...@li... 
Sent: Wednesday, 28 August 2013 5:47 PM
Subject: [Simple-support] Duplicate element error parsing rss and atom
 

this is a well designed api but i'm having what seems to be a common 
problem deserializing xml that contains elements with the same name but 
in different name spaces. the usual example is

<rss >
   <channel>
...
     <link>some value</link>
...
     <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom"
    rel="self"
    type="application/rss+xml"
    href="http://feeds.feedburner.com/..."/>

the 'link' in <atom:link> collides with <link>

first question: is there any way to parse this with the current version 
of simpleXml?

as no one that has asked this question has received an answer i'm 
assuming there is no way to do it now. that leads to my second question: 
how hard is this to support? is it something that an above average java 
developer (that's me) could get done relatively quickly?

or is it a big design change to support these name space name collisions?

thanks,
terry

------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

[Simple-support] Duplicate element error parsing rss and atom

[terry t. <tn...@na...>]

this is a well designed api but i'm having what seems to be a common 
problem deserializing xml that contains elements with the same name but 
in different name spaces. the usual example is

<rss >
   <channel>
...
     <link>some value</link>
...
     <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom"
	rel="self"
	type="application/rss+xml"
	href="http://feeds.feedburner.com/..."/>

the 'link' in <atom:link> collides with <link>

first question: is there any way to parse this with the current version 
of simpleXml?

as no one that has asked this question has received an answer i'm 
assuming there is no way to do it now. that leads to my second question: 
how hard is this to support? is it something that an above average java 
developer (that's me) could get done relatively quickly?

or is it a big design change to support these name space name collisions?

thanks,
terry

[Simple-support] Query regarding use of Namespace in Simple XML 2.7

[Harish R. <har...@gm...>]

Dear Sir/ Madam,

I am trying to create an XML as below using Java and Simple 2.7 Jar,

<TestXML xmlns:xs="urn:loc.gov:books" xs:"XYZ.xsd">
   <ABC>1.0</ABC>
</TestXML>

The Java code with Namespace for the same is as below,

@Root
@NamespaceList({
@Namespace(reference="urn:loc.gov:books", prefix="xs"),
@Namespace(reference="XYZ.xsd", prefix = "xs")
})
public class TestXML {
....
}

But, with the above Java class, the XML gets printed as below,
<TestXML xmlns:xs="urn:loc.gov:books" xmlns:xs="XYZ.xsd">
   <ABC>1.0</ABC>
</TestXML>

I do not require the "xmlns" and "=" appended to the second namespace. Can
you please let me know as to what I am missing in the Java code.

Thanks in advance.

Warm Regards,
Harish

Re: [Simple-support] Converter not being called for Attributes (2.7)

[Niall G. - Y. <Nia...@yi...>]

Attributes use org.simpleframework.xml.transform.Transform and org.simpleframework.xml.transform.Matcher..

From: Farago, Tamas [mailto:tam...@cr...]
Sent: Monday, 1 July 2013 5:45 PM
To: sim...@li...
Subject: [Simple-support] Converter not being called for Attributes (2.7)

Hi,

Using Simpl 2.7 I have added several converters through the RegistryStrategy to convert enum values from their XML value to the value we are using in the project. However the converter is not being called for attributes.

For example:

@Root(name = "TEST")
public class TestView {
    @Element public MyEnumType enum1;
    @Element public OtherTestView subclass;
    @Attribute public MyEnumType enum3;
}

public class OtherTestView {
    @Attribute public MyEnumType enum2;
}

public enum MyEnumType {
    Continuous("CONTINUOUS");
    public final String val;
    MyEnumType(String val) {this.val = val;}
}

My converter simply loops over all the enum values and returns the one that matches 'val'.
The generated XML is as follows; you can see it correctly works for enum1, which is the converted value, but not for the other two @Attribute annotated values. The same goes for deserializing, it simply fails because it cannot find the value.

<TEST enum3="Continuous">
   <enum1>CONTINUOUS</enum1>
   <subclass enum2="Continuous"/>
</TEST>

Am I missing something, or is this simply not supported? I can get conversion to work by implementing the Transform class for MyEnumType, but I find it very strange I have to go through that route.

Cheers,
Tomi


==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================

[Simple-support] Converter not being called for Attributes (2.7)

[Farago, T. <tam...@cr...>]

Hi,

 

Using Simpl 2.7 I have added several converters through the
RegistryStrategy to convert enum values from their XML value to the
value we are using in the project. However the converter is not being
called for attributes.

 

For example:

 

@Root(name = "TEST")

public class TestView {

    @Element public MyEnumType enum1;

    @Element public OtherTestView subclass;

    @Attribute public MyEnumType enum3;

}

 

public class OtherTestView {

    @Attribute public MyEnumType enum2;

}

 

public enum MyEnumType {

    Continuous("CONTINUOUS");

    public final String val;

    MyEnumType(String val) {this.val = val;}

}

 

My converter simply loops over all the enum values and returns the one
that matches 'val'.

The generated XML is as follows; you can see it correctly works for
enum1, which is the converted value, but not for the other two
@Attribute annotated values. The same goes for deserializing, it simply
fails because it cannot find the value.

 

<TEST enum3="Continuous">

   <enum1>CONTINUOUS</enum1>

   <subclass enum2="Continuous"/>

</TEST>

 

Am I missing something, or is this simply not supported? I can get
conversion to work by implementing the Transform class for MyEnumType,
but I find it very strange I have to go through that route. 

 

Cheers,

Tomi


=============================================================================== 
Please access the attached hyperlink for an important electronic communications disclaimer: 
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html 
=============================================================================== 

Re: [Simple-support] Unmodifiable ElementList / ElementMap option

[Niall G. - Y. <Nia...@yi...>]

Sure I will consider it for a future release, it should be a fairly simple change.

From: Lumsdon, Hugo [mailto:Hug...@bl...]
Sent: Thursday, 13 June 2013 10:10 PM
To: sim...@li...
Subject: [Simple-support] Unmodifiable ElementList / ElementMap option

Hi Niall,

We've mentioned this idea before and you don't seem to express any opinion / interest.  However we'd love to be able to add an attribute to the ElementList and ElementMap annotations to indicate that these should be made immutable once an object has been de-serialized - i.e. wrapped using Collections.unmodifiableXXX.

The reason is we that we are caching most of our de-serialized Simple XML based beans - and as such don't want developers accidently trying to modify the objects thinking they're just updating a local copy.

We're currently doing this manually by creating unmodifiable wrappers to mirror each List or Map member variable.  However, whilst trivial, this adds a fair amount of code bloat and the possibility devs forget to wrap the underlying collection.  It would be so much tidier to just add a flag to the @ElementList or @ElementMap annotations and get the framework to handle it - and easier for us to search across the code base and make sure the flag is being set - i.e. along the lines of @ElementList(unmodifiable=true).

Please consider this as a future enhancement.

Thanks.







THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE PRIVILEGED. If this message was misdirected, BlackRock, Inc. and its subsidiaries, ("BlackRock") does not waive any confidentiality or privilege. If you are not the intended recipient, please notify us immediately and destroy the message without disclosing its contents to anyone. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of BlackRock, unless the author is authorized by BlackRock to express such views or opinions on its behalf. All email sent to or from this address is subject to electronic storage and review by BlackRock. Although BlackRock operates anti-virus programs, it does not accept responsibility for any damage whatsoever caused by viruses being passed.



BlackRock Advisors (UK) Limited and BlackRock Investment Management (UK) Limited are authorised and regulated by the Financial Conduct Authority. Registered in England No. 796793 and No. 2020394 respectively. BlackRock Life Limited is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority. Registered in England No. 2223202. Registered Offices: Drapers Gardens, 12 Throgmorton Avenue, London EC2N 2DL. BlackRock International Limited is authorised and regulated by the Financial Conduct Authority and is a registered investment adviser with the Securities and Exchange Commission (SEC). Registered in Scotland No. SC160821. Registered Office: 40 Torphichen Street, Edinburgh, EH3 8JB.

(c) 2013 BlackRock, Inc. All Rights reserved.

[Simple-support] Unmodifiable ElementList / ElementMap option

[Lumsdon, H. <Hug...@bl...>]

Hi Niall,

We've mentioned this idea before and you don't seem to express any opinion / interest.  However we'd love to be able to add an attribute to the ElementList and ElementMap annotations to indicate that these should be made immutable once an object has been de-serialized - i.e. wrapped using Collections.unmodifiableXXX.

The reason is we that we are caching most of our de-serialized Simple XML based beans - and as such don't want developers accidently trying to modify the objects thinking they're just updating a local copy.

We're currently doing this manually by creating unmodifiable wrappers to mirror each List or Map member variable.  However, whilst trivial, this adds a fair amount of code bloat and the possibility devs forget to wrap the underlying collection.  It would be so much tidier to just add a flag to the @ElementList or @ElementMap annotations and get the framework to handle it - and easier for us to search across the code base and make sure the flag is being set - i.e. along the lines of @ElementList(unmodifiable=true).

Please consider this as a future enhancement.

Thanks.






THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE PRIVILEGED.  If this message was misdirected, BlackRock, Inc. and its subsidiaries, ("BlackRock") does not waive any confidentiality or privilege.  If you are not the intended recipient, please notify us immediately and destroy the message without disclosing its contents to anyone.  Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized.  The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of BlackRock, unless the author is authorized by BlackRock to express such views or opinions on its behalf.  All email sent to or from this address is subject to electronic storage and review by BlackRock.  Although BlackRock operates anti-virus programs, it does not accept responsibility for any damage whatsoever caused by viruses being passed.


--
BlackRock Advisors (UK) Limited and BlackRock Investment Management (UK) Limited are authorised and regulated by the Financial Conduct Authority. Registered in England No. 796793 and No. 2020394 respectively. BlackRock Life Limited is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority. Registered in England No. 2223202. Registered Offices: Drapers Gardens, 12 Throgmorton Avenue, London EC2N 2DL. BlackRock International Limited is authorised and regulated by the Financial Conduct Authority and is a registered investment adviser with the Securities and Exchange Commission (SEC).  Registered in Scotland No. SC160821. Registered Office: 40 Torphichen Street, Edinburgh, EH3 8JB.

© 2013 BlackRock, Inc. All Rights reserved.

[Simple-support] [simple-xml] Mapping with XPath expressions

[Arnaud b. <arn...@gm...>]

Hello,

In "Mapping with XPath expressions", we can step over some element.
But can we used Path annotation to filter extracted node:

@Root
class Root {
@Element
@Path("Element[id='10']")
Element element;
}

@Root
class Element {
@Attibute
int id;
}

<root>
<element id="1"/>
<element id="10"/>
</root>

Regards,

Arnaud.