Re: xsd files only: enough to start writing app. code of a DB-related component ?

"Spendius" <spendius@xxxxxxxxxxxxx> wrote in message
news:065af3b0-bb1a-454a-808c-0a4324433a90@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
I've recently started a new project where I've been hired as a
junior Java programmer (know Java but this is a J2EE project
involving Hibernate, Web Services and a few other stuffs). In
fact to start writing code (we use IBM RAD) of our component
me and another guy have only been given a series of .xsd files,
and THAT'S ALL.

These schema definition files aren't very numerous (about 20
or 25 .xsd), but the entities described therein are pretty
complex (many many attributes, complex types, dependencies
etc.). Our component is that which is supposed to deal with
databases connections in this app.

My question: is it usual to proceed this way and provide a
programmer only a few xml schema definitions to have him
starting to code the application ?

It's more common than one would like. I've had to work with less...on one
job we had to code up a DAO to communicate with an EIS (this was early days,
before J2EE connectors were supported), and we had to use JDBC to tackle the
EIS database directly, and the database we were interested in was ISAM, and
the client gave us rather cryptic format files for the tables...well, let's
not elaborate. :-)

If they are good XSD files consider yourselves lucky. I've done plenty of
projects where between one's superiors and the clients, it was like pulling
teeth to get enough information about file formats, database structure or
interfaces to actually do one's job. And if you actually ever get
documentation about anything consider yourself lucky.

I have to admit I suffer quite
a lot with this bizness (I'm a newbie to xml too more or less).
Could you give hints of tools (preferably freeware) to install
(plugins to Eclipse... whatever) to find a track from which I
could manage to start developping something ? Draw a database
schema too (the tables, how many, their structure...): is there
a tool to map xsd's to schema tables without too much hassle ?

Here's the thing. Nobody in his/her right mind coded up those XSD files by
hand. They were dumped from an existing database with a tool. Where such a
tool exists there's a good chance that there exists a tool to generate a
database schema from an XML schema. Just find out (from the schema or from a
boss) what that target database is, and then look for a tool. For example,
XSD2DB apparently works pretty good for SQL Server, at least as of a few
years ago. If your boss(es) is/are willing to crank out some cash, Altova
XMLSpy should be able to do what you want for a number of RDBMS's.

As a fallback it probably won't hurt to understand something about XML
schemas. Try http://www.w3schools.com/Schema/default.asp

AHS


.

Relevant Pages

  • Schema from xsd to sql ce
    ... I have a bunch of xsd files I _have_ imported into a dataset. ... create a sql ce database with the same schema. ... Should I use DataAdapters and Updatethe schema to the database? ...
    (microsoft.public.sqlserver.ce)
  • transform db lookup table to xml schema
    ... I'm creating a xml schema for my existing database. ... for any change in the lookup values, I'd have to change the schema, ...
    (comp.lang.java.programmer)
  • Re: Java is becoming the new Cobol
    ... In the Unisys 2200 environment using their Network Database Server, you get a schema work area depending on how you invoke the schema. ... However, it not only copies the schema area into the program, but the "DMCA" (Database Management Communication Area - basically, the block of information that holds your connection state) is copied in too. ... So, you're left with working-storage, which makes it visible to your program only, or common-storage, which makes it visible to programs linked in. ...
    (comp.lang.cobol)
  • Split messages
    ... This is based off the northwind database. ... Create document schema: ... Select the SQL entry, make sure that we are pointing to the SQL ... For the item select a receive pipeline and name it EmpSplitPipe.btp. ...
    (microsoft.public.biztalk.general)
  • Re: Decouple SQL queries from class in OOP design
    ... > Of course there are existing applications that uses many different ... > architectures and still provides measurable business value. ... > should access every database directly. ... by the database, but the schema changes. ...
    (comp.object)