| Task |
Priority |
Description |
| Tamino Manager |
High |
Required for reading from and writing into a Tamino database. Compared
with the JDBC support, this is a simple thing, but a requirement to use
JaxMe in my business work. |
| Type mapping for primary keys |
Medium |
Currently it is only possible to use the same type for the primary
key. However, it is a common concept to use a different type for the API
to the user and/or modify the value when shown to the user. For example,
if the database contains the long value >5L as a key, and the
document type is Order, then we might use the value Or5
in the API. This requires modification of primary key type and/or value
when reading from or to the database. |
| Recursion |
Low |
Currently JaxMe cannot handle recursive schemata. For example, the
XML schema itself contains recursive structures: An "element" can be a
descendant of another "element".
Support for recursion should be relatively simple. It is sufficient
to detect recursion. As simple as using a HashMap (Namespace URI) of HashSets
(Local name). |
| XML:DB Support |
Low |
I personally do not need it, but perhaps others will. Would be nice
to implement a Tamino interface for XML:DB on top of JaxMe, though. :-) |
| Mixed use of xs:sequence/xs:choice |
Low |
Currently a complex type must be either a sequence or a choice. For
example, a sequence of a simple element and a choice is not supported. |
| GUI frontend |
Very low |
Would be nice to have, perhaps based on xybrix.
Contact Dennis Daniels. |