|
Well, I'm starting out small and am returning a vector that contains a
class. Here's an example...
First, I have MyClass which is really a representation of one "record" from
a file. Each attribute represents a field:
public class MyClass extends java.lang.Object
{
protected String status = null;
protected String sendID = null;
protected String sendType = null;
protected String sendBatch = null;
protected String receiveID = null;
}
Then I have another class that is a vector of MyClass's.
public class MyClassList extends MyClass
{
protected Vector myClassList = new Vector();
public MyClassList(String sendID, String recID, String batch, int
numberToLoad)
{
// build SQL, run statement using sendID, recID and batch as selection.
Load "numberToLoad" records into the vector //
while ((rsControl.next()) && (count < numberToLoad))
{
count++;
MyClass myClass = new MyClass();
myClassList.status = rsControl.getString("STATUS").trim();
myClassList.sendID = rsControl.getString("SND_ID").trim();
myClassList.sendType = rsControl.getString("SND_TYPE").trim();
myClassList.sendBatch = rsControl.getString("SND_BATCH").trim();
myClassList.receiveID = rsControl.getString("REC_ID").trim();
myClassList.addElement(myClass);
}
}
public MyClass getField(int index)
{
return (MyClass) myClassList.get(index);
}
}
No that I have a "table" object (this one is simple I understand, not a
vector of vectors, but that will come later) I want to be able somewhere to
say:
MyClassList myClassList = new MyClassList(sendID, receiveID, numberToLoad)
Then I want to have a method that will convert something to xml or html
(toXML() or toHTML());
for (int i = 0; i < myClassList.size(); i++)
{
myClassList.getField(i).status.toXML();
myClassList.getField(i).sendID.toXML();
myClassList.getField(i).sendType.toXML();
myClassList.getField(i).sendBatch.toXML();
}
etc.. etc...
That's why I asked if I could extend String() because I'd like to be able to
to .toXML() or toHTML() without haveingn to put it into another "object".
This probably makes no sense. :)
Brad
> -----Original Message-----
> From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
> Sent: Tuesday, March 13, 2001 10:27 AM
> To: JAVA400-L@midrange.com
> Subject: RE: HTML to XML, vice versa
>
>
> Good questions. Why don't you show us what your decorator
> class looks like
> and maybe we can help a little...
>
> Joe
>
>
> > -----Original Message-----
> > From: owner-java400-l@midrange.com
> > [mailto:owner-java400-l@midrange.com]On Behalf Of Stone, Brad V (TC)
> > Sent: Tuesday, March 13, 2001 10:03 AM
> > To: 'JAVA400-L@midrange.com'
> > Subject: RE: HTML to XML, vice versa
> >
> > I can understand how you would control whether to use HTML
> or XML or any
> > other decorator. With HTML this is easy because <td> is
> always <td>.
> >
> > But, if you want to use XML, where do you get the tag names from?
> > Are they
> > hard coded into the decorator? If you have a vector of
> vectors (ie a
> > "table" of data) you have no way of knowing what the data
> actually is.
> > Unless of course each object in the vector element is really a data
> > structure with different descriptors such as field name, XML tag
> > name, HTML
> > table classname, the data itself, etc...
>
> +---
> | This is the JAVA/400 Mailing List!
> | To submit a new message, send your mail to JAVA400-L@midrange.com.
> | To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> JAVA400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: joe@zappie.net
> +---
>
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.