I can see doing that with an element we control so there is only one
copy, but I am also reluctant to pull j2ee schema elements into our
schemas at all. For this specific case I'm inclined to think that it
is much simpler to copy the type rather than set up dependencies
between the schemas, whether only ours or also the j2ee ones.
thanks
david jencks
On Jul 10, 2005, at 8:12 PM, Aaron Mulder wrote:
It might be nice if the schema-specific description element
extended or restricted or whatever the J2EE description element, such
that
they're guaranteed to have the same content, and this is just a
convenience to avoid lots of manual namespacing. Still, I fear that
may
aggravate XMLBeans. Some day, we'll all use JSR-88 and not worry about
writing our own DDs. I'll grant you that day is not here. :)
Aaron
On Mon, 11 Jul 2005, David Jencks (JIRA) wrote:
security, css, and tss schemas have description element from foreign
namespace. This is incredibly inconvenient
----------------------------------------------------------------------
------------------------------------------
Key: GERONIMO-736
URL: http://issues.apache.org/jira/browse/GERONIMO-736
Project: Geronimo
Type: Bug
Components: buildsystem
Versions: 1.0-M3
Reporter: David Jencks
Assigned to: David Jencks
The security, css and tss schemas include a description element from
the j2ee 1.4 namespace. If anyone tried to use this they would have
to change namespaces on each description element.
Solution is to provide a description type in each of these schemas.
--
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
