<div dir="ltr"><div><div><div>that is why i would suggest packaging this modules in special folder <br>under our distribution that would only be accessible by domain controller itself.<br><br></div><div>This way we make sure this modules only operate in MODEL stage.<br>
</div><div><br></div>Sure noting stops user from moving this modules to some other folder, <br>but he could also copy them from older version....<br><br></div>Other option would be to do model version checking, aka if module name is org.jboss.as.*<br>
and major version is < 2 we would not allow runtime stage to be executed.<br></div>That brings some more complexity and forces us to bump major version for all subsystems<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sat, Mar 2, 2013 at 12:15 AM, Brian Stansberry <span dir="ltr"><<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When I say "find problems" I don't mean management problems. I mean runtime service bugs. If we ship the 7.2 CMP module and someone runs it on an AS8 server and reports an EJBQL parsing bug, how do we respond?<div class="im">
<br>
<br>
On 3/1/13 5:07 PM, Tomaž Cerar wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
hmm, given that DC only operates on MODEL/ADMIN stage<br>
there should no big issues if we make sure our model driven api is<br>
compatible also in AS8.<br>
I think that would be mostly jboss-as-controller and maybe few more.<br>
But before I speculate, I should test my theory...<br>
--<br>
tomaz<br>
<br>
<br>
On Fri, Mar 1, 2013 at 11:55 PM, Brian Stansberry<br></div><div class="im">
<<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a> <mailto:<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@<u></u>redhat.com</a>>> wrote:<br>
<br>
They have to have logic that prevents their use on an AS8 server.<br>
Unless we are willing to tell folks who use them on AS8 servers and<br>
find problems that they're out of luck and should know better.<br>
<br>
<br>
On 3/1/13 4:49 PM, Tomaž Cerar wrote:<br>
<br>
What about if we just use legacy extensions that would be loaded<br>
only on DC?<br>
for legacy i mean, why not just have modules / jars from 7.2 in<br>
8.0 distro?<br>
that would make it easiest to support, and no extra work.<br>
We should just put them in some special place in distro,<br>
so it would be obvious that is legacy stuff only DC uses...<br>
<br>
<br>
On Fri, Mar 1, 2013 at 11:44 PM, Brian Stansberry<br>
<<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a><br>
<mailto:<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@<u></u>redhat.com</a>><br></div>
<mailto:<a href="mailto:brian.stansberry@" target="_blank">brian.stansberry@</a>__<a href="http://redhat.com" target="_blank">red<u></u>hat.com</a><div class="im"><br>
<mailto:<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@<u></u>redhat.com</a>>>> wrote:<br>
<br>
The extension registration logic would have to be altered<br>
to not barf<br>
when multiple aliases all try to register the same extensions/<br>
subsystems.<br>
<br>
But it probably should still barf if a user tried to do<br>
that for some<br>
other reason. So which is happening needs to be clarified.<br>
<br>
A way to do that is to use something other than<br></div>
org.jboss.as.controller.__<u></u>Extension for the ServiceLoader<div class="im"><br>
(i.e. first try<br>
ServiceLoader for "LegacyExtension" and then if not there<br>
try for<br></div>
org.jboss.as.controller.__<u></u>Extension.) That's hacky though<div><div class="h5"><br>
unless there is<br>
a real difference in the service API between Extension and<br>
what these<br>
legacy extensions do. AFAICT though, there is no API<br>
difference;<br>
difference is only in impl.<br>
<br>
On 3/1/13 4:23 PM, David M. Lloyd wrote:<br>
> Rewinding the discussion a bit :)<br>
><br>
> If we just had one compat module (with N pure aliases),<br>
it could<br>
easily<br>
> register all the subsystems for all the modules at that time<br>
(subsystem<br>
> registration is pretty lightweight these days, or so it<br>
seems at a<br>
> glance). If extra subsystems are available as a result<br>
of an<br>
extension<br>
> reg I don't see that as harmless.<br>
><br>
> On 03/01/2013 02:48 PM, Brian Stansberry wrote:<br>
>> I'm not sure how the ServiceLoader part would work<br>
there. At<br>
least not<br>
>> with what I imagine when I think of an "alias." With<br>
some kind<br>
of stub<br>
>> where each has a different<br></div></div>
>> META-INF/services/org.jboss.__<u></u>as.controller.Extension<div><div class="h5"><br>
file it<br>
could work.<br>
>><br>
>> On 3/1/13 2:29 PM, David M. Lloyd wrote:<br>
>>> Yeah, I was thinking they could just be aliases or<br>
stubs though.<br>
>>><br>
>>> On 03/01/2013 02:22 PM, Brian Stansberry wrote:<br>
>>>> In terms of code organization, perhaps. But the way the<br>
extension is<br>
>>>> activated in the HCs and servers is via the module<br>
name. So if<br>
you want<br>
>>>> a 7.2 server to be able to run CMP, there is going to<br>
have to be a<br>
>>>> module named org.jboss.as.cmp.<br>
>>>><br>
>>>> On 3/1/13 2:13 PM, David M. Lloyd wrote:<br>
>>>>> I wonder - should we retain a skeletal version of<br>
each of<br>
these modules?<br>
>>>>> I was thinking maybe it would be better to<br>
maintain<br>
one big<br>
>>>>> "removed-subsystems" or "compat-subsystems" module or<br>
something like<br>
>>>>> that where we can neatly/consistently organize all<br>
the model<br>
stuff for<br>
>>>>> these removals.<br>
>>>>><br>
>>>>> On 03/01/2013 09:39 AM, Brian Stansberry wrote:<br>
>>>>>> Thanks Thomas, for raising this and for the JIRA.<br>
>>>>>><br>
>>>>>> I've outlined what I think is needed for the stub<br>
extensions<br>
as a<br>
>>>>>> comment on<br></div></div>
<a href="https://issues.jboss.org/__browse/AS7-6656" target="_blank">https://issues.jboss.org/__<u></u>browse/AS7-6656</a><div class="im"><br>
<<a href="https://issues.jboss.org/browse/AS7-6656" target="_blank">https://issues.jboss.org/<u></u>browse/AS7-6656</a>> .<br>
>>>>>><br>
>>>>>> Can I request that folks hold up on deleting these<br>
subsystems? I think<br>
>>>>>> it will be easier to make these changes and then<br>
delete the<br>
unneeded<br>
>>>>>> runtime stuff than it will be to semi-restore from<br>
history<br>
and then change.<br>
>>>>>><br>
>>>>>> The ones that have already been deleted, it's no<br>
big deal.<br>
>>>>>><br>
>>>>>> On 2/28/13 10:35 AM, Thomas Diesler wrote:<br>
>>>>>>> Ok, stub extensions is the obvious alternative to<br>
breaking<br>
compatibility. I'll leave this as a future task and create<br>
a jira<br>
for it if that's ok with you.<br>
>>>>>>><br>
>>>>>>> cheers<br>
>>>>>>> --thomas<br>
>>>>>>><br>
>>>>>>> On Feb 28, 2013, at 4:22 PM, David M. Lloyd<br>
<<a href="mailto:david.lloyd@redhat.com" target="_blank">david.lloyd@redhat.com</a> <mailto:<a href="mailto:david.lloyd@redhat.com" target="_blank">david.lloyd@redhat.com</a><u></u>><br></div>
<mailto:<a href="mailto:david.lloyd@redhat.com" target="_blank">david.lloyd@redhat.com</a><div class="im"><br>
<mailto:<a href="mailto:david.lloyd@redhat.com" target="_blank">david.lloyd@redhat.com</a><u></u>>__>> wrote:<br>
>>>>>>><br>
>>>>>>>> On 02/28/2013 05:57 AM, Thomas Diesler wrote:<br>
>>>>>>>>> Folks,<br>
>>>>>>>>><br>
>>>>>>>>> related to<br>
>>>>>>>>><br>
>>>>>>>>> * [AS7-6612<br></div>
<<a href="https://issues.jboss.org/__browse/AS7-6612" target="_blank">https://issues.jboss.org/__<u></u>browse/AS7-6612</a><div><div class="h5"><br>
<<a href="https://issues.jboss.org/browse/AS7-6612" target="_blank">https://issues.jboss.org/<u></u>browse/AS7-6612</a>>>]<br>
Remove JAXR support<br>
>>>>>>>>><br>
>>>>>>>>> I'd like to know whether we need to preserve<br>
backward<br>
compatibility of<br>
>>>>>>>>> the configuration and if so what should happen<br>
if there<br>
is a jaxr config<br>
>>>>>>>>> item? Generally, can AS8 break backward<br>
compatibility<br>
with respect to<br>
>>>>>>>>> the config?<br>
>>>>>>>><br>
>>>>>>>> Brian points out that we don't have a specific<br>
requirement<br>
to maintain<br>
>>>>>>>> compatibility with obsolete subsystems. I think<br>
we could<br>
go ahead with<br>
>>>>>>>> the removal (granted part of the reason I feel<br>
this way is<br>
that I've<br>
>>>>>>>> already removed JSR-88...).<br>
>>>>>>>><br>
>>>>>>>> Going forward though Kabir suggested that if we<br>
do want<br>
to, say, allow<br>
>>>>>>>> 7.x instances to be managed from an 8.x DC, that<br>
we should<br>
create "stub"<br>
>>>>>>>> extensions for the removed stuff that only carry<br>
and validate<br>
>>>>>>>> configuration but aren't actually supported on 8.x<br>
servers. This seems<br>
>>>>>>>> like a valid possibility to me.<br>
>>>>>>>> --<br>
>>>>>>>> - DML<br></div></div>
>>>>>>>> ______________________________<u></u>___________________<div class="im"><br>
>>>>>>>> jboss-as7-dev mailing list<br>
>>>>>>>> <a href="mailto:jboss-as7-dev@lists.jboss.org" target="_blank">jboss-as7-dev@lists.jboss.org</a><br>
<mailto:<a href="mailto:jboss-as7-dev@lists.jboss.org" target="_blank">jboss-as7-dev@lists.<u></u>jboss.org</a>><br></div>
<mailto:<a href="mailto:jboss-as7-dev@lists." target="_blank">jboss-as7-dev@lists.</a>__<a href="http://jboss.org" target="_blank"><u></u>jboss.org</a><br>
<mailto:<a href="mailto:jboss-as7-dev@lists.jboss.org" target="_blank">jboss-as7-dev@lists.<u></u>jboss.org</a>>><br>
<br>
>>>>>>>><br>
<a href="https://lists.jboss.org/__mailman/listinfo/jboss-as7-dev" target="_blank">https://lists.jboss.org/__<u></u>mailman/listinfo/jboss-as7-dev</a><div class="im"><br>
<<a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev" target="_blank">https://lists.jboss.org/<u></u>mailman/listinfo/jboss-as7-dev</a><u></u>><br>
>>>>>>><br>
>>>>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx<br>
>>>>>>> Thomas Diesler<br>
>>>>>>> JBoss OSGi Lead<br>
>>>>>>> JBoss, a division of Red Hat<br>
>>>>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br></div>
>>>>>>> ______________________________<u></u>___________________<div class="im"><br>
>>>>>>> jboss-as7-dev mailing list<br>
>>>>>>> <a href="mailto:jboss-as7-dev@lists.jboss.org" target="_blank">jboss-as7-dev@lists.jboss.org</a><br>
<mailto:<a href="mailto:jboss-as7-dev@lists.jboss.org" target="_blank">jboss-as7-dev@lists.<u></u>jboss.org</a>><br></div>
<mailto:<a href="mailto:jboss-as7-dev@lists." target="_blank">jboss-as7-dev@lists.</a>__<a href="http://jboss.org" target="_blank"><u></u>jboss.org</a><br>
<mailto:<a href="mailto:jboss-as7-dev@lists.jboss.org" target="_blank">jboss-as7-dev@lists.<u></u>jboss.org</a>>><br>
<br>
>>>>>>><br>
<a href="https://lists.jboss.org/__mailman/listinfo/jboss-as7-dev" target="_blank">https://lists.jboss.org/__<u></u>mailman/listinfo/jboss-as7-dev</a><div class="im"><br>
<<a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev" target="_blank">https://lists.jboss.org/<u></u>mailman/listinfo/jboss-as7-dev</a><u></u>><br>
>>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>><br>
>>>>><br>
>>>><br>
>>>><br>
>>><br>
>>><br>
>><br>
>><br>
><br>
><br>
<br>
<br>
--<br>
Brian Stansberry<br>
Principal Software Engineer<br>
JBoss by Red Hat<br></div>
______________________________<u></u>___________________<div class="im"><br>
jboss-as7-dev mailing list<br>
<a href="mailto:jboss-as7-dev@lists.jboss.org" target="_blank">jboss-as7-dev@lists.jboss.org</a><br>
<mailto:<a href="mailto:jboss-as7-dev@lists.jboss.org" target="_blank">jboss-as7-dev@lists.<u></u>jboss.org</a>><br></div>
<mailto:<a href="mailto:jboss-as7-dev@lists." target="_blank">jboss-as7-dev@lists.</a>__<a href="http://jboss.org" target="_blank"><u></u>jboss.org</a><br>
<mailto:<a href="mailto:jboss-as7-dev@lists.jboss.org" target="_blank">jboss-as7-dev@lists.<u></u>jboss.org</a>>><br>
<a href="https://lists.jboss.org/__mailman/listinfo/jboss-as7-dev" target="_blank">https://lists.jboss.org/__<u></u>mailman/listinfo/jboss-as7-dev</a><div class="im"><br>
<<a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev" target="_blank">https://lists.jboss.org/<u></u>mailman/listinfo/jboss-as7-dev</a><u></u>><br>
<br>
<br>
<br>
<br>
--<br>
Brian Stansberry<br>
Principal Software Engineer<br>
JBoss by Red Hat<br>
<br>
<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
-- <br>
Brian Stansberry<br>
Principal Software Engineer<br>
JBoss by Red Hat<br>
</div></div></blockquote></div><br></div>