You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rakesh Midha (JIRA)" <ji...@apache.org> on 2006/12/14 07:44:20 UTC
[jira] Created: (GERONIMO-2660) Uniqueness constraint missing in
multiple places in geronimo schema's
Uniqueness constraint missing in multiple places in geronimo schema's
---------------------------------------------------------------------
Key: GERONIMO-2660
URL: http://issues.apache.org/jira/browse/GERONIMO-2660
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: deployment
Affects Versions: 2.0
Environment: Any
Reporter: Rakesh Midha
Assigned To: Rakesh Midha
Fix For: 2.0
Uniqueness constraint is missing in multiple places in geronimo schema's, this allows the multiple attributes to be specified in geronimo plan files without any problem.
Few examples:
In geronimo-web and openejb, multiple ejb-local-ref or any references with same ref-name are allowed, which is wrong.
In openejb multiple cmp fields with same name are allowed.
These are just two examples, if we look at any xsd file we dont have many constraints, if we look at coorsponding j2ee descriptors schema we will see all the required constraints.
It is not a mandatory feature to have, but I think right guidelines should be followed. It will require lot of changes though, in all the schema files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2660) Uniqueness constraint missing in
multiple places in geronimo schema's
Posted by "Prasad Kashyap (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Kashyap updated GERONIMO-2660:
-------------------------------------
Description:
Uniqueness constraint is missing in multiple places in geronimo schema's, this allows the multiple attributes to be specified in geronimo plan files without any problem.
Few examples:
In geronimo-web and openejb, multiple ejb-local-ref or any references with same ref-name are allowed, which is wrong.
In openejb multiple cmp fields with same name are allowed.
These are just two examples, if we look at any xsd file we dont have many constraints, if we look at coorsponding j2ee descriptors schema we will see all the required constraints.
It is not a mandatory feature to have, but I think right guidelines should be followed. It will require lot of changes though, in all the schema files.
was:
Uniqueness constraint is missing in multiple places in geronimo schema's, this allows the multiple attributes to be specified in geronimo plan files without any problem.
Few examples:
In geronimo-web and openejb, multiple ejb-local-ref or any references with same ref-name are allowed, which is wrong.
In openejb multiple cmp fields with same name are allowed.
These are just two examples, if we look at any xsd file we dont have many constraints, if we look at coorsponding j2ee descriptors schema we will see all the required constraints.
It is not a mandatory feature to have, but I think right guidelines should be followed. It will require lot of changes though, in all the schema files.
Fix Version/s: (was: 2.0-M5)
Wish List
> Uniqueness constraint missing in multiple places in geronimo schema's
> ---------------------------------------------------------------------
>
> Key: GERONIMO-2660
> URL: https://issues.apache.org/jira/browse/GERONIMO-2660
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0-M5
> Environment: Any
> Reporter: Rakesh Midha
> Assignee: Rakesh Midha
> Fix For: Wish List
>
>
> Uniqueness constraint is missing in multiple places in geronimo schema's, this allows the multiple attributes to be specified in geronimo plan files without any problem.
> Few examples:
> In geronimo-web and openejb, multiple ejb-local-ref or any references with same ref-name are allowed, which is wrong.
> In openejb multiple cmp fields with same name are allowed.
> These are just two examples, if we look at any xsd file we dont have many constraints, if we look at coorsponding j2ee descriptors schema we will see all the required constraints.
> It is not a mandatory feature to have, but I think right guidelines should be followed. It will require lot of changes though, in all the schema files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.