Thanks John
--- En date de : Lun 7.2.11, John Baker a
écrit :
De: John Baker
Objet: Rant: Re: [ARSLIST] JAVA API in a x64 machine using x32 dlls
À: arslist@ARSLIST.ORG
Date: Lundi 7 février 2011, 22h02
John,
In the interests of fairness, there's a community edition of the XML Ga
XMLGateway -- seems like a great approach.
I figure -- if you want your system to expand it's foothold you would be wise
in making it easy for all to interact with it.
This kind of functionality should exist in the raw package.
-John
On Feb 7, 2011, at 4:02 PM, John Baker wrote:
John,
John,
In the interests of fairness, there's a community edition of the XML Gateway
which does the same, but more :-)
http://www.javasystemsolutions.com/jss/video/view/BMCITSMIncidentsTasksWorklogs
Read all about it:
http://www.javasystemsolutions.com/documentation/xmlgateway/jss-xmlgateway-ins
Am I right?
Regards
frex
--- En date de : Ven 4.2.11, Axton a écrit :
De: Axton
Objet: Re: JAVA API in a x64 machine using x32 dlls
À: arslist@ARSLIST.ORG
Date: Vendredi 4 février 2011, 16h39
** Hot deployments would sure make development and deployments a lot easier
(and more product
Many thanks Axton.
--- En date de : Sam 5.2.11, Axton a écrit :
De: Axton
Objet: Re: JAVA API in a x64 machine using x32 dlls
À: arslist@ARSLIST.ORG
Date: Samedi 5 février 2011, 16h45
**
These are the option I see:- Use a 32-bit JVM and use the Remedy Java API
- Use a 64-bit JVM and don&#
t; 64x JVM in the same machine - use the correct Java version when compiling
> and running the API? Am I right?
>
> Regards
> frex
>
> --- En date de : *Ven 4.2.11, Axton * a écrit :
>
>
> De: Axton
> Objet: Re: JAVA API in a x64 machine using x32 dlls
> À: arslist@
when compiling and
running the API? Am I right?
Regards
frex
--- En date de : Ven 4.2.11, Axton a écrit :
De: Axton
Objet: Re: JAVA API in a x64 machine using x32 dlls
À: arslist@ARSLIST.ORG
Date: Vendredi 4 février 2011, 16h39
** Hot deployments would sure make development and deployments
Hot deployments would sure make development and deployments a lot easier
(and more productive - less development time and less downtime). Getting
rid of the native library dependencies would make that possible.
Axton Grams
The opinions, statements, and/or suggested courses of action expressed in
.
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Frex Popo
Sent: Friday, February 04, 2011 7:28 AM
To: arslist@ARSLIST.ORG
Subject: JAVA API in a x64 machine using x32 dlls
**
Dear listers,
I am not a Java person and would need some poi
Axton is correct, however you almost certainly don't want to really use
a 64bit VM, and if this isn't Midtier, you could probably use the native
Java API.
The Midtier, last time I checked, is 99.9% native library free.
Curiously, the only part of the native library it still uses is checking
the M
You can not classload a 32-bit native library (JNI) using a 64-bit JVM, and
vice versa. You will be constrained to a 32-bit JVM as long as those 32-bit
native libraries are required.
Axton
The opinions, statements, and/or suggested courses of action expressed in
this E-mail do not necessarily re
Dear listers,
I am not a Java person and would need some pointers from those who wrote Java
API in the past.
The company integrated with some supplier's application using web services.
They got into all kind of problems so they decided to go it the Java API route.
Someone from the supplier'
12 matches
Mail list logo
