On Fri, Aug 15, 2003 at 11:38:42PM +0200, Daniel Bonniot wrote:
>
> Deprecated features are still available. There are still tagged, so that
> their use is discouraged, since they might be removed in a later
> release. As far as I know, nothing has ever been removed yet.
> Technically, if a pack
Hello Arnaud,
Friday, August 15, 2003, 11:46:31 PM, you wrote:
> Jan Schulz <[EMAIL PROTECTED]> wrote:
>> IMO the big enchancement is, that you only have to specify the
>> Depends once: in debian/control and everything else is added from
>> there on.
> That's what we all want ;)
Ok, I take that a
Hello Xavier,
[sorry for the private mail... sometime I will learn it... ]
Saturday, August 16, 2003, 1:28:54 AM, you wrote:
> However, if,for example, I want to use a newer version of xalan or
> xerces (xml-apis.jar) instead of Crimson (well, any other parser
> implementing JAXP), you will have
Hi Jan,
Thank you for your response and the clarity of it.
I think also it might be a good idea to set a default parser if more
than one is used.
Please also note that i should have mention xercesImpl.jar instead of
xml-apis.jar
in my previous mail as, with 1.4 versions,this one (well, the conte
We have been working for a while with J2SDK1.4.2 +
JBoss + Jetty/Tomcat + Apache 2.0.x, and we seem to
keep coming up across the same problem regarding the re-
compiling of mod_jk2 for work with these systems (to
bind apache + tomcat/jetty for request).
Not sure if this will be helpful, but tho
On Sat, Aug 16, 2003 at 02:36:08AM -0500, Mike Maurer wrote:
> Currently this is true of the official and blackdown implementations. I've never
> seen anything that says deprecated methods are guaranteed to exist until API
> version X, or that they're guranteed to be removed by version X. So I wo
In message: <[EMAIL PROTECTED]>
Daniel Bonniot <[EMAIL PROTECTED]> writes:
>
>>>I would think that java2 is a superset of java1.
>>
>>Unfortunately, this is not the case; the deprecation of methods and
>>classes make java2 an intersecting set, not a superset of java1.
>
>Deprecated fe
> Additionally, I still question the wisdom of the shared JNI directory.
> >From what I understand, there are different versions of JNI and you
> cannot count on the idea that all JNI libraries are simply going to work
> with all VMs. It's not clear to me that different versions of JNI can
> even
> Additionally, I still question the wisdom of the shared JNI directory.
> >From what I understand, there are different versions of JNI and you
> cannot count on the idea that all JNI libraries are simply going to work
> with all VMs.
Further to my last email, I should add that this is not an iss
On Fri, Aug 15, 2003 at 11:38:42PM +0200, Daniel Bonniot wrote:
>
> Deprecated features are still available. There are still tagged, so that
> their use is discouraged, since they might be removed in a later
> release. As far as I know, nothing has ever been removed yet.
> Technically, if a pack
Hello Arnaud,
Friday, August 15, 2003, 11:46:31 PM, you wrote:
> Jan Schulz <[EMAIL PROTECTED]> wrote:
>> IMO the big enchancement is, that you only have to specify the
>> Depends once: in debian/control and everything else is added from
>> there on.
> That's what we all want ;)
Ok, I take that a
Hello Xavier,
[sorry for the private mail... sometime I will learn it... ]
Saturday, August 16, 2003, 1:28:54 AM, you wrote:
> However, if,for example, I want to use a newer version of xalan or
> xerces (xml-apis.jar) instead of Crimson (well, any other parser
> implementing JAXP), you will have
Hi Jan,
Thank you for your response and the clarity of it.
I think also it might be a good idea to set a default parser if more
than one is used.
Please also note that i should have mention xercesImpl.jar instead of
xml-apis.jar
in my previous mail as, with 1.4 versions,this one (well, the conten
We have been working for a while with J2SDK1.4.2 +
JBoss + Jetty/Tomcat + Apache 2.0.x, and we seem to
keep coming up across the same problem regarding the re-
compiling of mod_jk2 for work with these systems (to
bind apache + tomcat/jetty for request).
Not sure if this will be helpful, but tho
On Sat, Aug 16, 2003 at 02:36:08AM -0500, Mike Maurer wrote:
> Currently this is true of the official and blackdown implementations. I've
> never
> seen anything that says deprecated methods are guaranteed to exist until API
> version X, or that they're guranteed to be removed by version X. So I
In message: <[EMAIL PROTECTED]>
Daniel Bonniot <[EMAIL PROTECTED]> writes:
>
>>>I would think that java2 is a superset of java1.
>>
>>Unfortunately, this is not the case; the deprecation of methods and
>>classes make java2 an intersecting set, not a superset of java1.
>
>Deprecated fe
> Additionally, I still question the wisdom of the shared JNI directory.
> >From what I understand, there are different versions of JNI and you
> cannot count on the idea that all JNI libraries are simply going to work
> with all VMs. It's not clear to me that different versions of JNI can
> even
> Additionally, I still question the wisdom of the shared JNI directory.
> >From what I understand, there are different versions of JNI and you
> cannot count on the idea that all JNI libraries are simply going to work
> with all VMs.
Further to my last email, I should add that this is not an iss
18 matches
Mail list logo
