XML TRANSFORMER

Michał, Karol, Paweł

Presentation plan
 Who we are?
 What was the problem?
 What we do to resolve it?
 How we do that?
 What we have learned?
 What should be done next?
 Who we are?

Michał Kosowski Karol Andrusieczko Paweł Bugno

Students at Wrocław University of Technology:

• 5th year in Teleinformatics, Faculty of Electronics
• 3th year in Computer Science, Faculty of Fundamental Problems of Technology
What was the problem
… or why do we need the XML Transformer
The problem

Old XML structure New XML structure

 Basic solution
Changing node name

Deleting node

Adding new node

Changing node type

Old file New file

Moving node

Calculating value from

Changing node value Other nodes using external
functions eg. Written in C++
 Basic solution problem

Click! Click!
Click!

Click! Click!

Click!

Click!

Set of the XML files Set of XML files, with

with the old structure a proper sturcture
Automation of the solution

Operations, needed to structure change

It’s mainly what the XML Transformer do

Process
automation
What we do…
Basics of our application
Features
 Split view, on which you can observe both: old and new
file structure
 Three different views:
 Structure view
 Schema view
 Source view
 Batch conversion mode
 XSLT file generation
 Extensible with functions written in external languages
- calculation of nodes values
Fast lookup – main window
Different views comparison
Batch conversion mode
Extension functions

C++ DL Java .class

L
XML Transformer

custom functions

Extension functions
XSLT i.e. java:Package.Class.function()

XML
Schema algorithm
XSLT - problems
 Transforming XML file into another one.
 Moving actions from application to XSL.
 Handling XSL in a proper manner.
 Performing XSL commands in Java.
 Describing our goals clearly.
 Merging XSL templates in one stylesheet.
 Processing XML file with Xalan.
XSLT
The Patterns….
 Main patterns which we use:
 Command
 Observer
 Builder
 Factory Method
 MVP
…and the UML
How we do that?
…our work in big summary
Step 1 – Learning
Eclipse
Java
XML
w3c.dom
XSLT
Xerces
Hudson
Xalan
Ant
JUnit sax jaxen
Step 2 – planning

Weekly meetings in 1010

 Step 3 - coding

Programming in pairs
in the room 1010
What we have learned?
What we have learned?
Plans for the future
What should be done
 Interface improvement
 More tests
 Undo / Redo
 Intuitive functions choosing from menu
 Difference coloring
 Saving non complete project
 etc.
 How we wan’t to do that

New colaborants,
Project website maybe from NSN?

Hudson and all other

Project management system interesting stuff
Kliknij ikonę, aby dodać obraz

Thanks for attention

Michał KOSOWSKI, Karol ANDRUSIECZKO, Paweł BUGNO