simple-support — General user and support issues

Re: [Simple-support] Best way to start reusing simple code in order to automatically generate documentation

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

There is an example in a test called CommentTest of how to add your own annotations that can be used by Simple. This allows you to add custom annotations that can be processed, perhaps this can help with documentation generation? 


________________________________
From: Serge SIMON <ser...@gm...>
To: sim...@li...
Sent: Sunday, 2 October 2011 9:30 PM
Subject: [Simple-support] Best way to start reusing simple code in order to automatically generate documentation


Hello,

I'm using Simple with great success on various projects.
One of my usual use is to read and write application configuration. 
Sometimes this configuration becomes quite heavy and complicated.

I would like to write something to automatically generate my documentation (in HTML, Wiki, or Doxia format) from the annotations used for Simple (maybe with a few additionnal ones, for example a new @Description one). This way i would have an always up-to-date configuration accessible to users, without the hassle of maintaining this by hand.

What would be in your opinion the best and easiest way to start ? (i can of course do the while thing outside the Simple code, but it would maybe be a better idea to reuse as much code as possible from Simple). Any clues about where to start (in a few words) ?

Regards.

-- 
Serge.

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

Re: [Simple-support] Boolean Attribute 0 or 1

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

For primitives like boolean you must use a Transform not a Converter


________________________________
From: jc.jourdon <jc....@7g...>
To: sim...@li...
Sent: Friday, 30 September 2011 10:47 AM
Subject: [Simple-support]  Boolean Attribute 0 or 1

hello,

you've done a great job with this tool and i already parsed many 
different XML from soap servers since last 3 days, but i encountered 
boolean attributes with "0" or "1"

<list mybool1="0" mybool2="1" attr1="attr" attr2="attr">
<page mybool3="1">
         ...
</page>
<page mybool3="0">
         ...
</page>
     ...
</list>

I tried to create this class :

public class Boolean01Converter implements Converter<Boolean>
{
      @Override
     public Boolean read(InputNode node) throws Exception {
         return new Boolean(node.getValue().equals("1"));
     }
      @Override
     public void write(OutputNode node, Boolean value) throws Exception {
         node.setValue(value.booleanValue()?"1":"0");
     }
}

and implemented it on my object definition :

@Root(name="list")
public class ListFcts
{
     @Attribute
     @Convert(Boolean01Converter.class)
     private Boolean mybool1;

     @Attribute
     @Convert(Boolean01Converter.class)
     private Boolean mybool2;

     @Attribute
     private int ...

     @ElementList(name="page", inline=true)
     private List<Page> pages;
}


But i still get false for every boolean.

Also : how can I attach the converter to the Persister instead of 
declaring it on @Attributes hundred times ?

Many thanks in advance !!


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

Re: [Simple-support] How to add support for Object[] to a Transform?

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

You would need a Converter for this

@Convert(ObjectArrayConverter.class)
private Object[] x


________________________________
From: Marco LOMBARDO <mar...@ya...>
To: "sim...@li..." <sim...@li...>
Sent: Tuesday, 27 September 2011 11:41 PM
Subject: [Simple-support] How to add support for Object[] to a Transform?

I have a collection of value coming from a database, the generic record should be used for more than one table.

So I decide to use a Object[] to load values. But seems that this is not suported.
The problem is a bit more complicated: some value of the Object[] are Object[].

There is a way to add this Transform/Visitor?
Thx.
Mar

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

[Simple-support] Thank you note!

[--sowdri-- <so...@gm...>]

Hi Simple Team,

First of all, I'm not sure whether I can send feedback on the mailing list,
searched on the site but couldn't find some sort of feedback section.

Simple is a wonderful idea and the way its has been implemented is awesome!
Many thanks for Simple Team and special thanks for the designers to have
come up with an intuitive and natural way of expressing the relationship! I
could imagine the amount of code that could have been save if I had come
across simple-framework an year ago!

SimpleFramework rocks!
-- 
-sowdri-

Re: [Simple-support] How to provide annotations to the enum classes?

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

Use a Transformer for Enums



________________________________
From: A K <ak....@gm...>
To: sim...@li...
Sent: Monday, 26 September 2011 7:27 AM
Subject: [Simple-support] How to provide annotations to the enum classes?


Hi I have the below source data. And i want to provide the annotation to the enum class. When i give, it is throwing an exception. Pls let me know how to provide the annotations to the enum classes. Thanks in advance.



public class CTSystemData

{    private STSystemDataVal val;   // ---------------------------attribute type="ST_SystemDataVal" use="required" name="val"

    public STSystemColorVal getVal() {
        return val;
    }

    public void setVal(STSystemColorVal val) {
        this.val = val;
    }
}

public enum STSystemDataVal {
    MENU1("menu1"),
    MENU2("menu2"), 
    MENU3("menu3"), 
    MENU4("menu4"),  
    private final String value;

    private STSystemDataVal(String value) {
        this.value = value;
    }

    public String xmlValue() {
        return value;
    }
}

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

[Simple-support] Best way to start reusing simple code in order to automatically generate documentation

[Serge S. <ser...@gm...>]

Hello,

I'm using Simple with great success on various projects.
One of my usual use is to read and write application configuration.
Sometimes this configuration becomes quite heavy and complicated.

I would like to write something to automatically generate my documentation
(in HTML, Wiki, or Doxia format) from the annotations used for Simple (maybe
with a few additionnal ones, for example a new @Description one). This way i
would have an always up-to-date configuration accessible to users, without
the hassle of maintaining this by hand.

What would be in your opinion the best and easiest way to start ? (i can of
course do the while thing outside the Simple code, but it would maybe be a
better idea to reuse as much code as possible from Simple). Any clues about
where to start (in a few words) ?

Regards.

-- 
Serge.

[Simple-support] Boolean Attribute 0 or 1

[jc.jourdon <jc....@7g...>]

hello,

you've done a great job with this tool and i already parsed many 
different XML from soap servers since last 3 days, but i encountered 
boolean attributes with "0" or "1"

<list mybool1="0" mybool2="1" attr1="attr" attr2="attr">
<page mybool3="1">
         ...
</page>
<page mybool3="0">
         ...
</page>
     ...
</list>

I tried to create this class :

public class Boolean01Converter implements Converter<Boolean>
{
      @Override
     public Boolean read(InputNode node) throws Exception {
         return new Boolean(node.getValue().equals("1"));
     }
      @Override
     public void write(OutputNode node, Boolean value) throws Exception {
         node.setValue(value.booleanValue()?"1":"0");
     }
}

and implemented it on my object definition :

@Root(name="list")
public class ListFcts
{
     @Attribute
     @Convert(Boolean01Converter.class)
     private Boolean mybool1;

     @Attribute
     @Convert(Boolean01Converter.class)
     private Boolean mybool2;

     @Attribute
     private int ...

     @ElementList(name="page", inline=true)
     private List<Page> pages;
}


But i still get false for every boolean.

Also : how can I attach the converter to the Persister instead of 
declaring it on @Attributes hundred times ?

Many thanks in advance !!

[Simple-support] order of elements not preserved?

[Chandra M. <bsc...@ms...>]

Hi All, 
I am using SimpleXml 2.6.1 in my android app. Eventhough the document says the order of the elements in the xml are same as the way they have defined in the class file, I am always getting the order to be random in the xml. If I add few more variables, the order of the elements again changes. Adding @Order notation works, but since the class is complex with 100s of variables, I do not want to add order. Is this a known bug for android versions? 
p.s: I opened the .class file disassembled and found the variables declared in the same order as java file, so I don't think it's a class file issue. 
Warm Regards,Chandra
 		 	   		  

Re: [Simple-support] How to add support for Object[] to a Transform?

[Marco L. <mar...@ya...>]

Ok, I made some tests, don't know if I found a bug. The code below fires a NPE at TestStrategy.java:191
This is my case: an array of object where each element can be an Object so even a Object[].
After this I will try to figure out how to serialize this structure. Thx.

Mar
------------------------------ TestObject start ----------------------------------

import java.io.File;

import org.simpleframework.xml.ElementArray;
import org.simpleframework.xml.Root;
import org.simpleframework.xml.Serializer;
import org.simpleframework.xml.core.Persister;

@Root
public class TestObject {
    
    @ElementArray
    private Object[] values = null;
    
    public TestObject(Object[] values) {
        this.values = values;
    }

    public static void main(String[] args) {
        Object[] value1 = new Object[] {
                new Object[]{new Object[]{"ref1"}, "v1"}
                , new Object[]{new Object[]{"ref2"}, "v2"}
        };
        TestObject testObject = new TestObject(value1);
        Serializer serializer = new Persister();
        File result = new File("/tmp/example.xml");
        try {
            serializer.write(testObject, result);
        } catch (Exception e) {
            e.printStackTrace();
        }
    }
}

------------------------------ TestObject end ----------------------------------


----- Original Message -----
From: Marco LOMBARDO <mar...@ya...>
To: "sim...@li..." <sim...@li...>
Cc: 
Sent: Wednesday, September 28, 2011 12:41 AM
Subject: [Simple-support] How to add support for Object[] to a Transform?

I have a collection of value coming from a database, the generic record should be used for more than one table.

So I decide to use a Object[] to load values. But seems that this is not suported.
The problem is a bit more complicated: some value of the Object[] are Object[].

There is a way to add this Transform/Visitor?
Thx.
Mar

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

[Simple-support] simple not working on android device

[<da...@al...>]

Hi all,I'm using Simple 2.6.1 on an Android project for serialize some complex xml files. I use Eclipse and followed the procedure described on the project site (Simple XML in Android 1.5 and Up):
1) created the "libs" folder on the project root2) put simple-xml-2.6.1.jar in the "libs" folder3) added the jar to the build path4) selected for export on the build path
All works fine when I run the application on the android emulator. But when I install the application on the device I get a crash at the time of serialization.
What's wrong?
P.S. I'm developing with android api level 8 (android 2.2)

[Simple-support] How to add support for Object[] to a Transform?

[Marco L. <mar...@ya...>]

I have a collection of value coming from a database, the generic record should be used for more than one table.

So I decide to use a Object[] to load values. But seems that this is not suported.
The problem is a bit more complicated: some value of the Object[] are Object[].

There is a way to add this Transform/Visitor?
Thx.
Mar

[Simple-support] How to provide annotations to the enum classes?

[A K <ak....@gm...>]

Hi I have the below source data. And i want to provide the annotation to the
enum class. When i give, it is throwing an exception. Pls let me know how to
provide the annotations to the enum classes. Thanks in advance.



public class CTSystemData

{    private *STSystemDataVal *val;   //
---------------------------attribute type="ST_SystemDataVal" use="required"
name="val"

    public STSystemColorVal getVal() {
        return val;
    }

    public void setVal(STSystemColorVal val) {
        this.val = val;
    }
}

public enum STSystemDataVal {
    MENU1("menu1"),
    MENU2("menu2"),
    MENU3("menu3"),
    MENU4("menu4"),
    private final String value;

    private STSystemDataVal(String value) {
        this.value = value;
    }

    public String xmlValue() {
        return value;
    }
}

Re: [Simple-support] null variables and suppressing empty tags

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

Yep, that would work in the meantime.

--- On Thu, 22/9/11, Erez Lirov <er...@es...> wrote:

From: Erez Lirov <er...@es...>
Subject: Re: [Simple-support] null variables and suppressing empty tags
To: "Niall Gallagher" <gal...@ya...>
Cc: "James Oltmans" <Jam...@ip...>, "sim...@li..." <sim...@li...>
Received: Thursday, 22 September, 2011, 6:15 AM

Thanks!  I was also thinking about plugging in a different/custom serializer here:
 private static final Serializer serializer = new Persister(new AnnotationStrategy());
Does this make any sense or am I barking up the wrong tree?



On Thu, Sep 22, 2011 at 6:20 AM, Niall Gallagher <gal...@ya...> wrote:


Hi,
I think for this a change is required. Currently the @Path is required regardless of whether the elements are null or not.


I will take a look at adding something like this.
Niall

--- On Wed, 21/9/11, Erez Lirov <er...@es...> wrote:



From: Erez Lirov <er...@es...>
Subject: Re: [Simple-support] null variables and suppressing empty tags


To: "Niall Gallagher" <gal...@ya...>
Cc: "James Oltmans" <Jam...@ip...>, "sim...@li..." <sim...@li...>


Received: Wednesday, 21 September, 2011, 6:10 AM

Oops.  I'm sorry.  That
 was supposed to be @Path("To")  I think I was switching things out while testing and copying.  Here's the current copy of the code.  I just executed and it produced:<ContinuityOfCareRecord>



   <To/></ContinuityOfCareRecord>
---------------
import org.junit.Before;import org.junit.Test;import org.simpleframework.xml.Element;



import org.simpleframework.xml.Path;import org.simpleframework.xml.Root;
import com.espoc.vrclcommon.util.XmlUtil;
public class CcrTest {




  @Root(name = "ContinuityOfCareRecord")  static class Test1 {    @Element(name = "ActorLink", required = false)    @Path("To")    protected CcrDocActorLink toLink;



  }
  @Before  public void setUp() throws Exception {  }
  @Test  public void test() throws Exception {    // CcrDoc doc = sample();



    Test1 doc = new Test1();    System.out.println(XmlUtil.getAsString(doc));  }}
public class XmlUtil {  private static final Serializer serializer = new Persister(new AnnotationStrategy());




  public static String getAsString(Object obj) throws Exception {    ByteArrayOutputStream b = new ByteArrayOutputStream();    serializer.write(obj, b);    return b.toString();



  }}
On Wed, Sep 21, 2011 at 4:40 AM, Niall Gallagher <gal...@ya...> wrote:




The below annotated class will not generate the XML you provided. Can you provide a proper example of what you are doing.





--- On Tue, 20/9/11, Erez Lirov <er...@es...> wrote:





From: Erez Lirov <er...@es...>
Subject: Re: [Simple-support] null variables and suppressing empty tags
To: "James Oltmans" <Jam...@ip...>




Cc: "sim...@li..." <sim...@li...>




Received: Tuesday, 20 September, 2011, 12:05 PM

Doesn't look like the @Path annotation accepts required=false.  It looks like @Path only accepts one parameter, the path string...



On Tue, Sep 20, 2011 at 11:52 AM, James
 Oltmans <Jam...@ip...> wrote:


Set required = false for the To element

 From: Erez Lirov [mailto:er...@es...] 






Sent: Tuesday, September 20, 2011 7:25 AM
To: sim...@li...
Subject: [Simple-support] null variables and suppressing empty tags





 I have an annotated class that has a null field like this: 

@Root(name = "ContinuityOfCareRecord")class Test1 {  @Element(name = "ActorID", required = false)

  @Path("Patient")  protected String patientId;}

 generating the XML gives:<ContinuityOfCareRecord>

   <To/></ContinuityOfCareRecord> Is there any way to automatically suppress the <To/> tag since there are no values under it?





 Thanks!


-- 
The materials in this e-mail are private, may contain Protected Health Information as defined by the Health Insurance Portability and Accounting Act of 1986 (as codified at 42 U.S.C. 1320d through d-8), and are intended only for the use of the individual(s) named above. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this to the intended recipient, you are hereby notified that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited.  If you have received this e-mail in error, please immediately notify us by telephone at 877-753-4286 or notify us by e-mail at hel...@ve.... Thank you.








-----Inline Attachment Follows-----

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a




definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1




-----Inline Attachment Follows-----

_______________________________________________
Simple-support mailing list
Sim...@li...




https://lists.sourceforge.net/lists/listinfo/simple-support







-- 
The materials in this e-mail are private, may contain Protected Health Information as defined by the Health Insurance Portability and Accounting Act of 1986 (as codified at 42 U.S.C. 1320d through d-8), and are intended only for the use of the individual(s) named above. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this to the intended recipient, you are hereby notified that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited.  If you have received this e-mail in error, please immediately notify us by telephone at 877-753-4286 or notify us by e-mail at hel...@ve.... Thank you.









-- 
The materials in this e-mail are private, may contain Protected Health Information as defined by the Health Insurance Portability and Accounting Act of 1986 (as codified at 42 U.S.C. 1320d through d-8), and are intended only for the use of the individual(s) named above. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this to the intended recipient, you are hereby notified that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited.  If you have received this e-mail in error, please immediately notify us by telephone at 877-753-4286 or notify us by e-mail at hel...@ve.... Thank you.

Re: [Simple-support] null variables and suppressing empty tags

[Erez L. <er...@es...>]

Thanks!  I was also thinking about plugging in a different/custom serializer
here:
 private static final Serializer serializer = new Persister(new
AnnotationStrategy());

Does this make any sense or am I barking up the wrong tree?

On Thu, Sep 22, 2011 at 6:20 AM, Niall Gallagher
<gal...@ya...>wrote:

> Hi,
>
> I think for this a change is required. Currently the @Path is required
> regardless of whether the elements are null or not.
>
> I will take a look at adding something like this.
>
> Niall
>
>
> --- On *Wed, 21/9/11, Erez Lirov <er...@es...>* wrote:
>
>
> From: Erez Lirov <er...@es...>
> Subject: Re: [Simple-support] null variables and suppressing empty tags
> To: "Niall Gallagher" <gal...@ya...>
> Cc: "James Oltmans" <Jam...@ip...>, "
> sim...@li..." <
> sim...@li...>
> Received: Wednesday, 21 September, 2011, 6:10 AM
>
>
> Oops.  I'm sorry.  That was supposed to be @Path("To")  I think I was
> switching things out while testing and copying.  Here's the current copy of
> the code.  I just executed and it produced:
> <ContinuityOfCareRecord>
>    <To/>
> </ContinuityOfCareRecord>
>
> ---------------
>
> import org.junit.Before;
> import org.junit.Test;
> import org.simpleframework.xml.Element;
> import org.simpleframework.xml.Path;
> import org.simpleframework.xml.Root;
>
> import com.espoc.vrclcommon.util.XmlUtil;
>
> public class CcrTest {
>
>   @Root(name = "ContinuityOfCareRecord")
>   static class Test1 {
>     @Element(name = "ActorLink", required = false)
>     @Path("To")
>     protected CcrDocActorLink toLink;
>   }
>
>   @Before
>   public void setUp() throws Exception {
>   }
>
>   @Test
>   public void test() throws Exception {
>     // CcrDoc doc = sample();
>     Test1 doc = new Test1();
>     System.out.println(XmlUtil.getAsString(doc));
>   }
> }
>
> public class XmlUtil {
>   private static final Serializer serializer = new Persister(new
> AnnotationStrategy());
>
>   public static String getAsString(Object obj) throws Exception {
>     ByteArrayOutputStream b = new ByteArrayOutputStream();
>     serializer.write(obj, b);
>     return b.toString();
>   }
> }
>
> On Wed, Sep 21, 2011 at 4:40 AM, Niall Gallagher <
> gal...@ya... <http://mc/compose?to=...@ya...>
> > wrote:
>
> The below annotated class will not generate the XML you provided. Can you
> provide a proper example of what you are doing.
>
> --- On *Tue, 20/9/11, Erez Lirov <er...@es...<http://mc/compose?to...@es...>
> >* wrote:
>
>
> From: Erez Lirov <er...@es... <http://mc/compose?to...@es...>>
> Subject: Re: [Simple-support] null variables and suppressing empty tags
> To: "James Oltmans" <Jam...@ip...<http://mc/compose?to=...@ip...>
> >
> Cc: "sim...@li...<http://mc/compose?to=...@li...>"
> <sim...@li...<http://mc/compose?to=...@li...>
> >
> Received: Tuesday, 20 September, 2011, 12:05 PM
>
>
> Doesn't look like the @Path annotation accepts required=false.  It looks
> like @Path only accepts one parameter, the path string...
>
> On Tue, Sep 20, 2011 at 11:52 AM, James Oltmans <Jam...@ip...<http://mc/compose?to=...@ip...>
> > wrote:
>
> Set required = false for the To element****
>
> ** **
>
> *From:* Erez Lirov [mailto:er...@es...<http://mc/compose?to...@es...>]
>
> *Sent:* Tuesday, September 20, 2011 7:25 AM
> *To:* sim...@li...<http://mc/compose?to=...@li...>
> *Subject:* [Simple-support] null variables and suppressing empty tags****
>
> ** **
>
> I have an annotated class that has a null field like this:****
>
> ** **
>
> @Root(name = "ContinuityOfCareRecord")****
>
> class Test1 {****
>
>   @Element(name = "ActorID", required = false)****
>
>   @Path("Patient")****
>
>   protected String patientId;****
>
> }****
>
> ** **
>
> generating the XML gives:****
>
> <ContinuityOfCareRecord>****
>
>    <To/>****
>
> </ContinuityOfCareRecord>****
>
> ** **
>
> Is there any way to automatically suppress the <To/> tag since there are no
> values under it?****
>
> ** **
>
> Thanks!****
>
>
>
>
> --
> The materials in this e-mail are private, may contain Protected Health
> Information as defined by the Health Insurance Portability and Accounting
> Act of 1986 (as codified at 42 U.S.C. 1320d through d-8), and are intended
> only for the use of the individual(s) named above. If you are not the
> intended recipient of this e-mail, or the employee or agent responsible for
> delivering this to the intended recipient, you are hereby notified that any
> unauthorized use, disclosure, copying, distribution or the taking of any
> action in reliance on the contents of this information is strictly
> prohibited.  If you have received this e-mail in error, please immediately
> notify us by telephone at 877-753-4286 or notify us by e-mail at
> hel...@ve... <http://mc/compose?to=...@ve...>. Thank
> you.
>
> -----Inline Attachment Follows-----
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Simple-support mailing list
> Sim...@li...<http://mc/compose?to=...@li...>
> https://lists.sourceforge.net/lists/listinfo/simple-support
>
>
>
>
> --
> The materials in this e-mail are private, may contain Protected Health
> Information as defined by the Health Insurance Portability and Accounting
> Act of 1986 (as codified at 42 U.S.C. 1320d through d-8), and are intended
> only for the use of the individual(s) named above. If you are not the
> intended recipient of this e-mail, or the employee or agent responsible for
> delivering this to the intended recipient, you are hereby notified that any
> unauthorized use, disclosure, copying, distribution or the taking of any
> action in reliance on the contents of this information is strictly
> prohibited.  If you have received this e-mail in error, please immediately
> notify us by telephone at 877-753-4286 or notify us by e-mail at
> hel...@ve... <http://mc/compose?to=...@ve...>. Thank
> you.
>
>


-- 
The materials in this e-mail are private, may contain Protected Health
Information as defined by the Health Insurance Portability and Accounting
Act of 1986 (as codified at 42 U.S.C. 1320d through d-8), and are intended
only for the use of the individual(s) named above. If you are not the
intended recipient of this e-mail, or the employee or agent responsible for
delivering this to the intended recipient, you are hereby notified that any
unauthorized use, disclosure, copying, distribution or the taking of any
action in reliance on the contents of this information is strictly
prohibited.  If you have received this e-mail in error, please immediately
notify us by telephone at 877-753-4286 or notify us by e-mail at
hel...@ve.... Thank you.

Re: [Simple-support] Same Attribute name and different namespace

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

You will have to write a Converter for this. There are some examples in the test cases and the tutorial.

--- On Thu, 22/9/11, A K <ak....@gm...> wrote:

From: A K <ak....@gm...>
Subject: [Simple-support] Same Attribute name and different namespace
To: sim...@li...
Received: Thursday, 22 September, 2011, 12:03 AM



Hi,
 I have the below input xml file. Am trying to read the data by providing the annotations.


<p:input 
    saveSubsetFonts="1">
    <p:sldMasterIdLst>
        <p:masterId id="2147483660" r:id="rId1" />

    </p:sldMasterIdLst>
    <p:sldIdLst>
        <p:Id id="256" r:id="rId2" />

        <p:Id id="257" r:id="rId3" />
        <p:Id id="258" r:id="rId4" />

        <p:Id id="259" r:id="rId5" />
        <p:Id id="275" r:id="rId6" />

    </p:sldIdLst>
</p:input>


The schema definations says as below

 &lt;xs:attribute type="xs:int" use="optional" name="id"/>

 *   &lt;xs:attribute use="required" ref="ns1:id"/>
 * &lt;/xs:complexType>
 * 
 * &lt;xs:attribute xmlns:ns="http://namespace1/main" xmlns:ns1="http://namespace2/relationships" xmlns:xs="http://namespace3" type="xs:string" name="id"/>


Both the id's attribute has the same name "id". I tried giving the annotations as 


@Attribute(required=false)
    @Namespace(reference="http://www.w3.org/2001/XMLSchema")
    private Integer id;

    
    @Attribute(name="id")
    @Namespace(prefix="r",reference="http://schemas.openxmlformats.org/officeDocument/2006/relationships")

    private String id1;


But, getting the exception :  Exception : org.simpleframework.xml.core.PersistenceException: Duplicate annotation of name 'id' on field 'id1' private java.lang.String org..main.MasterIdListEntry.id1


If anyone know how to give exactly, please let me know.

Thanks in advance



-----Inline Attachment Follows-----

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
-----Inline Attachment Follows-----

_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

Re: [Simple-support] Attribute field for "default" field

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

Here are some ways
@Attributeprivate String x = "default value"
or 
@Attribute(empty="default value")private String x; // x = "default value" if it is null when writing
Niall

--- On Wed, 21/9/11, A K <ak....@gm...> wrote:

From: A K <ak....@gm...>
Subject: [Simple-support] Attribute field for "default" field
To: sim...@li...
Received: Wednesday, 21 September, 2011, 11:04 PM

Hi,

I have the below declaration for the attrubute.


&lt;xs:attribute type="xs:int" use="optional" default="50000" name="tagname1"/>

&lt;xs:attribute type="xs:int" use="optional" default="1" name="tagname2"/>
xs:attribute type="xs:boolean" use="optional" default="true" name="tagname3"



The way we provide annotations is as below:

 @Attribute(required=false)
 private Integer tagname1;
 @Attribute(required=false)
 private Integer tagname2;
 @Attribute(required=false)

private Boolean tagname3;


Does default="50000" has any significance? is there any field in attribute to provide "default" data, like we give "required=false" for "use=optional"?



-----Inline Attachment Follows-----

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
-----Inline Attachment Follows-----

_______________________________________________
Simple-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simple-support

Re: [Simple-support] implementing a progress bar

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

Yes, you need to know what your parsing, you could write a Visitor to check things like this.

"element1" = 10%
"element2" = 12%
"element4" = 50%

etc... With this you need to know the elements in advance. If you don't know them, then using an input steam with an upfront file size would be best.

--- On Wed, 21/9/11, Aaron Digulla <di...@he...> wrote:

> From: Aaron Digulla <di...@he...>
> Subject: Re: [Simple-support] implementing a progress bar
> To: sim...@li...
> Received: Wednesday, 21 September, 2011, 11:28 AM
> Am 21.09.2011 15:05, schrieb Krein,
> Jörg:
> > Hi,
> > 
> > I need to add a progress bar to visualize the
> (de)serialization process.
> > Please give me some hints how to achive this.
> > From what I understand one way is to use a visitor?
> > A simple example would be very helpful.
> 
> That depends on what you know.
> 
> Do you know in advance how many XML elements the document
> contains?
> 
> If not, do you know the file size?
> 
> If you know the latter, you can create an InputStream
> (derived from
> FilterInputStream) which updates a counter with the number
> of bytes read
> so far.
> 
> That allows you to read this information from a second
> thread or by
> triggering a callback after a certain number of bytes have
> been read.
> 
> In the former case, you need to hook into the
> (de)serialization process.
> I'm not sure whether a visitor is really helpful here.
> 
> Regards,
> 
> -- 
> Aaron "Optimizer" Digulla a.k.a. Philmann Dark
> "It's not the universe that's limited, it's our
> imagination.
> Follow me and I'll show you something beyond the limits."
> http://blog.pdark.de/
> 
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT
> infrastructure contains a
> definitive record of customers, application performance,
> security
> threats, fraudulent activity and more. Splunk takes this
> data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Simple-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simple-support
> 

Re: [Simple-support] populating ElementMap

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

Its false for a reason only <exported>true</exported> is true. <exported>  true</exported> is false, because it evaluates to "  true". Your options are to a) write a Transform to parse boolean values or b) change your XML.

--- On Wed, 21/9/11, bubbleguuum <bub...@fr...> wrote:

> From: bubbleguuum <bub...@fr...>
> Subject: [Simple-support] populating ElementMap
> To: sim...@li...
> Received: Wednesday, 21 September, 2011, 7:15 AM
> Give then following XML:
> 
> <devices>
>     <device udn="1">
>         <exported>
>            
> true
>         </exported>
>     </device>
>     <device udn="2">
>         <exported>
>            
> false
>         </exported>
>     </device>
> </devices>
> 
> 
> I want to populate a Map whose values are of type Device
> with:
> 
> @Root
> public static class Device {
>     @Element(required = false)
>     private boolean exported;
>     
>     public Device() {
>     }
> }
> 
> 
> The map is declared as:
> 
> @ElementMap(entry="device", key="udn", attribute=true)
> private Map<String, Device> devices;
> 
> 
> 
> The result is Map containing 2 Device with correct key, but
> the devices 
> were not parsed (ie for the first one , exported is
> false).
> 
> 
> I must be missing something obvious to achieve this ?
> 
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT
> infrastructure contains a
> definitive record of customers, application performance,
> security
> threats, fraudulent activity and more. Splunk takes this
> data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Simple-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simple-support
> 

Re: [Simple-support] null variables and suppressing empty tags

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

Hi,
I think for this a change is required. Currently the @Path is required regardless of whether the elements are null or not.
I will take a look at adding something like this.
Niall

--- On Wed, 21/9/11, Erez Lirov <er...@es...> wrote:

From: Erez Lirov <er...@es...>
Subject: Re: [Simple-support] null variables and suppressing empty tags
To: "Niall Gallagher" <gal...@ya...>
Cc: "James Oltmans" <Jam...@ip...>, "sim...@li..." <sim...@li...>
Received: Wednesday, 21 September, 2011, 6:10 AM

Oops.  I'm sorry.  That was supposed to be @Path("To")  I think I was switching things out while testing and copying.  Here's the current copy of the code.  I just executed and it produced:<ContinuityOfCareRecord>

   <To/></ContinuityOfCareRecord>
---------------
import org.junit.Before;import org.junit.Test;import org.simpleframework.xml.Element;

import org.simpleframework.xml.Path;import org.simpleframework.xml.Root;
import com.espoc.vrclcommon.util.XmlUtil;
public class CcrTest {


  @Root(name = "ContinuityOfCareRecord")  static class Test1 {    @Element(name = "ActorLink", required = false)    @Path("To")    protected CcrDocActorLink toLink;

  }
  @Before  public void setUp() throws Exception {  }
  @Test  public void test() throws Exception {    // CcrDoc doc = sample();

    Test1 doc = new Test1();    System.out.println(XmlUtil.getAsString(doc));  }}
public class XmlUtil {  private static final Serializer serializer = new Persister(new AnnotationStrategy());


  public static String getAsString(Object obj) throws Exception {    ByteArrayOutputStream b = new ByteArrayOutputStream();    serializer.write(obj, b);    return b.toString();

  }}
On Wed, Sep 21, 2011 at 4:40 AM, Niall Gallagher <gal...@ya...> wrote:


The below annotated class will not generate the XML you provided. Can you provide a proper example of what you are doing.



--- On Tue, 20/9/11, Erez Lirov <er...@es...> wrote:



From: Erez Lirov <er...@es...>
Subject: Re: [Simple-support] null variables and suppressing empty tags
To: "James Oltmans" <Jam...@ip...>


Cc: "sim...@li..." <sim...@li...>


Received: Tuesday, 20 September, 2011, 12:05 PM

Doesn't look like the @Path annotation accepts required=false.  It looks like @Path only accepts one parameter, the path string...



On Tue, Sep 20, 2011 at 11:52 AM, James
 Oltmans <Jam...@ip...> wrote:


Set required = false for the To element

 From: Erez Lirov [mailto:er...@es...] 




Sent: Tuesday, September 20, 2011 7:25 AM
To: sim...@li...
Subject: [Simple-support] null variables and suppressing empty tags



 I have an annotated class that has a null field like this: 

@Root(name = "ContinuityOfCareRecord")class Test1 {  @Element(name = "ActorID", required = false)

  @Path("Patient")  protected String patientId;}

 generating the XML gives:<ContinuityOfCareRecord>

   <To/></ContinuityOfCareRecord> Is there any way to automatically suppress the <To/> tag since there are no values under it?



 Thanks!


-- 
The materials in this e-mail are private, may contain Protected Health Information as defined by the Health Insurance Portability and Accounting Act of 1986 (as codified at 42 U.S.C. 1320d through d-8), and are intended only for the use of the individual(s) named above. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this to the intended recipient, you are hereby notified that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited.  If you have received this e-mail in error, please immediately notify us by telephone at 877-753-4286 or notify us by e-mail at hel...@ve.... Thank you.






-----Inline Attachment Follows-----

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a


definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1


-----Inline Attachment Follows-----

_______________________________________________
Simple-support mailing list
Sim...@li...


https://lists.sourceforge.net/lists/listinfo/simple-support





-- 
The materials in this e-mail are private, may contain Protected Health Information as defined by the Health Insurance Portability and Accounting Act of 1986 (as codified at 42 U.S.C. 1320d through d-8), and are intended only for the use of the individual(s) named above. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this to the intended recipient, you are hereby notified that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited.  If you have received this e-mail in error, please immediately notify us by telephone at 877-753-4286 or notify us by e-mail at hel...@ve.... Thank you.

[Simple-support] Same Attribute name and different namespace

[A K <ak....@gm...>]

Hi,
 I have the below input xml file. Am trying to read the data by providing
the annotations.


*<p:input
    saveSubsetFonts="1">
    <p:sldMasterIdLst>
        <p:masterId id="2147483660" r:id="rId1" />
    </p:sldMasterIdLst>
    <p:sldIdLst>
        <p:Id id="256" r:id="rId2" />
        <p:Id id="257" r:id="rId3" />
        <p:Id id="258" r:id="rId4" />
        <p:Id id="259" r:id="rId5" />
        <p:Id id="275" r:id="rId6" />
    </p:sldIdLst>
</p:**input**>*


The schema definations says as below

 *&lt;xs:attribute type="xs:int" use="optional" name="id"/>
 *   &lt;xs:attribute use="required" ref="ns1:id"/>
 * &lt;/xs:complexType>
 *
 * &lt;xs:attribute xmlns:ns="http://namespace1/main" xmlns:ns1="
http://namespace2/relationships" xmlns:xs="http://namespace3"
type="xs:string" name="id"/>*

Both the id's attribute has the same name *"id"*. I tried giving the
annotations as

*@Attribute(required=false)
    @Namespace(reference="http://www.w3.org/2001/XMLSchema")
    private Integer id;

    @Attribute(name="id")
    @Namespace(prefix="r",reference="
http://schemas.openxmlformats.org/officeDocument/2006/relationships")
    private String id1;*


But, getting the exception : * Exception :
org.simpleframework.xml.core.PersistenceException: Duplicate annotation of
name 'id' on field 'id1' private java.lang.String
org..main.MasterIdListEntry.id1*

If anyone know how to give exactly, please let me know.

Thanks in advance

[Simple-support] Attribute field for "default" field

[A K <ak....@gm...>]

Hi,

I have the below declaration for the attrubute.
*

<xs:attribute type="xs:int" use="optional" default="50000"name="tagname1"/>
<xs:attribute type="xs:int" use="optional" default="1" name="tagname2"/>*
*xs:attribute type="xs:boolean" use="optional" default="true"name="tagname3"
*


The way we provide annotations is as below:

 @Attribute(required=false)
 private *Integer tagname1*;
 @Attribute(required=false)
 private *Integer tagname2*;
 @Attribute(required=false)
private Boolean *tagname3*;


Does *default="50000" has any significance? is there any field in attribute
to provide "default" data, like we give "required=false" for "use=optional"?
*

Re: [Simple-support] implementing a progress bar

[Aaron D. <di...@he...>]

Am 21.09.2011 15:05, schrieb Krein, Jörg:
> Hi,
> 
> I need to add a progress bar to visualize the (de)serialization process.
> Please give me some hints how to achive this.
> From what I understand one way is to use a visitor?
> A simple example would be very helpful.

That depends on what you know.

Do you know in advance how many XML elements the document contains?

If not, do you know the file size?

If you know the latter, you can create an InputStream (derived from
FilterInputStream) which updates a counter with the number of bytes read
so far.

That allows you to read this information from a second thread or by
triggering a callback after a certain number of bytes have been read.

In the former case, you need to hook into the (de)serialization process.
I'm not sure whether a visitor is really helpful here.

Regards,

-- 
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://blog.pdark.de/

[Simple-support] populating ElementMap

[bubbleguuum <bub...@fr...>]

Give then following XML:

<devices>
	<device udn="1">
		<exported>
			true
		</exported>
	</device>
	<device udn="2">
		<exported>
			false
		</exported>
	</device>
</devices>


I want to populate a Map whose values are of type Device with:

@Root
public static class Device {
	@Element(required = false)
	private boolean exported;
	
	public Device() {
	}
}


The map is declared as:

@ElementMap(entry="device", key="udn", attribute=true)
private Map<String, Device> devices;



The result is Map containing 2 Device with correct key, but the devices 
were not parsed (ie for the first one , exported is false).


I must be missing something obvious to achieve this ?

Re: [Simple-support] null variables and suppressing empty tags

[Erez L. <er...@es...>]

Oops.  I'm sorry.  That was supposed to be @Path("To")  I think I was
switching things out while testing and copying.  Here's the current copy of
the code.  I just executed and it produced:
<ContinuityOfCareRecord>
   <To/>
</ContinuityOfCareRecord>

---------------

import org.junit.Before;
import org.junit.Test;
import org.simpleframework.xml.Element;
import org.simpleframework.xml.Path;
import org.simpleframework.xml.Root;

import com.espoc.vrclcommon.util.XmlUtil;

public class CcrTest {

  @Root(name = "ContinuityOfCareRecord")
  static class Test1 {
    @Element(name = "ActorLink", required = false)
    @Path("To")
    protected CcrDocActorLink toLink;
  }

  @Before
  public void setUp() throws Exception {
  }

  @Test
  public void test() throws Exception {
    // CcrDoc doc = sample();
    Test1 doc = new Test1();
    System.out.println(XmlUtil.getAsString(doc));
  }
}

public class XmlUtil {
  private static final Serializer serializer = new Persister(new
AnnotationStrategy());

  public static String getAsString(Object obj) throws Exception {
    ByteArrayOutputStream b = new ByteArrayOutputStream();
    serializer.write(obj, b);
    return b.toString();
  }
}

On Wed, Sep 21, 2011 at 4:40 AM, Niall Gallagher
<gal...@ya...>wrote:

> The below annotated class will not generate the XML you provided. Can you
> provide a proper example of what you are doing.
>
> --- On *Tue, 20/9/11, Erez Lirov <er...@es...>* wrote:
>
>
> From: Erez Lirov <er...@es...>
> Subject: Re: [Simple-support] null variables and suppressing empty tags
> To: "James Oltmans" <Jam...@ip...>
> Cc: "sim...@li..." <
> sim...@li...>
> Received: Tuesday, 20 September, 2011, 12:05 PM
>
>
> Doesn't look like the @Path annotation accepts required=false.  It looks
> like @Path only accepts one parameter, the path string...
>
> On Tue, Sep 20, 2011 at 11:52 AM, James Oltmans <Jam...@ip...<http://mc/compose?to=...@ip...>
> > wrote:
>
> Set required = false for the To element****
>
> ** **
>
> *From:* Erez Lirov [mailto:er...@es...<http://mc/compose?to...@es...>]
>
> *Sent:* Tuesday, September 20, 2011 7:25 AM
> *To:* sim...@li...<http://mc/compose?to=...@li...>
> *Subject:* [Simple-support] null variables and suppressing empty tags****
>
> ** **
>
> I have an annotated class that has a null field like this:****
>
> ** **
>
> @Root(name = "ContinuityOfCareRecord")****
>
> class Test1 {****
>
>   @Element(name = "ActorID", required = false)****
>
>   @Path("Patient")****
>
>   protected String patientId;****
>
> }****
>
> ** **
>
> generating the XML gives:****
>
> <ContinuityOfCareRecord>****
>
>    <To/>****
>
> </ContinuityOfCareRecord>****
>
> ** **
>
> Is there any way to automatically suppress the <To/> tag since there are no
> values under it?****
>
> ** **
>
> Thanks!****
>
>
>
>
> --
> The materials in this e-mail are private, may contain Protected Health
> Information as defined by the Health Insurance Portability and Accounting
> Act of 1986 (as codified at 42 U.S.C. 1320d through d-8), and are intended
> only for the use of the individual(s) named above. If you are not the
> intended recipient of this e-mail, or the employee or agent responsible for
> delivering this to the intended recipient, you are hereby notified that any
> unauthorized use, disclosure, copying, distribution or the taking of any
> action in reliance on the contents of this information is strictly
> prohibited.  If you have received this e-mail in error, please immediately
> notify us by telephone at 877-753-4286 or notify us by e-mail at
> hel...@ve... <http://mc/compose?to=...@ve...>. Thank
> you.
>
> -----Inline Attachment Follows-----
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Simple-support mailing list
> Sim...@li...<http://mc/compose?to=...@li...>
> https://lists.sourceforge.net/lists/listinfo/simple-support
>
>


-- 
The materials in this e-mail are private, may contain Protected Health
Information as defined by the Health Insurance Portability and Accounting
Act of 1986 (as codified at 42 U.S.C. 1320d through d-8), and are intended
only for the use of the individual(s) named above. If you are not the
intended recipient of this e-mail, or the employee or agent responsible for
delivering this to the intended recipient, you are hereby notified that any
unauthorized use, disclosure, copying, distribution or the taking of any
action in reliance on the contents of this information is strictly
prohibited.  If you have received this e-mail in error, please immediately
notify us by telephone at 877-753-4286 or notify us by e-mail at
hel...@ve.... Thank you.

[Simple-support] implementing a progress bar

[Krein, J. <Joe...@im...>]

Hi,

I need to add a progress bar to visualize the (de)serialization process.
Please give me some hints how to achive this.
>From what I understand one way is to use a visitor?
A simple example would be very helpful.

Thanks!