Hello,
Just digging up this 2.5 year old thread...
On 18/04/2010, at 4:12 PM, Kieran Kelleher wrote:
> Alternative suggestion:
> A readonly derived column is another option to expose the PK. The advantage
> is that the the new exposed column can be used in standard EOQualifier that
> works in
D2W? If so what are your rules?
Sent from my iPad
On 2012-10-02, at 3:07 PM, Oscar González wrote:
> Hi all,
> I try it but no luck.
> I have in my ValidationTemplate.strings
> "MgeProductor_Existe" = "Ya existe un @@displayNameForEntity@@ con el mismo
> @@displayNameForProperty@@";
>
> And i
Hi all,I try it but no luck.I have in my
ValidationTemplate.strings"MgeProductor_Existe" = "Ya existe un
@@displayNameForEntity@@ con el mismo @@displayNameForProperty@@";
And in my Localizable.strings"MgeProductor.codigoInterno" =
"código";"Entity.MgeProductor" = "Productor";
And the message f
The following is just an update in case anyone stumbles upon this same problem.
Not really a full solution but perhaps useful none the less.
I was not able to get SVN+SSH in Jenkins to work on an OSX 10.6.7 system that
otherwise can access the repository via command line and Eclipse. If I manua
I had the same problem. I got the adaptor to compile by manually modifying the
/usr/sbin/apxs script. On the lines where 'libtool' is called I added "--tag
CC" to the list of arguments. That's in two places.
I am not sure why that is necessary because according to the manual libtool
should try
Hi all,I'm starting with localizables.
I need to localizable a entity name MgeProductor. I try with this.{
"MgeProductor" = "Productor"; "EntityKey.MgeProductor" = "Productor";
"Entity.name.MgeProductor" = "Productor";}
Non of this work for me.
Saludos,
Oscar.
Hi,
forget my reply to your original mail - I didn't see that you used the -target
1.4 switch and misunderstood that you wanted to actually run Java 6 class files
on 1.4.
Maik
Am 02.10.2012 um 22:29 schrieb doug andrews :
> Never mind. I've got it figured out. I had some Wonder stuff in
Am 02.10.2012 um 21:23 schrieb doug andrews :
> Is it possible to deploy an application compiled with java 6 on a machine
> running java 1.4?
> I have both Java 6 and 4 on my machine.
> I have a test application created using the Eclipse ant build while running
> java 6.
> I force the app to us
Never mind. I've got it figured out. I had some Wonder stuff in there, which
I don't think is compatible with java 1.4.
On Oct 2, 2012, at 3:23 PM, doug andrews wrote:
> Is it possible to deploy an application compiled with java 6 on a machine
> running java 1.4?
> I have both Java 6 and 4
Is it possible to deploy an application compiled with java 6 on a machine
running java 1.4?
I have both Java 6 and 4 on my machine.
I have a test application created using the Eclipse ant build while running
java 6.
I force the app to use java 1.4 when deployed by modifying the MacOS class path
Yes, I don't know if it's Axis that is old or the stuff connecting to
my app that sucks but with JAX-WS I solved the problem (of course I
had to make a proxy on apache to be able to connect to port 8080).
Now I need to find a way to make the endpoint link to the WOPort...
I'll try your suggestion b
The WO web service stuff is just a wrapper around Axis 1.4, which is a
generic java library, so I would be surprised if it wouldn't work. That
said, Axis 1.4 is quite old now, and using something newer is a good
option. The port thing doesn't matter -- 8080 is just the standard J2EE
port, but you
Hi list,
I'm trying to implement a webservice using JAX-WS after I concluded
that the app that needs to talk with mine can't speak through
WOWebServices...
All the examples I found make a webservice server by
javax.xml.ws.Endpoint.publish("http://localhost:8080/WS/NameOfService";,
implementor);
13 matches
Mail list logo
