XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Jon WilmothSubject: Open a new DB to XML data source doc in v5.1 173d
Author: Jon Wilmoth
Date: 10 Dec 2003 07:03 PM
File --> New --> DB to XML Data Source doesn't do anything. How do I create a new DB connection?

Postnext
Ivan PedruzziSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Ivan Pedruzzi
Date: 10 Dec 2003 08:53 PM
Hi Jon,

the SQL/XML plug-in requires the Java Virtual Machine.
Do you have one configured (tools->options->Application Settings->Java Virtual Machine)?

Ivan

-----Original Message-----
From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
Sent: Wednesday, December 10, 2003 7:29 PM
To: Recipients of 'stylus-studio-tech' suppressed
Subject: Open a new DB to XML data source doc in v5.1 173d

From: "Jon Wilmoth"

File --> New --> DB to XML Data Source doesn't do anything. How do I create a new DB connection?



To reply: mailto:stylus-studio-tech.7135@edn.exln.com
To start a new topic: mailto:stylus-studio-tech@edn.exln.com
To login: http://edn.exln.com/~SSDN

Postnext
Lance SelockSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Lance Selock
Date: 11 Dec 2003 01:03 AM
Ivan,

I got a little farther than Jon, but not much.

I have a JVM, as indicated by Help About: 1.4.2_02-b03 Java HotSpot(TM) Client VM Sun Microsystems Inc. debug mode port:-1

I can even "Select * from Emp" on my Oracle server from the Scott sample schema. I get a nice little XML file in the preview window. Very nice.

Unfortunately, using "Connect" to get a schema causes the familiar "swinging flashlight" to appear for a while, eventually followed by the system returning with no errors or results. Too bad, because this could be very neat if it worked.

I've tried various combinations of going in with/without a SELECT statement first, starting Stylus Studio from scratch every time or not, etc. Nothing seems to work.

On a related note, if I save the previously mentioned Scott_Emp.rdbxml to my Relational DB it appears to work and appears in the root as a document when I try to Open, but upon retrieval it's empty. Very strange! You would think if there was some kind of rights issue, the document wouldn't even appear.

My DBA_Registry reports:
COMP_NAME VERSION
------------------------------ ----------
Oracle9i Catalog Views 9.2.0.1.0
Oracle9i Packages and Types 9.2.0.1.0
Oracle Workspace Manager 9.2.0.1.0
JServer JAVA Virtual Machine 9.2.0.1.0
Oracle XDK for Java 9.2.0.2.0
Oracle9i Java Packages 9.2.0.1.0
Oracle interMedia 9.2.0.1.0
Spatial 9.2.0.1.0
Oracle Text 9.2.0.1.0
Oracle XML Database 9.2.0.1.0
Oracle Ultra Search 9.2.0.1.0
Oracle Data Mining 9.2.0.1.0
OLAP Analytic Workspace 9.2.0.1.0
Oracle OLAP API 9.2.0.1.0
OLAP Catalog 9.2.0.1.0

I'm going up to version 9.2.0.4 on the weekend, so maybe it will work next week.

Any thoughts in the meantime would be appreciated.

Thanks,

Lance.

P.S. Good luck to Jon. This looks like it's gong to be really cool if we can just get it working!





On 12/10/03 8:53:18 PM, Ivan Pedruzzi wrote:
>Hi Jon,

the SQL/XML plug-in
>requires the Java Virtual
>Machine.
Do you have one
>configured
>(tools->options->Application
>Settings->Java Virtual
>Machine)?

Ivan

-----Original
>Message-----
From:
>stylus-studio-tech Listmanager
>[mailto:listmanager@edn.exln.c
>om]
Sent: Wednesday, December
>10, 2003 7:29 PM
To:
>Recipients of
>'stylus-studio-tech'
>suppressed
Subject: Open a new
>DB to XML data source doc in
>v5.1 173d

From: "Jon Wilmoth"
>

File
>--> New --> DB to XML Data
>Source doesn't do anything.
>How do I create a new DB
>connection?



To reply:
>mailto:stylus-studio-tech.7135
>@edn.exln.com
To start a new
>topic:
>mailto:stylus-studio-tech@edn.
>exln.com
To login:
>http://edn.exln.com/~SSDN

Postnext
Alberto MassariSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Alberto Massari
Date: 11 Dec 2003 08:23 AM
Hi Lance,

At 01.29 11/12/2003 -0500, stylus-studio-tech Listmanager wrote:
>Attn: ivan
>From: "Lance Selock"
>
>Ivan,
>
>I got a little farther than Jon, but not much.
>
>I have a JVM, as indicated by Help About: 1.4.2_02-b03 Java HotSpot(TM)
>Client VM Sun Microsystems Inc. debug mode port:-1
>
>I can even "Select * from Emp" on my Oracle server from the Scott sample
>schema. I get a nice little XML file in the preview window. Very nice.
>
>Unfortunately, using "Connect" to get a schema causes the familiar
>"swinging flashlight" to appear for a while, eventually followed by the
>system returning with no errors or results. Too bad, because this could
>be very neat if it worked.

Can you try opening the Output Window (View | Output)? That should contain
the raw response we got from the database.

Alberto

Postnext
Lance SelockSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Lance Selock
Date: 13 Dec 2003 12:19 AM
Hi ALberto,

When I try to Connect the swinging flashlight appears for several minutes, and eventually I am returned to where everything works normally, but nothing in the output window or the right schema window.

When I select from a specific table the output window says "m_queryOuput = File.createTempFile('sqlx', null);"
and I get a nice preview as expected. Unfortunately, as noted in my first post there is no way to save it. Correction it appears to save, but there is no way to retrieve it.

I attached a files listing all my loaded modules. Perhaps it will give you some clues.

Lance.


On 12/11/03 8:23:12 AM, Alberto Massari wrote:
>Hi Lance,

At 01.29 11/12/2003 -0500,
>stylus-studio-tech Listmanager
>wrote:
>Attn: ivan
>From: "Lance Selock"
>
>
>Ivan,
>
>I got a little farther than
>Jon, but not much.
>
>I have a JVM, as
>indicated by Help About: 1.4.2_02-b03
>Java HotSpot(TM)
>Client VM Sun
>Microsystems Inc. debug mode
>port:-1
>
>I can even "Select * from
>Emp" on my Oracle server from the Scott
>sample
>schema. I get a nice little
>XML file in the preview window. Very
>nice.
>
>Unfortunately, using "Connect"
>to get a schema causes the familiar
>
>"swinging flashlight" to appear for a
>while, eventually followed by the
>
>system returning with no errors or
>results. Too bad, because this could
>
>be very neat if it worked.

Can you
>try opening the Output Window (View |
>Output)? That should contain
the raw
>response we got from the
>database.

Alberto






DocumentModules.htm
List of modfules loaded with Struzzo.exe

Postnext
Ivan PedruzziSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Ivan Pedruzzi
Date: 11 Dec 2003 10:35 AM

Lance,

In the current release stylus asks to the database what schemas are defined then for each schema retrieves the table definitions.

We are discovering that most of time this approach is too restrictive so for the next update stylus will be able browse table
definitions regardless their schema/catalog.

If you want to open the "DB to XML data source" as XML you have to use the XML editor.
Do the follow:

- File -> Open
- Click on "Relational DB"
- select the document
- click on the black arrow on the "open" button and pick "XML Editor"

Thank you
Ivan

-----Original Message-----
From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
Sent: Thursday, December 11, 2003 1:29 AM
To: Recipients of 'stylus-studio-tech' suppressed
Subject: RE: Open a new DB to XML data source doc in v5.1 173d

Attn: ivan
From: "Lance Selock"

Ivan,

I got a little farther than Jon, but not much.

I have a JVM, as indicated by Help About: 1.4.2_02-b03 Java HotSpot(TM) Client VM Sun Microsystems Inc. debug mode port:-1

I can even "Select * from Emp" on my Oracle server from the Scott sample schema. I get a nice little XML file in the preview
window. Very nice.

Unfortunately, using "Connect" to get a schema causes the familiar "swinging flashlight" to appear for a while, eventually followed
by the system returning with no errors or results. Too bad, because this could be very neat if it worked.

I've tried various combinations of going in with/without a SELECT statement first, starting Stylus Studio from scratch every time or
not, etc. Nothing seems to work.

On a related note, if I save the previously mentioned Scott_Emp.rdbxml to my Relational DB it appears to work and appears in the
root as a document when I try to Open, but upon retrieval it's empty. Very strange! You would think if there was some kind of
rights issue, the document wouldn't even appear.

My DBA_Registry reports:
COMP_NAME VERSION
------------------------------ ----------
Oracle9i Catalog Views 9.2.0.1.0
Oracle9i Packages and Types 9.2.0.1.0
Oracle Workspace Manager 9.2.0.1.0
JServer JAVA Virtual Machine 9.2.0.1.0
Oracle XDK for Java 9.2.0.2.0
Oracle9i Java Packages 9.2.0.1.0
Oracle interMedia 9.2.0.1.0
Spatial 9.2.0.1.0
Oracle Text 9.2.0.1.0
Oracle XML Database 9.2.0.1.0
Oracle Ultra Search 9.2.0.1.0
Oracle Data Mining 9.2.0.1.0
OLAP Analytic Workspace 9.2.0.1.0
Oracle OLAP API 9.2.0.1.0
OLAP Catalog 9.2.0.1.0

I'm going up to version 9.2.0.4 on the weekend, so maybe it will work next week.

Any thoughts in the meantime would be appreciated.

Thanks,

Lance.

P.S. Good luck to Jon. This looks like it's gong to be really cool if we can just get it working!





On 12/10/03 8:53:18 PM, Ivan Pedruzzi wrote:
>Hi Jon,

the SQL/XML plug-in
>requires the Java Virtual
>Machine.
Do you have one
>configured
>(tools->options->Application
>Settings->Java Virtual
>Machine)?

Ivan

-----Original
>Message-----
From:
>stylus-studio-tech Listmanager
>[mailto:listmanager@edn.exln.c
>om]
Sent: Wednesday, December
>10, 2003 7:29 PM
To:
>Recipients of
>'stylus-studio-tech'
>suppressed
Subject: Open a new
>DB to XML data source doc in
>v5.1 173d

From: "Jon Wilmoth"
>

File
>--> New --> DB to XML Data
>Source doesn't do anything.
>How do I create a new DB
>connection?



To reply:
>mailto:stylus-studio-tech.7135
>@edn.exln.com
To start a new
>topic:
>mailto:stylus-studio-tech@edn.
>exln.com
To login:
>http://edn.exln.com/~SSDN



To reply: mailto:stylus-studio-tech.7138@edn.exln.com
To start a new topic: mailto:stylus-studio-tech@edn.exln.com
To login: http://edn.exln.com/~SSDN

Postnext
Lance SelockSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Lance Selock
Date: 13 Dec 2003 12:37 AM
Ivan,

If I understand your point correctly, retrieving all the schemas and tables from my database would take a very long time, and perhaps Struzzo just times out. But I assumed that by logging in as Scott/Tiger I would only get Oracle's sample schema for Scott which has only five tables. Scott doesn't even have rights to see any of the other schema so there is no point offering them as choices!

In regards to your second point, as mentioned previously I can retrieve records from Scott.Emp and when I save everything appears to work, but upon retrieval using "XML Editor" all I get is a document that says:

java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.stylusstudio.DataDirectStub.connect(DataDirectStub.java:58)
at com.stylusstudio.DataDirectStub.select(DataDirectStub.java:215)
at com.stylusstudio.SQLXFile.executeQuery(SQLXFile.java:281)
at com.stylusstudio.SQLXFile.executeQuery(SQLXFile.java:261)
at com.stylusstudio.SQLXFile.getInputStream(SQLXFile.java:293)

Where exactly is this stuff being "saved" on my server? I suspect that Scott doesn't have any rights wherever it is, but it's confusing that it appears to work. That could be an Oracle bug in 9.2.0.1. We're moving up to 9.2.0.4 on Sunday morning, so I'll have to try it again after that. Maybe then Scott will be denied access when I try to save.

Lance.


On 12/11/03 10:35:14 AM, Ivan Pedruzzi wrote:

Lance,

In the current release stylus asks to the database what schemas are defined then for each schema retrieves the table definitions.

We are discovering that most of time this approach is too restrictive so for the next update stylus will be able browse table
definitions regardless their schema/catalog.

If you want to open the "DB to XML data source" as XML you have to use the XML editor.
Do the follow:

- File -> Open
- Click on "Relational DB"
- select the document
- click on the black arrow on the "open" button and pick "XML Editor"

Thank you
Ivan



Postnext
Ivan PedruzziSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Ivan Pedruzzi
Date: 13 Dec 2003 12:31 PM
Lance,

Stylus save the connection properties on the local file system (\dbxml), it doesn't try to save anything in the
database.

When you do save (db to xml editor) you are not saving the query result, but the connection properties and the query statements.

When you open an existing "DB to XML data source" document, stylus do not run the query.
You have to click "Execute" to run the query again.

The database schema tree has been already corrected in the internal build and I was able to browse an instance of Oracle 9.1.

From the error you are getting, looks like the connection properties are not saved correctly.
Could you send the files you have under \dbxml?

Thank You for your patience
Ivan


-----Original Message-----
From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
Sent: Saturday, December 13, 2003 1:03 AM
To: Recipients of 'stylus-studio-tech' suppressed
Subject: RE: Open a new DB to XML data source doc in v5.1 173d

From: "Lance Selock"

Ivan,

If I understand your point correctly, retrieving all the schemas and tables from my database would take a very long time, and
perhaps Struzzo just times out. But I assumed that by logging in as Scott/Tiger I would only get Oracle's sample schema for Scott
which has only five tables. Scott doesn't even have rights to see any of the other schema so there is no point offering them as
choices!

In regards to your second point, as mentioned previously I can retrieve records from Scott.Emp and when I save everything appears to
work, but upon retrieval using "XML Editor" all I get is a document that says:

java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.stylusstudio.DataDirectStub.connect(DataDirectStub.java:58)
at com.stylusstudio.DataDirectStub.select(DataDirectStub.java:215)
at com.stylusstudio.SQLXFile.executeQuery(SQLXFile.java:281)
at com.stylusstudio.SQLXFile.executeQuery(SQLXFile.java:261)
at com.stylusstudio.SQLXFile.getInputStream(SQLXFile.java:293)

Where exactly is this stuff being "saved" on my server? I suspect that Scott doesn't have any rights wherever it is, but it's
confusing that it appears to work. That could be an Oracle bug in 9.2.0.1. We're moving up to 9.2.0.4 on Sunday morning, so I'll
have to try it again after that. Maybe then Scott will be denied access when I try to save.

Lance.


On 12/11/03 10:35:14 AM, Ivan Pedruzzi wrote:

Lance,

In the current release stylus asks to the database what schemas are defined then for each schema retrieves the table definitions.

We are discovering that most of time this approach is too restrictive so for the next update stylus will be able browse table
definitions regardless their schema/catalog.

If you want to open the "DB to XML data source" as XML you have to use the XML editor.
Do the follow:

- File -> Open
- Click on "Relational DB"
- select the document
- click on the black arrow on the "open" button and pick "XML Editor"

Thank you
Ivan






To reply: mailto:stylus-studio-tech.7144@edn.exln.com
To start a new topic: mailto:stylus-studio-tech@edn.exln.com
To login: http://edn.exln.com/~SSDN

Postnext
Lance SelockSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Lance Selock
Date: 13 Dec 2003 03:45 PM
Ivan,

The DBXML directory is present, but the files are all zero bytes. Probably not much point in sending you those. I confirmed that I can save and edit files in that directory using Notepad or Struzzo.

Now I'm intrigued. What is the format of a rdbxml file? Could I make one manually and save it to this directory? Is rdbxml some type of public standard about which I should already be aware?

Perhaps you could send me the rdbxml file for "SELECT * FROM EMP" while connected as SCOTT identified by TIGER. Then I could try it here.

Thanks,

Lance.


On 12/13/03 12:31:54 PM, Ivan Pedruzzi wrote:
>Lance,

Stylus save the connection
>properties on the local file system
>(\dbxml), it doesn't try to save
>anything in the
database.

When you do
>save (db to xml editor) you are not
>saving the query result, but the
>connection properties and the query
>statements.

When you open an existing
>"DB to XML data source" document, stylus
>do not run the query.
You have to click
>"Execute" to run the query again.

The
>database schema tree has been already
>corrected in the internal build and I
>was able to browse an instance of Oracle
>9.1.

From the error you are getting,
>looks like the connection properties are
>not saved correctly.
Could you send the
>files you have under \dbxml?

Thank You
>for your patience
Ivan


-----Original
>Message-----
From: stylus-studio-tech
>Listmanager
>[mailto:listmanager@edn.exln.com]
Sent:
>Saturday, December 13, 2003 1:03 AM
To:
>Recipients of 'stylus-studio-tech'
>suppressed
Subject: RE: Open a new DB to
>XML data source doc in v5.1 173d

From:
>"Lance Selock"

Ivan,

If I understand
>your point correctly, retrieving all the
>schemas and tables from my database
>would take a very long time, and
perhaps
>Struzzo just times out. But I assumed
>that by logging in as Scott/Tiger I
>would only get Oracle's sample schema
>for Scott
which has only five tables.
>Scott doesn't even have rights to see
>any of the other schema so there is no
>point offering them as
choices!

In
>regards to your second point, as
>mentioned previously I can retrieve
>records from Scott.Emp and when I save
>everything appears to
work, but upon
>retrieval using "XML Editor" all I get
>is a document that
>says:

java.lang.NullPointerException

>at java.lang.Class.forName0(Native
>Method)
at
>java.lang.Class.forName(Class.java:141)

>at
>com.stylusstudio.DataDirectStub.connect(
>DataDirectStub.java:58)
at
>com.stylusstudio.DataDirectStub.select(D
>ataDirectStub.java:215)
at
>com.stylusstudio.SQLXFile.executeQuery(S
>QLXFile.java:281)
at
>com.stylusstudio.SQLXFile.executeQuery(S
>QLXFile.java:261)
at
>com.stylusstudio.SQLXFile.getInputStream
>(SQLXFile.java:293)

Where exactly is
>this stuff being "saved" on my server?
>I suspect that Scott doesn't have any
>rights wherever it is, but
>it's
confusing that it appears to work.
>That could be an Oracle bug in 9.2.0.1.
>We're moving up to 9.2.0.4 on Sunday
>morning, so I'll
have to try it again
>after that. Maybe then Scott will be
>denied access when I try to
>save.

Lance.


On 12/11/03 10:35:14 AM,
>Ivan Pedruzzi wrote:

Lance,

In the
>current release stylus asks to the
>database what schemas are defined then
>for each schema retrieves the table
>definitions.

We are discovering that
>most of time this approach is too
>restrictive so for the next update
>stylus will be able browse
>table
definitions regardless their
>schema/catalog.

If you want to open the
>"DB to XML data source" as XML you have
>to use the XML editor.
Do the follow:

-
>File -> Open
- Click on "Relational
>DB"
- select the document
- click on the
>black arrow on the "open" button and
>pick "XML Editor"

Thank
>you
Ivan






To reply:
>mailto:stylus-studio-tech.7144@edn.exln.
>com
To start a new topic:
>mailto:stylus-studio-tech@edn.exln.com
T
>o login: http://edn.exln.com/~SSDN




Postnext
Lance SelockSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Lance Selock
Date: 13 Dec 2003 11:28 PM
Ivan,

Thanks for your quick response and the sample rdbxml file.

For those interested, here is the file:
<?xml version="1.0" encoding="UTF-8"?>
<meta-info>
<scenario
JDBC_DRIVER_CLASS="com.ddtek.jdbc.jxtr.JXTRDriver"
JDBC_CONNECTION_URL="jdbc:datadirect:jxtr:oracle://localhost:1521;SID=oracl"
JDBC_CONNECTION_USER="scott"
JDBC_CONNECTION_PASSWORD="tiger"
ROOT_NODE="">
<select>SELECT * FROM EMP</select>
<update/>
</scenario>
</meta-info>

The ROOT_NODE attribute allows me to rename the document root from the default of "root" to whatever I want. Is there equivalent capability for the ROW_NODE? What other attributes are available? Is there any documentation on the rdbxml file format? How could I use these in a stand alone XSL application?

The good news is that I was been able to create rdbxml files that work against Oracle's Scott schema and also against my own giant schema. This allows me to start playing with rdbxml possibilities. Thanks.

When I open an rdbxml file in the XML Editor, everything works as expected and I see an XML representation of my data. The output window contains:
m_queryOuput = File.createTempFile('sqlx', null);
m_queryOuput.delete()

However, if I try to open the same file as DBtoXML, the flashlight swings for a very long time before control is eventually returned to Struzzo, but there is nothing in the Output window and no results, no message box, nothing to indicate what went wrong. This could still be your "Read All Schema" problem. Perhaps when _any_ rdbxml file is opened an attempt is still made to read all the schema. As previously mentioned, that would be a bad idea on my server.

I look forward to seeing the next release soon, as I assume that these problems will be gone. In the meantime I will make my rdbxml files by hand. Now if I can just figure out where they fit into the big picture...

Thanks again,

Lance.



On 12/13/03 3:45:29 PM, Lance Selock wrote:
>Ivan,
>
>The DBXML directory is
>present, but the files are all
>zero bytes. Probably not much
>point in sending you those. I
>confirmed that I can save and
>edit files in that directory
>using Notepad or Struzzo.
>
>Now I'm intrigued. What is
>the format of a rdbxml file?
>Could I make one manually and
>save it to this directory? Is
>rdbxml some type of public
>standard about which I should
>already be aware?
>
>Perhaps you could send me the
>rdbxml file for "SELECT * FROM
>EMP" while connected as SCOTT
>identified by TIGER. Then I
>could try it here.
>
>Thanks,
>
>Lance.
>
>
>On 12/13/03 12:31:54 PM, Ivan Pedruzzi
>wrote:
>>Lance,
>
>Stylus save the connection
>>properties on the local file system
>>(\dbxml), it doesn't try to save
>>anything in the
>database.
>
>When you do
>>save (db to xml editor) you are not
>>saving the query result, but the
>>connection properties and the query
>>statements.
>
>When you open an existing
>>"DB to XML data source" document, stylus
>>do not run the query.
>You have to click
>>"Execute" to run the query again.
>
>The
>>database schema tree has been already
>>corrected in the internal build and I
>>was able to browse an instance of Oracle
>>9.1.
>
>From the error you are getting,
>>looks like the connection properties are
>>not saved correctly.
>Could you send the
>>files you have under \dbxml?
>
>Thank You
>>for your patience
>Ivan
>
>
>-----Original
>>Message-----
>From: stylus-studio-tech
>>Listmanager
>>[mailto:listmanager@edn.exln.com]
>Sent:
>>Saturday, December 13, 2003 1:03 AM
>To:
>>Recipients of 'stylus-studio-tech'
>>suppressed
>Subject: RE: Open a new DB to
>>XML data source doc in v5.1 173d
>
>From:
>>"Lance Selock"
>
>Ivan,
>
>If I understand
>>your point correctly, retrieving all the
>>schemas and tables from my database
>>would take a very long time, and
>perhaps
>>Struzzo just times out. But I assumed
>>that by logging in as Scott/Tiger I
>>would only get Oracle's sample schema
>>for Scott
>which has only five tables.
>>Scott doesn't even have rights to see
>>any of the other schema so there is no
>>point offering them as
>choices!
>
>In
>>regards to your second point, as
>>mentioned previously I can retrieve
>>records from Scott.Emp and when I save
>>everything appears to
>work, but upon
>>retrieval using "XML Editor" all I get
>>is a document that
>>says:
>
>java.lang.NullPointerException
>
>>at java.lang.Class.forName0(Native
>>Method)
> at
>>java.lang.Class.forName(Class.java:141)
>
>>at
>>com.stylusstudio.DataDirectStub.connect(
>>DataDirectStub.java:58)
> at
>>com.stylusstudio.DataDirectStub.select(D
>>ataDirectStub.java:215)
> at
>>com.stylusstudio.SQLXFile.executeQuery(S
>>QLXFile.java:281)
> at
>>com.stylusstudio.SQLXFile.executeQuery(S
>>QLXFile.java:261)
> at
>>com.stylusstudio.SQLXFile.getInputStream
>>(SQLXFile.java:293)
>
>Where exactly is
>>this stuff being "saved" on my server?
>>I suspect that Scott doesn't have any
>>rights wherever it is, but
>>it's
>confusing that it appears to work.
>>That could be an Oracle bug in 9.2.0.1.
>>We're moving up to 9.2.0.4 on Sunday
>>morning, so I'll
>have to try it again
>>after that. Maybe then Scott will be
>>denied access when I try to
>>save.
>
>Lance.
>
>
>On 12/11/03 10:35:14 AM,
>>Ivan Pedruzzi wrote:
>
>Lance,
>
>In the
>>current release stylus asks to the
>>database what schemas are defined then
>>for each schema retrieves the table
>>definitions.
>
>We are discovering that
>>most of time this approach is too
>>restrictive so for the next update
>>stylus will be able browse
>>table
>definitions regardless their
>>schema/catalog.
>
>If you want to open the
>>"DB to XML data source" as XML you have
>>to use the XML editor.
>Do the follow:
>
>-
>>File -> Open
>- Click on "Relational
>>DB"
>- select the document
>- click on the
>>black arrow on the "open" button and
>>pick "XML Editor"
>
>Thank
>>you
>Ivan
>
>
>
>
>
>
>To reply:
>>mailto:stylus-studio-tech.7144@edn.exln.
>>com
>To start a new topic:
>>mailto:stylus-studio-tech@edn.exln.com
>T
>>o login: http://edn.exln.com/~SSDN
>
>
>
>

Postnext
Ivan PedruzziSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Ivan Pedruzzi
Date: 15 Dec 2003 12:31 AM

..rdbxml files have to be created/edited using stylus studio, we strongly advise not to edit/create those files manually. The
document format could hint to features that are not yet supported and using the wrong values could produce unpredictable behaviors.

In this particular case we are investigating a support event so I asked Lance to start from an existing dbtoxml document just to
verify the editor behavior.


Thank You
Ivan Pedruzzi
Stylus Studio Team


-----Original Message-----
From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
Sent: Saturday, December 13, 2003 11:54 PM
To: Recipients of 'stylus-studio-tech' suppressed
Subject: RE: Open a new DB to XML data source doc in v5.1 173d

From: "Lance Selock"

Ivan,

Thanks for your quick response and the sample rdbxml file.

For those interested, here is the file:
<?xml version="1.0" encoding="UTF-8"?>
<meta-info>
<scenario
JDBC_DRIVER_CLASS="com.ddtek.jdbc.jxtr.JXTRDriver"
JDBC_CONNECTION_URL="jdbc:datadirect:jxtr:oracle://localhost:1521;SID=oracl"
JDBC_CONNECTION_USER="scott"
JDBC_CONNECTION_PASSWORD="tiger"
ROOT_NODE="">
<select>SELECT * FROM EMP</select>
<update/>
</scenario>
</meta-info>

The ROOT_NODE attribute allows me to rename the document root from the default of "root" to whatever I want. Is there equivalent
capability for the ROW_NODE? What other attributes are available? Is there any documentation on the rdbxml file format? How could
I use these in a stand alone XSL application?

The good news is that I was been able to create rdbxml files that work against Oracle's Scott schema and also against my own giant
schema. This allows me to start playing with rdbxml possibilities. Thanks.

When I open an rdbxml file in the XML Editor, everything works as expected and I see an XML representation of my data. The output
window contains:
m_queryOuput = File.createTempFile('sqlx', null);
m_queryOuput.delete()

However, if I try to open the same file as DBtoXML, the flashlight swings for a very long time before control is eventually returned
to Struzzo, but there is nothing in the Output window and no results, no message box, nothing to indicate what went wrong. This
could still be your "Read All Schema" problem. Perhaps when _any_ rdbxml file is opened an attempt is still made to read all the
schema. As previously mentioned, that would be a bad idea on my server.

I look forward to seeing the next release soon, as I assume that these problems will be gone. In the meantime I will make my rdbxml
files by hand. Now if I can just figure out where they fit into the big picture...

Thanks again,

Lance.



On 12/13/03 3:45:29 PM, Lance Selock wrote:
>Ivan,
>
>The DBXML directory is
>present, but the files are all
>zero bytes. Probably not much
>point in sending you those. I
>confirmed that I can save and
>edit files in that directory
>using Notepad or Struzzo.
>
>Now I'm intrigued. What is
>the format of a rdbxml file?
>Could I make one manually and
>save it to this directory? Is
>rdbxml some type of public
>standard about which I should
>already be aware?
>
>Perhaps you could send me the
>rdbxml file for "SELECT * FROM
>EMP" while connected as SCOTT
>identified by TIGER. Then I
>could try it here.
>
>Thanks,
>
>Lance.
>
>
>On 12/13/03 12:31:54 PM, Ivan Pedruzzi
>wrote:
>>Lance,
>
>Stylus save the connection
>>properties on the local file system
>>(\dbxml), it doesn't try to save
>>anything in the
>database.
>
>When you do
>>save (db to xml editor) you are not
>>saving the query result, but the
>>connection properties and the query
>>statements.
>
>When you open an existing
>>"DB to XML data source" document, stylus
>>do not run the query.
>You have to click
>>"Execute" to run the query again.
>
>The
>>database schema tree has been already
>>corrected in the internal build and I
>>was able to browse an instance of Oracle
>>9.1.
>
>From the error you are getting,
>>looks like the connection properties are
>>not saved correctly.
>Could you send the
>>files you have under \dbxml?
>
>Thank You
>>for your patience
>Ivan
>
>
>-----Original
>>Message-----
>From: stylus-studio-tech
>>Listmanager
>>[mailto:listmanager@edn.exln.com]
>Sent:
>>Saturday, December 13, 2003 1:03 AM
>To:
>>Recipients of 'stylus-studio-tech'
>>suppressed
>Subject: RE: Open a new DB to
>>XML data source doc in v5.1 173d
>
>From:
>>"Lance Selock"
>
>Ivan,
>
>If I understand
>>your point correctly, retrieving all the
>>schemas and tables from my database
>>would take a very long time, and
>perhaps
>>Struzzo just times out. But I assumed
>>that by logging in as Scott/Tiger I
>>would only get Oracle's sample schema
>>for Scott
>which has only five tables.
>>Scott doesn't even have rights to see
>>any of the other schema so there is no
>>point offering them as
>choices!
>
>In
>>regards to your second point, as
>>mentioned previously I can retrieve
>>records from Scott.Emp and when I save
>>everything appears to
>work, but upon
>>retrieval using "XML Editor" all I get
>>is a document that
>>says:
>
>java.lang.NullPointerException
>
>>at java.lang.Class.forName0(Native
>>Method)
> at
>>java.lang.Class.forName(Class.java:141)
>
>>at
>>com.stylusstudio.DataDirectStub.connect(
>>DataDirectStub.java:58)
> at
>>com.stylusstudio.DataDirectStub.select(D
>>ataDirectStub.java:215)
> at
>>com.stylusstudio.SQLXFile.executeQuery(S
>>QLXFile.java:281)
> at
>>com.stylusstudio.SQLXFile.executeQuery(S
>>QLXFile.java:261)
> at
>>com.stylusstudio.SQLXFile.getInputStream
>>(SQLXFile.java:293)
>
>Where exactly is
>>this stuff being "saved" on my server?
>>I suspect that Scott doesn't have any
>>rights wherever it is, but
>>it's
>confusing that it appears to work.
>>That could be an Oracle bug in 9.2.0.1.
>>We're moving up to 9.2.0.4 on Sunday
>>morning, so I'll
>have to try it again
>>after that. Maybe then Scott will be
>>denied access when I try to
>>save.
>
>Lance.
>
>
>On 12/11/03 10:35:14 AM,
>>Ivan Pedruzzi wrote:
>
>Lance,
>
>In the
>>current release stylus asks to the
>>database what schemas are defined then
>>for each schema retrieves the table
>>definitions.
>
>We are discovering that
>>most of time this approach is too
>>restrictive so for the next update
>>stylus will be able browse
>>table
>definitions regardless their
>>schema/catalog.
>
>If you want to open the
>>"DB to XML data source" as XML you have
>>to use the XML editor.
>Do the follow:
>
>-
>>File -> Open
>- Click on "Relational
>>DB"
>- select the document
>- click on the
>>black arrow on the "open" button and
>>pick "XML Editor"
>
>Thank
>>you
>Ivan
>
>
>
>
>
>
>To reply:
>>mailto:stylus-studio-tech.7144@edn.exln.
>>com
>To start a new topic:
>>mailto:stylus-studio-tech@edn.exln.com
>T
>>o login: http://edn.exln.com/~SSDN
>
>
>
>



To reply: mailto:stylus-studio-tech.7147@edn.exln.com
To start a new topic: mailto:stylus-studio-tech@edn.exln.com
To login: http://edn.exln.com/~SSDN

Postnext
Lance SelockSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Lance Selock
Date: 15 Dec 2003 02:07 AM
Sorry about exposing the file format Ivan, but anyone who does any snooping around probably would have found the rdbxml files soon enough. I for one am quite grateful for the file you sent me, since it allowed me to play with the new feature even though the save isn't working yet. But now that I've mucked with it a bit, I come back to the question: How can I use this in my own applications?

I too would like to know why the save doesn’t work. When I try to save the output window displays:

java.lang.NoSuchFieldError: S_KEY_INDENT_AMOUNT at org.apache.xalan.serialize.SerializerToXML.init(SerializerToXML.java:408) at org.apache.xalan.serialize.SerializerToXML.init(SerializerToXML.java:532) at org.apache.xalan.serialize.SerializerToXML.setOutputStream(SerializerToXML.java:2443) at com.stylusstudio.SQLXFile.setScenario(SQLXFile.java:150)

A file is created in the DBXML directory, but it is zero length. If you don't look at the Output Window, there is no indication that the save failed.

Indeed there is no such field as "S_KEY_INDENT_AMOUNT" in my "Select * from ..." query result, so it must be one of yours.

Lance.

P.S. I notice that when I reply to your private messages to me, your mail server rejects your address:
Recipient address: ipedruzz@progress.com
Reason: Remote SMTP server has rejected address
Diagnostic code: smtp;550 5.7.1 ... Access denied
Remote system: dns;webserv.progress.com (TCP|10.0.120.199|44831|192.77.186.2|25) (webserv.progress.com ESMTP Sendmail 8.12.10/8.12.10/PSC-5.10; Sat, 13 Dec 2003 23:34:18 -0500 [EST])

Get that fixed and we can probably have a private e-mail exchange instead of having to use the board. Also, I notice that often Reply/Quote doesn't work properly. I usually just copy the previous message before hitting the button, because about half the time the previous thread is not quoted into the reply.

As in the example below, only the "On ... wrote:" was supplied. I pasted everything below that.

On 12/15/03 12:31:08 AM, Ivan Pedruzzi wrote:

..rdbxml files have to be created/edited using stylus studio, we strongly advise not to edit/create those files manually. The
document format could hint to features that are not yet supported and using the wrong values could produce unpredictable behaviors.

In this particular case we are investigating a support event so I asked Lance to start from an existing dbtoxml document just to
verify the editor behavior.


Thank You
Ivan Pedruzzi
Stylus Studio Team


-----Original Message-----
From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
Sent: Saturday, December 13, 2003 11:54 PM
To: Recipients of 'stylus-studio-tech' suppressed
Subject: RE: Open a new DB to XML data source doc in v5.1 173d

From: "Lance Selock"

Ivan,

Thanks for your quick response and the sample rdbxml file.

For those interested, here is the file:


JDBC_DRIVER_CLASS="com.ddtek.jdbc.jxtr.JXTRDriver"
JDBC_CONNECTION_URL="jdbc:datadirect:jxtr:oracle://localhost:1521;SID=oracl"
JDBC_CONNECTION_USER="scott"
JDBC_CONNECTION_PASSWORD="tiger"
ROOT_NODE="">





The ROOT_NODE attribute allows me to rename the document root from the default of "root" to whatever I want. Is there equivalent
capability for the ROW_NODE? What other attributes are available? Is there any documentation on the rdbxml file format? How could
I use these in a stand alone XSL application?

The good news is that I was been able to create rdbxml files that work against Oracle's Scott schema and also against my own giant
schema. This allows me to start playing with rdbxml possibilities. Thanks.

When I open an rdbxml file in the XML Editor, everything works as expected and I see an XML representation of my data. The output
window contains:
m_queryOuput = File.createTempFile('sqlx', null);
m_queryOuput.delete()

However, if I try to open the same file as DBtoXML, the flashlight swings for a very long time before control is eventually returned
to Struzzo, but there is nothing in the Output window and no results, no message box, nothing to indicate what went wrong. This
could still be your "Read All Schema" problem. Perhaps when _any_ rdbxml file is opened an attempt is still made to read all the
schema. As previously mentioned, that would be a bad idea on my server.

I look forward to seeing the next release soon, as I assume that these problems will be gone. In the meantime I will make my rdbxml
files by hand. Now if I can just figure out where they fit into the big picture...

Thanks again,

Lance.



On 12/13/03 3:45:29 PM, Lance Selock wrote:
>Ivan,
>
>The DBXML directory is
>present, but the files are all
>zero bytes. Probably not much
>point in sending you those. I
>confirmed that I can save and
>edit files in that directory
>using Notepad or Struzzo.
>
>Now I'm intrigued. What is
>the format of a rdbxml file?
>Could I make one manually and
>save it to this directory? Is
>rdbxml some type of public
>standard about which I should
>already be aware?
>
>Perhaps you could send me the
>rdbxml file for "SELECT * FROM
>EMP" while connected as SCOTT
>identified by TIGER. Then I
>could try it here.
>
>Thanks,
>
>Lance.
>
>
>On 12/13/03 12:31:54 PM, Ivan Pedruzzi
>wrote:
>>Lance,
>
>Stylus save the connection
>>properties on the local file system
>>(\dbxml), it doesn't try to save
>>anything in the
>database.
>
>When you do
>>save (db to xml editor) you are not
>>saving the query result, but the
>>connection properties and the query
>>statements.
>
>When you open an existing
>>"DB to XML data source" document, stylus
>>do not run the query.
>You have to click
>>"Execute" to run the query again.
>
>The
>>database schema tree has been already
>>corrected in the internal build and I
>>was able to browse an instance of Oracle
>>9.1.
>
>From the error you are getting,
>>looks like the connection properties are
>>not saved correctly.
>Could you send the
>>files you have under \dbxml?
>
>Thank You
>>for your patience
>Ivan
>
>
>-----Original
>>Message-----
>From: stylus-studio-tech
>>Listmanager
>>[mailto:listmanager@edn.exln.com]
>Sent:
>>Saturday, December 13, 2003 1:03 AM
>To:
>>Recipients of 'stylus-studio-tech'
>>suppressed
>Subject: RE: Open a new DB to
>>XML data source doc in v5.1 173d
>
>From:
>>"Lance Selock"
>
>Ivan,
>
>If I understand
>>your point correctly, retrieving all the
>>schemas and tables from my database
>>would take a very long time, and
>perhaps
>>Struzzo just times out. But I assumed
>>that by logging in as Scott/Tiger I
>>would only get Oracle's sample schema
>>for Scott
>which has only five tables.
>>Scott doesn't even have rights to see
>>any of the other schema so there is no
>>point offering them as
>choices!
>
>In
>>regards to your second point, as
>>mentioned previously I can retrieve
>>records from Scott.Emp and when I save
>>everything appears to
>work, but upon
>>retrieval using "XML Editor" all I get
>>is a document that
>>says:
>
>java.lang.NullPointerException
>
>>at java.lang.Class.forName0(Native
>>Method)
> at
>>java.lang.Class.forName(Class.java:141)
>
>>at
>>com.stylusstudio.DataDirectStub.connect(
>>DataDirectStub.java:58)
> at
>>com.stylusstudio.DataDirectStub.select(D
>>ataDirectStub.java:215)
> at
>>com.stylusstudio.SQLXFile.executeQuery(S
>>QLXFile.java:281)
> at
>>com.stylusstudio.SQLXFile.executeQuery(S
>>QLXFile.java:261)
> at
>>com.stylusstudio.SQLXFile.getInputStream
>>(SQLXFile.java:293)
>
>Where exactly is
>>this stuff being "saved" on my server?
>>I suspect that Scott doesn't have any
>>rights wherever it is, but
>>it's
>confusing that it appears to work.
>>That could be an Oracle bug in 9.2.0.1.
>>We're moving up to 9.2.0.4 on Sunday
>>morning, so I'll
>have to try it again
>>after that. Maybe then Scott will be
>>denied access when I try to
>>save.
>
>Lance.
>
>
>On 12/11/03 10:35:14 AM,
>>Ivan Pedruzzi wrote:
>
>Lance,
>
>In the
>>current release stylus asks to the
>>database what schemas are defined then
>>for each schema retrieves the table
>>definitions.
>
>We are discovering that
>>most of time this approach is too
>>restrictive so for the next update
>>stylus will be able browse
>>table
>definitions regardless their
>>schema/catalog.
>
>If you want to open the
>>"DB to XML data source" as XML you have
>>to use the XML editor.
>Do the follow:
>
>-
>>File -> Open
>- Click on "Relational
>>DB"
>- select the document
>- click on the
>>black arrow on the "open" button and
>>pick "XML Editor"
>
>Thank
>>you
>Ivan
>
>
>
>
>
>
>To reply:
>>mailto:stylus-studio-tech.7144@edn.exln.
>>com
>To start a new topic:
>>mailto:stylus-studio-tech@edn.exln.com
>T
>>o login: http://edn.exln.com/~SSDN
>
>
>
>



Postnext
Ivan PedruzziSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Ivan Pedruzzi
Date: 15 Dec 2003 02:09 PM


> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
> Sent: Monday, December 15, 2003 2:32 AM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: RE: Open a new DB to XML data source doc in v5.1 173d
>
> How can I use this in my own applications?


Stylus Studio makes use of "Connect for SQL/XML 2.0" from Data Direct Technologies.
You can read more here [1].

[1]http://www.datadirect.com/products/connectsqlxml/csqlxml_index.asp

For future versions we are thinking to a more integrate deployment solution, stay tune.


>
> I too would like to know why the save doesn't work. When I try to save the output window displays:
>
> java.lang.NoSuchFieldError: S_KEY_INDENT_AMOUNT at
> org.apache.xalan.serialize.SerializerToXML.init(SerializerToXML.java:408) at
> org.apache.xalan.serialize.SerializerToXML.init(SerializerToXML.java:532) at
> org.apache.xalan.serialize.SerializerToXML.setOutputStream(SerializerToXML.java:2443) at
> com.stylusstudio.SQLXFile.setScenario(SQLXFile.java:150)


Excellent!!!
Looks like a xalan version mismatch, Stylus is picking the wrong version from somewhere.

You mentioned that you are running JVM 1.4.2_02-b03, correct?

Do you have the xalan jar(s) under \Java\j2re1.4.2_03\lib\ext?
If you do, move them in a subdirectory, and re-start stylus.


> P.S. I notice that when I reply to your private messages to me, your mail server rejects your
> address:
> Recipient address: ipedruzz@progress.com
> Reason: Remote SMTP server has rejected address
> Diagnostic code: smtp;550 5.7.1 ... Access denied
> Remote system: dns;webserv.progress.com (TCP|10.0.120.199|44831|192.77.186.2|25)
> (webserv.progress.com ESMTP Sendmail 8.12.10/8.12.10/PSC-5.10; Sat, 13 Dec 2003 23:34:18 -0500 [EST])

Sounds strange, I received several emails during the weekend.
It could be a temporary problem on our side. If the problem persists you should double check with your IT department.

Ivan

Postnext
Lance SelockSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Lance Selock
Date: 17 Dec 2003 11:27 PM
Hi Ivan,

Thanks for the Data Direct link.

You're right about Xalan. I'm using v2.5.2, but you ship v2.4.1 with your product. When I substitute in v2.4.1, the save routine works as expected.

I still have the same problem on open with it going away for a long time, but I think we've already identified that as the schema loading problem.

I look forward to the next release which will hopefully support the current version of Xalan, and more importantly have the schema loading scaled back to just load the schema to which a user has appropriate rights. But even my smallest schema has 1200 tables, so it remains to be seen if even that is too many.

Thanks for all your help.

Lance.



On 12/15/03 2:09:17 PM, Ivan Pedruzzi wrote:
>

> -----Original
>Message-----
> From:
>stylus-studio-tech Listmanager
>[mailto:listmanager@edn.exln.c
>om]
> Sent: Monday, December
>15, 2003 2:32 AM
> To:
>Recipients of
>'stylus-studio-tech'
>suppressed
> Subject: RE: Open
>a new DB to XML data source
>doc in v5.1 173d
>
> How can
>I use this in my own
>applications?


Stylus Studio
>makes use of "Connect for
>SQL/XML 2.0" from Data Direct
>Technologies.
You can read
>more here
>[1].

[1]http://www.datadirect
>.com/products/connectsqlxml/cs
>qlxml_index.asp

For future
>versions we are thinking to a
>more integrate deployment
>solution, stay tune.


>
> I
>too would like to know why the
>save doesn't work. When I try
>to save the output window
>displays:
>
>
>java.lang.NoSuchFieldError:
>S_KEY_INDENT_AMOUNT at
>
>org.apache.xalan.serialize.Ser
>ializerToXML.init(SerializerTo
>XML.java:408) at
>
>org.apache.xalan.serialize.Ser
>ializerToXML.init(SerializerTo
>XML.java:532) at
>
>org.apache.xalan.serialize.Ser
>ializerToXML.setOutputStream(S
>erializerToXML.java:2443)
>at
>
>com.stylusstudio.SQLXFile.setS
>cenario(SQLXFile.java:150)


E
>xcellent!!!
Looks like a xalan
>version mismatch, Stylus is
>picking the wrong version from
>somewhere.

You mentioned that
>you are running JVM
>1.4.2_02-b03, correct?

Do you
>have the xalan jar(s) under
>\Java\j2re1.4.2_03\lib\ext?
If
>you do, move them in a
>subdirectory, and re-start
>stylus.


> P.S. I notice that
>when I reply to your private
>messages to me, your mail
>server rejects your
>
>address:
> Recipient
>address:
>ipedruzz@progress.com
>
>Reason: Remote SMTP server has
>rejected address
>
>Diagnostic code: smtp;550
>5.7.1 ... Access denied
>
>Remote system:
>dns;webserv.progress.com
>(TCP|10.0.120.199|44831|192.77
>.186.2|25)
>
>(webserv.progress.com ESMTP
>Sendmail
>8.12.10/8.12.10/PSC-5.10; Sat,
>13 Dec 2003 23:34:18 -0500
>[EST])

Sounds strange, I
>received several emails during
>the weekend.
It could be a
>temporary problem on our side.
>If the problem persists you
>should double check with your
>IT department.

Ivan




Postnext
Lance SelockSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Lance Selock
Date: 23 Dec 2003 01:06 AM
Hi Ivan,

Thanks for the link. A few observations:

As before I can build a new rdbxml file and as long as I don't attempt to connect to the schema, everything works fine.

However, if I touch that Connect button Struzzo attempts to download ALL the schema from my database, but this time after a VERY long wait it actually succeeds. Of course, the SCOTT user doesn't have rights to read from most of those tables, but he can build a query.

This presents a serious obstacle since Struzzo insists upon performing this ridiculous search whenever I try to open any rdbxml file. Pushing the stop button cancels the schema loading, but them pushing run causes it to start again. This effectively means that once a rdbxml has been created and saved it's results can be opened in the XML Editor, but it can never be changed. It's OK for me because I'm willing to create them from scratch in the raw format, but I can't imagine that most users will find this acceptable.

You might want to look at the way the XMLSpy folks handle the schema problem. They start by presenting a list of Schema Owners. Picking one or more from the owners list reveals the tables within each owner's schema. It makes for a fast interface and still provides the flexibility to pick from multiple schema.

As predicted the save stills fails under Xalan v2.5.2, but works with the older 2.4.1 version. You need to get that working.

I'll let you know if I come across anything else.

Happy Holidays
Lance.

P.S. Your mail is still broken:

Your message cannot be delivered to the following recipients:

Recipient address: ipedruzz@progress.com
Reason: Remote SMTP server has rejected address
Diagnostic code: smtp;550 5.7.1 ... Access denied
Remote system: dns;webserv.progress.com (TCP|10.0.120.96|17407|192.77.186.2|25) (webserv.progress.com ESMTP Sendmail 8.12.10/8.12.10/PSC-5.10; Mon, 22 Dec 2003 23:38:40 -0500 [EST])




On 12/17/03 11:27:54 PM, Lance Selock wrote:
>Hi Ivan,
>
>Thanks for the Data Direct
>link.
>
>You're right about Xalan. I'm
>using v2.5.2, but you ship
>v2.4.1 with your product.
>When I substitute in v2.4.1,
>the save routine works as
>expected.
>
>I still have the same problem
>on open with it going away for
>a long time, but I think we've
>already identified that as the
>schema loading problem.
>
>I look forward to the next
>release which will hopefully
>support the current version of
>Xalan, and more importantly
>have the schema loading scaled
>back to just load the schema
>to which a user has
>appropriate rights. But even
>my smallest schema has 1200
>tables, so it remains to be
>seen if even that is too many.
>
>Thanks for all your help.
>
>Lance.
>
>
>
>On 12/15/03 2:09:17 PM, Ivan Pedruzzi
>wrote:
>>
>
>> -----Original
>>Message-----
>> From:
>>stylus-studio-tech Listmanager
>>[mailto:listmanager@edn.exln.c
>>om]
>> Sent: Monday, December
>>15, 2003 2:32 AM
>> To:
>>Recipients of
>>'stylus-studio-tech'
>>suppressed
>> Subject: RE: Open
>>a new DB to XML data source
>>doc in v5.1 173d
>>
>> How can
>>I use this in my own
>>applications?
>
>
>Stylus Studio
>>makes use of "Connect for
>>SQL/XML 2.0" from Data Direct
>>Technologies.
>You can read
>>more here
>>[1].
>
>[1]http://www.datadirect
>>.com/products/connectsqlxml/cs
>>qlxml_index.asp
>
>For future
>>versions we are thinking to a
>>more integrate deployment
>>solution, stay tune.
>
>
>>
>> I
>>too would like to know why the
>>save doesn't work. When I try
>>to save the output window
>>displays:
>>
>>
>>java.lang.NoSuchFieldError:
>>S_KEY_INDENT_AMOUNT at
>>
>>org.apache.xalan.serialize.Ser
>>ializerToXML.init(SerializerTo
>>XML.java:408) at
>>
>>org.apache.xalan.serialize.Ser
>>ializerToXML.init(SerializerTo
>>XML.java:532) at
>>
>>org.apache.xalan.serialize.Ser
>>ializerToXML.setOutputStream(S
>>erializerToXML.java:2443)
>>at
>>
>>com.stylusstudio.SQLXFile.setS
>>cenario(SQLXFile.java:150)
>
>
>E
>>xcellent!!!
>Looks like a xalan
>>version mismatch, Stylus is
>>picking the wrong version from
>>somewhere.
>
>You mentioned that
>>you are running JVM
>>1.4.2_02-b03, correct?
>
>Do you
>>have the xalan jar(s) under
>>\Java\j2re1.4.2_03\lib\ext?
>If
>>you do, move them in a
>>subdirectory, and re-start
>>stylus.
>
>
>> P.S. I notice that
>>when I reply to your private
>>messages to me, your mail
>>server rejects your
>>
>>address:
>> Recipient
>>address:
>>ipedruzz@progress.com
>>
>>Reason: Remote SMTP server has
>>rejected address
>>
>>Diagnostic code: smtp;550
>>5.7.1 ... Access denied
>>
>>Remote system:
>>dns;webserv.progress.com
>>(TCP|10.0.120.199|44831|192.77
>>.186.2|25)
>>
>>(webserv.progress.com ESMTP
>>Sendmail
>>8.12.10/8.12.10/PSC-5.10; Sat,
>>13 Dec 2003 23:34:18 -0500
>>[EST])
>
>Sounds strange, I
>>received several emails during
>>the weekend.
>It could be a
>>temporary problem on our side.
>>If the problem persists you
>>should double check with your
>>IT department.
>
>Ivan
>
>
>
>



Postnext
Ivan PedruzziSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Ivan Pedruzzi
Date: 23 Dec 2003 02:03 AM


> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
> Sent: Tuesday, December 23, 2003 1:32 AM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: RE: Open a new DB to XML data source doc in v5.1 173d
>
> Attn: ivan
> From: "Lance Selock"
>
> Hi Ivan,
>
> Thanks for the link. A few observations:
>
> As before I can build a new rdbxml file and as long as I don't attempt to connect to the schema,
> everything works fine.
>
> However, if I touch that Connect button Struzzo attempts to download ALL the schema from my database,
> but this time after a VERY long wait it actually succeeds. Of course, the SCOTT user doesn't have
> rights to read from most of those tables, but he can build a query.
>

What do you mean by VERY long time 30 sec, 30 min, 30 hours?


> This presents a serious obstacle since Struzzo insists upon performing this ridiculous search
> whenever I try to open any rdbxml file. Pushing the stop button cancels the schema loading, but them
> pushing run causes it to start again. This effectively means that once a rdbxml has been created

The "Execute" command does not fetch the schema, it only runs the query.

> and
> saved it's results can be opened in the XML Editor, but it can never be changed. It's OK for me
> because I'm willing to create them from scratch in the raw format, but I can't imagine that most
> users will find this acceptable.

I am not sure I understand what you mean by "it can never be changed"; when you open a .rdbxml file, you can stop the schema
fetching at any time, then you can edit the connection properties or the query and save it.



> As predicted the save stills fails under Xalan v2.5.2, but works with the older 2.4.1 version. You
> need to get that working.

We are working on this one.

Ivan

Postnext
Lance SelockSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Lance Selock
Date: 23 Dec 2003 04:41 PM
Hi Ivan,

A VERY long time in this case was more than thirty minutes, but less than three hours. I wandered away for a while and when I returned the schema for the entire database was in the right pane. This is a significant improvement. In the past it would run for a long time, but eventually would just give up, returning nothing. Unfortunately, because Struzzo returns the schema for all owners, the schema tool is effectively useless for complex databases.

Fortunately, the Execute button saves the day since it doesn't require the schema for a NEW rdbxml file. However, if I open an existing rdbxml file, an immediate attempt is made to retrieve the schema. Pushing stop cancels that, but if I change the query and try to execute it, the schema loading starts again. At least I think that is what it is doing. The swinging flashlight doesn't appear, but the progress bar runs at the bottom. Pushing stop cancels it.

If I don't try to execute the changed query, but instead immediately do a Save As, the system appears to hang before the dialog box even comes up. Once again I suspect that it is trying to retrieve the schema, but this time there is no progress bar or flashlight and worst of all the stop button is grayed out. I have to kill the process to regain control.

Even if the stop button were available, I don't think that it always really stops things, because attempting to close a rdbxml file that has been "stopped" often hangs Struzzo.

In all cases, I have never waited for it to actually finish any of these modified file scenarios. My patience ran out at 105 minutes. The only time that I've seen a schema was the one time that I created a rdbxml from scratch, hit connect, and waited the above mentioned VERY long time.

Hope this helps you to get the Data Direct stuff going.

However, as an Oracle 9iR2 user I would prefer an approach that takes advantage of Oracle's native XML support. The Data Direct approach is similar enough to be useful, but not identical. The Oracle XMLDB API is very powerful and exposes some key functionality that would benefit from a nice user interface such as Struzzo offers. I'm think in particular about the ability to have Oracle apply an XSLT style sheet before returning the results, or even failing that the ability to rename the row and root elements. Also there's a neat little feature where Oracle will automatically generate an ID attribute for each row.

It might be interesting for you to survey your clients and see how many would prefer native tools over generic tools such as provided by Data Direct. I think if you focused your efforts on the native API's you would have more control of your product and a much better tool in the long run. Obviously, that's easy for me to say since I use Oracle which is the market leader. Users of other databases that aren't as far along benefit greatly from the Data Direct approach.


Happy Holidays
Lance.

P.S. Still can't get through your e-mail server:

Reporting-MTA: dns;l-daemon (shaw_internet-daemon)

Original-recipient: rfc822;ipedruzz@progress.com
Final-recipient: rfc822;ipedruzz@progress.com
Action: failed
Status: 5.7.1 (Remote SMTP server has rejected address)
Remote-MTA: dns;pscgate.progress.com (TCP|10.0.120.198|50008|192.77.186.1|25)
(pscgate.progress.com ESMTP Sendmail 8.12.10/8.12.10/PSC-5.10; Tue, 23 Dec
2003 16:15:44 -0500 [EST])
Diagnostic-code: smtp;550 5.7.1 ... Access denied


On 12/23/03 2:03:54 AM, Ivan Pedruzzi wrote:
>

> -----Original
>Message-----
> From:
>stylus-studio-tech Listmanager
>[mailto:listmanager@edn.exln.c
>om]
> Sent: Tuesday, December
>23, 2003 1:32 AM
> To:
>Recipients of
>'stylus-studio-tech'
>suppressed
> Subject: RE: Open
>a new DB to XML data source
>doc in v5.1 173d
>
> Attn:
>ivan
> From: "Lance Selock"
>
>
> Hi Ivan,
>
> Thanks for
>the link. A few
>observations:
>
> As before I
>can build a new rdbxml file
>and as long as I don't attempt
>to connect to the schema,
>
>everything works fine.
>
>
>However, if I touch that
>Connect button Struzzo
>attempts to download ALL the
>schema from my database,
> but
>this time after a VERY long
>wait it actually succeeds. Of
>course, the SCOTT user doesn't
>have
> rights to read from
>most of those tables, but he
>can build a query.
>

What do
>you mean by VERY long time 30
>sec, 30 min, 30 hours?


>
>This presents a serious
>obstacle since Struzzo insists
>upon performing this
>ridiculous search
> whenever I
>try to open any rdbxml file.
>Pushing the stop button
>cancels the schema loading,
>but them
> pushing run causes
>it to start again. This
>effectively means that once a
>rdbxml has been created

The
>"Execute" command does not
>fetch the schema, it only runs
>the query.

> and
> saved it's
>results can be opened in the
>XML Editor, but it can never
>be changed. It's OK for me
>
>because I'm willing to create
>them from scratch in the raw
>format, but I can't imagine
>that most
> users will find
>this acceptable.

I am not
>sure I understand what you
>mean by "it can never be
>changed"; when you open a
>.rdbxml file, you can stop the
>schema
fetching at any time,
>then you can edit the
>connection properties or the
>query and save it.



> As
>predicted the save stills
>fails under Xalan v2.5.2, but
>works with the older 2.4.1
>version. You
> need to get
>that working.

We are working
>on this one.

Ivan

Posttop
Ivan PedruzziSubject: RE: Open a new DB to XML data source doc in v5.1 173d
Author: Ivan Pedruzzi
Date: 23 Dec 2003 06:04 PM


> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
> Sent: Tuesday, December 23, 2003 5:06 PM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: RE: Open a new DB to XML data source doc in v5.1 173d
>
> Attn: ivan
> From: "Lance Selock"
>
> Hi Ivan,
>
> A VERY long time in this case was more than thirty minutes, but less than three hours. I wandered
> away for a while and when I returned the schema for the entire database was in the right pane. This
> is a significant improvement. In the past it would run for a long time, but eventually would just
> give up, returning nothing. Unfortunately, because Struzzo returns the schema for all owners, the
> schema tool is effectively useless for complex databases.
>
> Fortunately, the Execute button saves the day since it doesn't require the schema for a NEW rdbxml
> file. However, if I open an existing rdbxml file, an immediate attempt is made to retrieve the
> schema. Pushing stop cancels that, but if I change the query and try to execute it, the schema
> loading starts again. At least I think that is what it is doing. The swinging flashlight doesn't
> appear, but the progress bar runs at the bottom. Pushing stop cancels it.
>
> If I don't try to execute the changed query, but instead immediately do a Save As, the system appears
> to hang before the dialog box even comes up. Once again I suspect that it is trying to retrieve the
> schema, but this time there is no progress bar or flashlight and worst of all the stop button is
> grayed out. I have to kill the process to regain control.
>
> Even if the stop button were available, I don't think that it always really stops things, because
> attempting to close a rdbxml file that has been "stopped" often hangs Struzzo.
>
> In all cases, I have never waited for it to actually finish any of these modified file scenarios. My
> patience ran out at 105 minutes. The only time that I've seen a schema was the one time that I
> created a rdbxml from scratch, hit connect, and waited the above mentioned VERY long time.
>
> Hope this helps you to get the Data Direct stuff going.


Thank You for the feedbacks, we will work to improve performance and responsiveness



>
> However, as an Oracle 9iR2 user I would prefer an approach that takes advantage of Oracle's native
> XML support. The Data Direct approach is similar enough to be useful, but not identical. The Oracle
> XMLDB API is very powerful and exposes some key functionality that would benefit from a nice user
> interface such as Struzzo offers. I'm think in particular about the ability to have Oracle apply an
> XSLT style sheet before returning the results, or even failing that the ability to rename the row and
> root elements. Also there's a neat little feature where Oracle will automatically generate an ID
> attribute for each row.


I think you are missing the fact that you can issue a query using SQL/XML syntax.
This means that you can define any XML structure, here is an example


SELECT
XMLELEMENT(name "employee",
XMLATTRIBUTES(t.EMPNO as " EMPNO "),
XMLELEMENT(name "ENAME",t.ENAME),
XMLELEMENT(name "JOB",t.JOB),
XMLELEMENT(name "MGR",t.MGR),
XMLELEMENT(name "HIREDATE",t.HIREDATE),
XMLELEMENT(name "SAL",t.SAL),
XMLELEMENT(name "COMM",t.COMM),
XMLELEMENT(name "DEPTNO",t.DEPTNO)
)
FROM SCOTT.EMP t

The above query generates



SMITH
CLERK
7902
1980-12-17 00:00:00.0
800

20

....


>
> Happy Holidays
> Lance.

Mary Christmas

Ivan Pedruzzi
Stylus Studio Team

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.