charlie hunt wrote:
> Would it help to rename them to;
> com.sun.grizzly.org.apache.coyote and
> com.sun.grizzly.org.apache.tomcat.util ?
No because external component like mod_jk requires org.apache.coyote.*
I'm trying to find a way to avoid breaking backward
compatibility....quite a challenge :-)
A+
>
> charlie ...
>
> Jeanfrancois Arcand wrote:
>> Hi,
>>
>> when we released Grizzly 1.5.x, we took classes from
>> org.apache.coyote/tomcat to com.sun.grizzly. So far it worked well but
>> it gives trouble when we:
>>
>> + want to port fixes from Tomcat directly (always have to find the
>> associated classes)
>> + breaks backward compatibility with GlassFish when Apache mod_jk is
>> used, because mod_jk requires classes with org.apache.* .
>>
>> So I would like to rename those classes back to their original package
>> so the process will be simpler. The issue I'm having is it MAY breaks
>> ***a lot*** of applications that were using packages:
>>
>> com.sun.grizzly.util.*
>>
>> I don't have any better solution unfortunately. If someone has a
>> better idea, please let me know.
>>
>> Thanks!!!
>>
>> -- Jeanfrancois
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>