AW: My first contact with StrutsCX

Hi Bertrand,

I added the setSystemId() to the StrutsCXURIResolver, too. Thanks again
for the hint.

Your statement about Castor is exactly what I do towards the
backend/data storage... Anyways, I guess that 'Castor will respect the
XSD when marshalling' this is the point. - This is one advantages of a
Castor XML solution; are there others? What about performance...? How do
you pass the XSD to your StrutsCXDocumentBuilder? Do you use the
strutscx-config.xml to tell StrutsCX where to find the XSD? - Besides
that and lack of time I do not have any problem to add an (optional)
Castor XML based StrutsCXDocumentBuilder/StrutsCXBeanToElement version
to StrutsCX. 

Regards,

Berny


-----Ursprüngliche Nachricht-----
Von: [email protected]
[mailto:[email protected]] Im Auftrag von
Bertrand Martel
Gesendet: Samstag, 24. Januar 2004 19:03
An: [email protected]
Betreff: RE: [Strutscx-user] My first contact with StrutsCX

> Thanks for your comments on StrutsCX. Very helpful!

You are welcome !

> BTW, what advantages do you see in replacing the actual
checkBeanContent
with a Castor 
> XML solution? One disadvantage I see, is the 1.1 MB size of Castor XML
JAR.

Well Castor is a (the most ?) powerfull way of mapping XML to JavaBean.
With
a nice XSD editor (XMLSPy for instance) you build your Schemas. From the
same file (the XSD) you can build your beans (for logic layer) and your
XSL
(for presentation layer). Castor will respect the XSD when marshalling
(an
attribute of a node will be serialize as is, etc). Moreover, you benefit
from the Castor checking/validating system. Why don't you provide a
"Castor"
way of serializing and people interesting in this process will change
their
configuration file (strutscx-config.xml) and add the castor.jar file.

> I followed your suggestion and added the 
> ss.setSystemId(url.toString()); line to the 
> createXSLTemplate() method of the StrutsCXStandardTransformer. 

Great ! I forgot to mention that the setSystemId() method should also be
set
in the URIResolver to the Source returned by the resolve() method. If
the
included/imported XSL (which URI is resolved from the URIResolver)
contains
as well a "<!DOCTYPE ...>" then we need the SystemId to be set.

Regars,

Bertrand.



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Strutscx-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/strutscx-user



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn