Am 02.02.2011 um 06:21 schrieb Paul Hoadley:
SuccessTextEmail component =
ERXApplication.erxApplication().pageWithName(SuccessTextEmail.class);
This will pollute the current context. Try
ERXApplication.erxApplication().pageWithName(SuccessTextEmail.class,
(WOContext)
On 2011-01-28, at 9:02 PM, Pascal Robert wrote:
Le 2011-01-28 à 19:15, Chuck Hill a écrit :
Hi Kevin,
On Jan 28, 2011, at 3:54 PM, Kevin Hinkson wrote:
Hi,
I'm hoping someone can help me with this problem.
Let's say I have a Person object. How would I go about handling a GET
Hello Chuck,
With JavaERJDBCAdaptor or the default JavaJDBCAdaptor, the result is the same,
it doesn't conform to the inheritance modeled in EntityModeler.
I've got to check into ERExtensions if I can find something.
I understand not everyone is using Horizontal Inheritance, but I must not be
This sounds really familiar ... I think it was a bug in 5.4.3.
ms
On Feb 2, 2011, at 12:46 PM, Dev WO wrote:
Hello Chuck,
With JavaERJDBCAdaptor or the default JavaJDBCAdaptor, the result is the
same, it doesn't conform to the inheritance modeled in EntityModeler.
I've got to check into
Hi Xavier,
Can you paste the .plist files for the three Entities (the super and two
subclasses) into this email? I'm suspecting that there maybe something wrong
with the way it is modeled...
What if you manually create the database tables and the sequence instead of
letting EntityModeler
Hi Chuck,
As explained in the email below, I have implemented AjaxTabbedPanel
and AjaxTabbedPanelTab 's, in each Tab I am loading a component page
and from that page I am navigating to the next page using
AjaxSubmitButton action. From the first page I am able to
successfully navigate to
What you are doing is not something that I have used the AjaxTabbedPanel for,
nor something I expected it to be used for. I suspect the problem is in your
code, but if you do find a bug in the AjaxTabbedPanel source, patches are
welcome.
This sounds really familiar ... I think it was a bug in 5.4.3.
OK, and as I wouldn't hold my breath for 5.4.4 is there a way to fix it:)
Xavier
ms
On Feb 2, 2011, at 12:46 PM, Dev WO wrote:
Hello Chuck,
With JavaERJDBCAdaptor or the default JavaJDBCAdaptor, the result is the
Sure Dave, here they are:
parent entity
{
attributes = (
{allowsNull = N; name = id; prototypeName = id; },
{allowsNull = Y; columnName = name; name = name; prototypeName =
varchar255; }
);
attributesUsedForLocking = (id);
className =
On Feb 2, 2011, at 12:36 PM, Dev WO wrote:
This sounds really familiar ... I think it was a bug in 5.4.3.
OK, and as I wouldn't hold my breath for 5.4.4 is there a way to fix it:)
It can probably be fixed in Wonder. But first you have to identify where the
problem is and what the fix is.
On Feb 1, 2011, at 9:21 PM, Paul Hoadley wrote:
Hi Chuck,
On 02/02/2011, at 2:40 PM, Chuck Hill wrote:
You can also use the JS AMD.close(); to close it. You should not NEED to
do this, but it may provide a clue as to what is or is not wrong.
I've added that to the 'onComplete'
see what entity.primaryKeyRootName() returns for each of the entities involved
...
actually on your abstract entity, did you set an external name? make sure you
set that -- external name on the root entity is what is used in 5.4.3 to
determine what sequence to generate.
ms
On Feb 2, 2011, at
see what entity.primaryKeyRootName() returns for each of the entities
involved ...
actually on your abstract entity, did you set an external name? make sure you
set that -- external name on the root entity is what is used in 5.4.3 to
determine what sequence to generate.
I was about to
It is called Table Name in Entity Modeler:
PastedGraphic-1.pdf
Description: Adobe PDF document
On Feb 2, 2011, at 12:56 PM, Dev WO wrote:
see what entity.primaryKeyRootName() returns for each of the entities
involved ...
actually on your abstract entity, did you set an external
OK, I tried this actually (even if I don't like that because it creates un-used
tables I have to clean;)), but still got the wrong inheritance.
So maybe not a winner Chuck;)
But I would have hoped for;)
Another player? same player shoot again?
Xavier
It is called Table Name in Entity
On Feb 2, 2011, at 1:03 PM, Dev WO wrote:
OK, I tried this actually (even if I don't like that because it creates
un-used tables I have to clean;)),
Some databases (FrontBase) need this table as the sequence is attached to it.
but still got the wrong inheritance.
So maybe not a winner
i still would like to see what entity.primaryKeyRootName returns for each ... i
don't recall what the impl was in 5.4.3 and I don't have it checked out at the
moment, but i'm pretty sure that method is the only thing that matters here.
ms
On Feb 2, 2011, at 4:56 PM, Chuck Hill wrote:
On
Hi Xavier,
Hmmm. As a complete aside to the SQL generation issue, are you _sure_ you need
inheritance for this?
In your app, what happens if an employee wants to buy something from you? They
can't be both a customer and an employee. Don't make the mistake of thinking
you can change change
On 03/02/2011, at 8:59 AM, Mike Schrag wrote:
i still would like to see what entity.primaryKeyRootName returns for each ...
i don't recall what the impl was in 5.4.3 and I don't have it checked out at
the moment, but i'm pretty sure that method is the only thing that matters
here.
The
On Feb 2, 2011, at 5:33 PM, Lachlan Deck wrote:
On 03/02/2011, at 8:59 AM, Mike Schrag wrote:
i still would like to see what entity.primaryKeyRootName returns for each
... i don't recall what the impl was in 5.4.3 and I don't have it checked
out at the moment, but i'm pretty sure that
Yeah, that's it. For 5.4.3, that would fix this problem.
ms
On Feb 2, 2011, at 8:38 PM, Chuck Hill wrote:
On Feb 2, 2011, at 5:33 PM, Lachlan Deck wrote:
On 03/02/2011, at 8:59 AM, Mike Schrag wrote:
i still would like to see what entity.primaryKeyRootName returns for each
... i
My team is testing a WO application on a Linux server that has worked great on
OSX for years. We are being hit by the known threadsafe issue of
SimpleDateFormat corrupting our data feed. We found this through exceptions
being thrown and logged.
We have corrected the issue by wrapping that class
How can we identify non-threadsafe classes without waiting for an exception
or data error?
you can't, really ... i would say that the majority of classes probably AREN'T
thread-safe and work your way back as you prove otherwise.
ms ___
Do not post
On Feb 2, 2011, at 6:56 PM, Mike Schrag wrote:
How can we identify non-threadsafe classes without waiting for an exception
or data error?
you can't, really ... i would say that the majority of classes probably
AREN'T thread-safe and work your way back as you prove otherwise.
That is my
Hi David,
Hi Xavier,
Hmmm. As a complete aside to the SQL generation issue, are you _sure_ you
need inheritance for this?
In your app, what happens if an employee wants to buy something from you?
They can't be both a customer and an employee. Don't make the mistake of
thinking you
Hello Lachlan,
On 03/02/2011, at 8:59 AM, Mike Schrag wrote:
i still would like to see what entity.primaryKeyRootName returns for each
... i don't recall what the impl was in 5.4.3 and I don't have it checked
out at the moment, but i'm pretty sure that method is the only thing that
26 matches
Mail list logo
