Hola Chuck!
On Jul 4, 2007, at 11:30, Chuck Hill wrote:
On Jul 4, 2007, at 9:12 AM, Ricardo Strausz wrote:
To have full access to the model (to the database) trough a service...
I am thinking in an intranet, where security is not issue... well it
is, but it can be handled.
This may be the
On Jul 4, 2007, at 9:12 AM, Ricardo Strausz wrote:
To have full access to the model (to the database) trough a service...
I am thinking in an intranet, where security is not issue... well
it is, but it can be handled.
This may be the simplest way to connect a desktop app to a database...
I k
To have full access to the model (to the database) trough a service...
I am thinking in an intranet, where security is not issue... well it
is, but it can be handled.
This may be the simplest way to connect a desktop app to a database...
I know, it has its problems (e.g., most of the logic goes
On 04.07.2007, at 09:02, Ricardo Strausz wrote:
Apparently, it is not trivial (at least not easy) to publish an
EOEditingContex trough a web service (see below)
And in my opinion, it should be even harder ... why would someone
want to publish an EOEditingContext? Sounds like a very terrible
Why would you want to expose an editing context through a web
service? That seems like the wrong thing to even _want_ to do.
Chuck
On Jul 4, 2007, at 8:02 AM, Ricardo Strausz wrote:
Hola!
Apparently, it is not trivial (at least not easy) to publish an
EOEditingContex trough a web servic
Hola!
Apparently, it is not trivial (at least not easy) to publish an
EOEditingContex trough a web service (see below), nor a subclass of
it, so i decided to do so by "wrapping" such an object into one of
mine...
it works, but it is more tedious since I have to "bypass" each used
method..
On 03/07/2007, at 7:50 AM, Ricardo Strausz wrote:
public class BAEditingContext extends EOEditingContext {
public BAEditingContext(){
super();
}
public int test(int n){
return n;
}
}
Nothing wrong there. But...
and I a
Something is wrong...
my class looks like:
public class BAEditingContext extends EOEditingContext {
public BAEditingContext(){
super();
}
public int test(int n){
return n;
}
}
and I am publishing it trough
public Applica
Cool... I'll give it a try, and let you all know.
Gracias,
Dino
On Jul 2, 2007, at 4:09 PM, Kieran Kelleher wrote:
Call super with matching args in your constructors when subclassing
anything. For example:
public class MyEditingContext extends ERXEC {
public MyEditingContext(EO
Call super with matching args in your constructors when subclassing
anything. For example:
public class MyEditingContext extends ERXEC {
public MyEditingContext(EOObjectStore anObjectStore) {
super(anObjectStore);
}
public MyEditingContext() {
supe
MyEditingContext extends EOEditingContext
EOEditingContext ec = new MyEditingContext();
if you are using Wonder, you need to examine the ERXEC factory
and make your own factory to return your subclass of ERXEC. Specify
the custom factory in Properties somewhere .. just poke around
And how do you manage it?
simply calling to super?
can you please give me an example?
On Jul 2, 2007, at 3:33 PM, Simon McLean wrote:
We have a subclass to enable us to limit what the default editing
context can and can't do and haven't had any problems.
Simon
On 2 Jul 2007, at 21:17, Ricar
We have a subclass to enable us to limit what the default editing
context can and can't do and haven't had any problems.
Simon
On 2 Jul 2007, at 21:17, Ricardo Strausz wrote:
Hola!
What is the best practice to subclass the EOEditingContext (besides
not subclassing at all)?
Some experien
Hola!
What is the best practice to subclass the EOEditingContext (besides
not subclassing at all)?
Some experience on that?
Dino
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lis
14 matches
Mail list logo
