Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP 3 Classic ASP Active Server Pages 3.0 > Classic ASP XML
Password Reminder
Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
Classic ASP XML Using ASP 3 and XML. See also the XML category for more XML discussions not relating to ASP. NOT for ASP.NET 1.0, 1.1, or 2.0
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Classic ASP XML section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old July 9th, 2005, 01:18 PM
Registered User
Join Date: Dec 2003
Location: London, , United Kingdom.
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default Achitecture ? SQL -> XML -> ASP -> PDF or HTML Frm


This query is by way of a design / architecture sanity check first and then a question about how to undertake the integration. if someone can advise I'd appreciate the steer now at design time rather than finding out that the concept is completely cookie later on after I have written code.

1) Raw data for standard document fields will be stored in SQL Server. The documents will require data entry via online forms and can be presented back within a navigable Web application and in a format suitable for printing.
- An ASP.Net application will manage the presentation of the data via HTML to a browser for data entry update etc.
- I'm happy with this chain end to end, i.e. SQL Server -> ASP -> HTML, and would separate the business layer from the form layer using code behind modules.
2) Users will require to generate a document for signature and permanent storage. (Paper audit trails are still a requirement in some areas)
- I was planning to use the SQL Server XML capabilities in conjunction with a pre-built XSL-FO stylesheet to generate a .pdf document all nicely formatted and ready for printing... .pdfs being a little less open to user editing than .doc files.

It occurred to me that I could try to use the SQL Server / XML capabilities, possibly in conjunction with XSLT, to create the main data forms and incorporate them within an ASP Wrapper that manages the presentation of application navigation elements, i.e. menus, button controls etc., thus enabling me to be able to re-use components.

I was planning using the Apache XSL_FO engine for the .PDF generation and have determined how the FO.BAT file might be triggered from within ASP.NET (VB environment)

Is this a viable approach? and if so how would I integrate the components. If there is a better way of achieving the results I want then I'm open to suggestions. I'm at a design stage. If I've missed an ASP - XML - SQL integration bit I'll be content with "RTM!" and a reference to the example, see reference list below.

The issue I am not clear on is how to integrate the components seamlessly.
- Is it necessary to create and store a physical .XML/XSL file within the application layer that can then be referenced by the presentation layer as in the AdRotator examples within ASP.Net Website Programming and ASP.Net 1.1 with VB.Net 2003? These seem to imply a separation between the XML and database elements of the application.

Or, can some sort of stream object be used to pass the data between the two layers? Ideally I'd prefer not to be generating XML files that need cleaning off the server on an automated basis.

The references I have available are:
ASP.Net 1.1 with VB.NET 2003
XSLT 2.0
SQL Server 2000 XML
ASP.Net Website programming
a couple of XSL-FO books by other publishers.

Tools available: SQL Server, Visual Studio.Net (I know VB), Altova's XMLSpy and Stylevision (with .Net Integration). The Rational Rose XDE tool is being used to model the classes for the different layers and generate out the class code stubs.
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Chpt 7 >> Pg 245 >>Try It Out #4-5 harrison4411 BOOK: Beginning ASP.NET 2.0 BOOK VB ISBN: 978-0-7645-8850-1; C# ISBN: 978-0-470-04258-8 0 March 2nd, 2006 06:26 PM
Forms with XML > XSLT > XHTML kwilliams XSLT 0 October 27th, 2005 09:52 AM
HELP: XSL -> HTML <select selected=true> jedbartlett XSLT 4 October 7th, 2004 11:16 PM
VB.Net -> Filename -> DTS Package -> tempdB daniel Pro VB.NET 2002/2003 1 October 7th, 2004 01:46 PM
asp(ado->xml) --->internet>--asp(xml->ado) moon XML 0 November 28th, 2003 09:27 AM

All times are GMT -4. The time now is 06:25 AM.

Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.