2:48 p.m.
The jboss-web_5_0.dtd available from
http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd is different from the
one in AS 5's docs/dtd directory. Looks like an updated version needs to
be pushed to jboss.org (cc'd).
Probably a general update is in order.
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
5:15 a.m.
Brian Stansberry wrote:
Probably a general update is in order.
I guess, there are some other inconsistencies too
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=149036
regards,
-Jaikiran
6:53 a.m.
We still haven't found a reliable way to keep the dtds/schemas on the www.jboss.org
side
up-to-date.
The dtds/schemas live in different locations in the code, e.g.:
https://svn.jboss.org/repos/jbossas/trunk/server/src/resources/dtd/
https://svn.jboss.org/repos/jbossas/trunk/server/src/resources/schema/
or
https://svn.jboss.org/repos/jbossas/trunk/mbeans/src/resources/dtd/
They might also live in external projects, like the security-config_x_y.xsds.
Then the majority (but not all) are gathered in the JBOSS_HOME/docs/dtd|schema directory.
We could have a process where every time a JBoss AS version is released, the website is
updated.
For this to work, I think the following should apply:
1) DTD/schemas are only allowd to change before the final (GA) version in which they are
specified. E.g. jboss_5_0.xsd could be initially published with 5.0.0.Beta1, and change in
5.0.0.CR1, but never change again after 5.0.0.GA is out.
2) Every time a dtd/schema is introduced/modified the change should propagate to all
upstream branches/trunk. E.g. If you add jboss_5_1.xsd in Branch_5_x you need to add it to
trunk as well. And if change it in Branch_5_x (before the 5.1 GA release is out) you need
to
do the same in trunk.
3) Whenever the website is updated, we don't cleanup the previous content first, we
just
overwrite it with the latest. This is to avoid dtds/schemas coming from other projects
getting lost. Or else we would have to make sure all those end up in JBOSS_HOME/docs
during
the build process.
Another issue is that the update of the www.jboss.org site is totally manual now. You need
to contact helpdesk to do the update.
Thoughts?
/Dimitris
Jaikiran Pai wrote:
Brian Stansberry wrote:
> Probably a general update is in order.
>
I guess, there are some other inconsistencies too
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=149036
regards,
-Jaikiran
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
7:26 a.m.
Dimitris Andreadis wrote:
We could have a process where every time a JBoss AS version is
released,
the website is updated.
For this to work, I think the following should apply:
1) DTD/schemas are only allowd to change before the final (GA) version
in which they are specified. E.g. jboss_5_0.xsd could be initially
published with 5.0.0.Beta1, and change in 5.0.0.CR1, but never change
again after 5.0.0.GA is out.
I think I've been silently bitten by this before. My 5.0.0.Beta2 release
suddenly stopped working without explanation (i.e. without me having
modified anything which might account for the balls-up). I 'fixed' the
problem by upgrading to the newly released Beta3 and only later worked
out that the problems were to do with obtaining schemas from jboss.org
(actually, I'm not sure now that the switcheroo didn't happen at the
Beta1/2 transition but you get the point). It's a little unsatisfactory
that beta users may be arbitrarily confounded by this sort of update. We
don't really want to make life any more difficult or puzzling than
necessary for our valuable early adopters.
I guess resolving this would require having (and having the users
include) minor release-specific schemas prior to GA. This has the
disadvantage that it requires users to modify their app code but at
least they can see what is happening.
Otherwise the rest sounds like it works.
regards,
Andrew Dinn
-----------
8:25 a.m.
I believe it's a bit too much to ask that a dtd/schema doesn't change at all
before a final
release. You might need to fix a typo or something. Breaking (for a good reason) an
Alpha/Beta/CR user is almost acceptable.
However, breaking the dtd/schema compatibility for a GA user is bad, and IMHO fixing this
should be our focus.
Andrew Dinn wrote:
Dimitris Andreadis wrote:
> We could have a process where every time a JBoss AS version is
> released, the website is updated.
>
> For this to work, I think the following should apply:
>
> 1) DTD/schemas are only allowd to change before the final (GA) version
> in which they are specified. E.g. jboss_5_0.xsd could be initially
> published with 5.0.0.Beta1, and change in 5.0.0.CR1, but never change
> again after 5.0.0.GA is out.
I think I've been silently bitten by this before. My 5.0.0.Beta2 release
suddenly stopped working without explanation (i.e. without me having
modified anything which might account for the balls-up). I 'fixed' the
problem by upgrading to the newly released Beta3 and only later worked
out that the problems were to do with obtaining schemas from jboss.org
(actually, I'm not sure now that the switcheroo didn't happen at the
Beta1/2 transition but you get the point). It's a little unsatisfactory
that beta users may be arbitrarily confounded by this sort of update. We
don't really want to make life any more difficult or puzzling than
necessary for our valuable early adopters.
I guess resolving this would require having (and having the users
include) minor release-specific schemas prior to GA. This has the
disadvantage that it requires users to modify their app code but at
least they can see what is happening.
Otherwise the rest sounds like it works.
regards,
Andrew Dinn
-----------
6:23 a.m.
https://jira.jboss.org/jira/browse/JBAS-6114
Jaikiran Pai wrote:
Brian Stansberry wrote:
> Probably a general update is in order.
>
I guess, there are some other inconsistencies too
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=149036
regards,
-Jaikiran
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
6:41 a.m.
The zip file attached to that issue seems to be having an inconsistency
between the jboss_5_0.dtd and jboss_5_0.xsd. Especially, the dtd does
not mention that the a <service> element can be used within the
<enterprise-beans>, whereas the xsd correctly does:
<xsd:complexType name="enterprise-beansType">
....
<xsd:choice maxOccurs="unbounded">
..... //removed intentionally
<xsd:element name="service"
type="jboss:service-beanType">
</xsd:element>
<xsd:element name="consumer"
type="jboss:consumer-beanType">
</xsd:element>
<!-- For generic ejb -->
<xsd:element name="ejb"
type="jboss:generic-beanType"/>
</xsd:choice>
</xsd:complexType>
regards,
-Jaikiran
Dimitris Andreadis wrote:
https://jira.jboss.org/jira/browse/JBAS-6114
Jaikiran Pai wrote:
> Brian Stansberry wrote:
>> Probably a general update is in order.
>>
> I guess, there are some other inconsistencies too
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=149036
>
> regards,
> -Jaikiran
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
7:27 a.m.
Issues of this type should be opened against the JBMETA project.
Jaikiran Pai wrote:
The zip file attached to that issue seems to be having an
inconsistency
between the jboss_5_0.dtd and jboss_5_0.xsd. Especially, the dtd does
not mention that the a <service> element can be used within the
<enterprise-beans>, whereas the xsd correctly does:
<xsd:complexType name="enterprise-beansType">
.... <xsd:choice maxOccurs="unbounded">
..... //removed intentionally
<xsd:element name="service"
type="jboss:service-beanType">
</xsd:element>
<xsd:element name="consumer"
type="jboss:consumer-beanType">
</xsd:element>
<!-- For generic ejb -->
<xsd:element name="ejb"
type="jboss:generic-beanType"/>
</xsd:choice>
</xsd:complexType>
regards,
-Jaikiran
Dimitris Andreadis wrote:
> https://jira.jboss.org/jira/browse/JBAS-6114
>
> Jaikiran Pai wrote:
>> Brian Stansberry wrote:
>>> Probably a general update is in order.
>>>
>> I guess, there are some other inconsistencies too
>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=149036
>>
>> regards,
>> -Jaikiran
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
7:57 a.m.
The DTD is for legacy EJB2 containers only, XSD is only for the EJB3 stuff.
We (or was it just me) have been dealing with this for a long time now.
DTD and XSD were maid different on purpose, which was discussed (or at
least announced) on this list, forums and phone calls.
This is the case for the jboss ejb schemas only.
jboss-web and jboss-app still have only the dtd.
jboss-client has both, I haven't looked into differences yet but unless
there is a reason for the DTD it should not be supported.
Alexey
Dimitris Andreadis wrote:
Issues of this type should be opened against the JBMETA project.
Jaikiran Pai wrote:
> The zip file attached to that issue seems to be having an
> inconsistency between the jboss_5_0.dtd and jboss_5_0.xsd. Especially,
> the dtd does not mention that the a <service> element can be used
> within the <enterprise-beans>, whereas the xsd correctly does:
>
> <xsd:complexType name="enterprise-beansType">
> .... <xsd:choice maxOccurs="unbounded">
> ..... //removed intentionally
>
> <xsd:element name="service"
type="jboss:service-beanType">
> </xsd:element>
> <xsd:element name="consumer"
type="jboss:consumer-beanType">
> </xsd:element>
> <!-- For generic ejb -->
> <xsd:element name="ejb"
type="jboss:generic-beanType"/>
> </xsd:choice>
>
> </xsd:complexType>
>
>
> regards,
> -Jaikiran
> Dimitris Andreadis wrote:
>> https://jira.jboss.org/jira/browse/JBAS-6114
>>
>> Jaikiran Pai wrote:
>>> Brian Stansberry wrote:
>>>> Probably a general update is in order.
>>>>
>>> I guess, there are some other inconsistencies too
>>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=149036
>>>
>>> regards,
>>> -Jaikiran
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
9:41 a.m.
Okay, i wasn't aware this was intentional.
-Jaikiran
Alexey Loubyansky wrote:
The DTD is for legacy EJB2 containers only, XSD is only for the EJB3
stuff.
We (or was it just me) have been dealing with this for a long time
now. DTD and XSD were maid different on purpose, which was discussed
(or at least announced) on this list, forums and phone calls.
This is the case for the jboss ejb schemas only.
jboss-web and jboss-app still have only the dtd.
jboss-client has both, I haven't looked into differences yet but
unless there is a reason for the DTD it should not be supported.
Alexey
Dimitris Andreadis wrote:
> Issues of this type should be opened against the JBMETA project.
>
> Jaikiran Pai wrote:
>> The zip file attached to that issue seems to be having an
>> inconsistency between the jboss_5_0.dtd and jboss_5_0.xsd.
>> Especially, the dtd does not mention that the a <service> element
>> can be used within the <enterprise-beans>, whereas the xsd correctly
>> does:
>>
>> <xsd:complexType name="enterprise-beansType">
>> .... <xsd:choice maxOccurs="unbounded">
>> ..... //removed intentionally
>>
>> <xsd:element name="service"
type="jboss:service-beanType">
>> </xsd:element>
>> <xsd:element name="consumer"
type="jboss:consumer-beanType">
>> </xsd:element>
>> <!-- For generic ejb -->
>> <xsd:element name="ejb"
type="jboss:generic-beanType"/>
>> </xsd:choice>
>>
>> </xsd:complexType>
>>
>>
>> regards,
>> -Jaikiran
>> Dimitris Andreadis wrote:
>>> https://jira.jboss.org/jira/browse/JBAS-6114
>>>
>>> Jaikiran Pai wrote:
>>>> Brian Stansberry wrote:
>>>>> Probably a general update is in order.
>>>>>
>>>> I guess, there are some other inconsistencies too
>>>> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=149036
>>>>
>>>> regards,
>>>> -Jaikiran
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
5813
days inactive
5854
days old
jboss-development@lists.jboss.org
9 comments
5 participants
participants (5)
-
Alexey Loubyansky -
Andrew Dinn -
Brian Stansberry -
Dimitris Andreadis -
Jaikiran Pai