You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Dave Carlson <dc...@ontogenics.com> on 2001/08/01 23:09:19 UTC

updated SQL scripts for Postgres

There were numerous errors in the current turbine-postgres.sql script,
including a significant discrepancy with the current schema definitions used
in other scripts for mysql and hypersonic.  I have fixed these.

The attached script works successfully with PostgreSQL 7.1.2 and the current
cvs of Jetspeed.  As part of this testing, I was getting an error when running
the populate-postgres script.  Postgres could not parse the blob object data
included for turbine_user.  In the attached populate script I replaced the
binary data with NULL, and this works fine.

How is turbine_user.objectdata used by Jetspeed?  What should be contained in
the populate script for this field?

Cheers,
  Dave Carlson
  Ontogenics Corp.
  Boulder, Colorado
  http://XMLmodeling.com


Re: UML models of psml and xreg

Posted by Frans Thamura <ft...@yahoo.com>.
Thanks.. for the UML... I used it for my dev..

Frans


--- Dave Carlson <dc...@ontogenics.com> wrote:
> I'm building a set of tools for generating and
> reverse-engineering XML Schemas
> from/to UML.  I attached two GIF diagrams of the
> current psml.xsd from CVS, as
> well as the xreg.xsd that was posted by Frans
> Thamura on 7/26.  These UML
> diagrams were produced by Rational Rose, but the
> model structure was
> automatically generated from the XSD source.  I only
> rearranged the diagrams
> to make them more readable.  I can also generate
> complete schemas from the
> same models.
> 
> If there is interest on this list, I'll explain the
> process in more detail.
> But I thought the diagrams would be of interest.  I
> find that it is much
> easier to understand the concepts and relationships
> via a diagram.
> 
> As part of this, I discovered a few technical errors
> in the schemas.  Both
> schemas use the XSD <all> content model incorrectly.
>  I really wish that it
> did work like this!   However, an <all> group cannot
> directly contain any
> elements that have cardinality other than 1..1 or
> 0..1.  Both schemas contain
> one or more <all> groups with elements having
> maxOccurs=unbounded, which is
> not allowed.
> 
> Unfortunately, this means that we must use either
> <sequence> or <choice
> minOccurs="0" maxOccurs="unbounded"> instead of
> <all> for these complexTypes.
> If you want to validate the cardinality of child
> elements, we must use
> <sequence>.  Or, we use <choice> and basically punt
> on the strictness of
> validation.  I have not looked at Caster, but how
> does it handle these
> alternatives?
> 
> In addition, the psml.xsd schema must declare a
> namespace prefix for the
> targetNamespace.  Or, the XMLSchema namespace must
> use a prefix and allow the
> psml targetNamespace to use the default namespace. 
> I've added the xsd: prefix
> to schema elements and will test the schema before
> posting it back to the
> list.
> 
> Any preferences for how to handle the <all> problem?
> 
> As an aside, I'm working on a major upgrade to my
> http://XMLmodeling.com
> portal.  It's currently running a very old 1.2 beta
> version of Jetspeed.  I
> plan to update to the current version with user
> logins and customization.  I
> also plan to make some of my UML to XSD conversion
> tools available as a web
> application within this portal. So, you'll see more
> messages from me as I try
> to figure out the templating system and
> modifications to the turbine_user
> database table...
> 
> Cheers,
>   Dave Carlson
> 

> ATTACHMENT part 2 image/gif name=xreg.gif


> ATTACHMENT part 3 image/gif name=psml.gif
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
jetspeed-dev-help@jakarta.apache.org


=====
Let's Empowering Open Source

__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


UML models of psml and xreg

Posted by Dave Carlson <dc...@ontogenics.com>.
I'm building a set of tools for generating and reverse-engineering XML Schemas
from/to UML.  I attached two GIF diagrams of the current psml.xsd from CVS, as
well as the xreg.xsd that was posted by Frans Thamura on 7/26.  These UML
diagrams were produced by Rational Rose, but the model structure was
automatically generated from the XSD source.  I only rearranged the diagrams
to make them more readable.  I can also generate complete schemas from the
same models.

If there is interest on this list, I'll explain the process in more detail.
But I thought the diagrams would be of interest.  I find that it is much
easier to understand the concepts and relationships via a diagram.

As part of this, I discovered a few technical errors in the schemas.  Both
schemas use the XSD <all> content model incorrectly.  I really wish that it
did work like this!   However, an <all> group cannot directly contain any
elements that have cardinality other than 1..1 or 0..1.  Both schemas contain
one or more <all> groups with elements having maxOccurs=unbounded, which is
not allowed.

Unfortunately, this means that we must use either <sequence> or <choice
minOccurs="0" maxOccurs="unbounded"> instead of <all> for these complexTypes.
If you want to validate the cardinality of child elements, we must use
<sequence>.  Or, we use <choice> and basically punt on the strictness of
validation.  I have not looked at Caster, but how does it handle these
alternatives?

In addition, the psml.xsd schema must declare a namespace prefix for the
targetNamespace.  Or, the XMLSchema namespace must use a prefix and allow the
psml targetNamespace to use the default namespace.  I've added the xsd: prefix
to schema elements and will test the schema before posting it back to the
list.

Any preferences for how to handle the <all> problem?

As an aside, I'm working on a major upgrade to my http://XMLmodeling.com
portal.  It's currently running a very old 1.2 beta version of Jetspeed.  I
plan to update to the current version with user logins and customization.  I
also plan to make some of my UML to XSD conversion tools available as a web
application within this portal. So, you'll see more messages from me as I try
to figure out the templating system and modifications to the turbine_user
database table...

Cheers,
  Dave Carlson

RE: updated SQL scripts for Postgres

Posted by David Sean Taylor <da...@bluesunrise.com>.
Thanks. Its now checked in to cvs.

-------------------------------------
David Sean Taylor
taylor@apache.org
-------------------------------------
http://jakarta.apache.org/jetspeed
-------------------------------------
 

 

> -----Original Message-----
> From: Dave Carlson [mailto:dcarlson@ontogenics.com]
> Sent: Wednesday, August 01, 2001 2:09 PM
> To: jetspeed-dev@jakarta.apache.org
> Subject: updated SQL scripts for Postgres
> 
> 
> There were numerous errors in the current turbine-postgres.sql script,
> including a significant discrepancy with the current schema 
> definitions used
> in other scripts for mysql and hypersonic.  I have fixed these.
> 
> The attached script works successfully with PostgreSQL 7.1.2 
> and the current
> cvs of Jetspeed.  As part of this testing, I was getting an 
> error when running
> the populate-postgres script.  Postgres could not parse the 
> blob object data
> included for turbine_user.  In the attached populate script I 
> replaced the
> binary data with NULL, and this works fine.
> 
> How is turbine_user.objectdata used by Jetspeed?  What should 
> be contained in
> the populate script for this field?
> 
> Cheers,
>   Dave Carlson
>   Ontogenics Corp.
>   Boulder, Colorado
>   http://XMLmodeling.com
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org