I'd bet that is still from pre-Wonder ERX. And it was probably there
because of the move from 4.0->5.0.
Cheers, Anjo
Am 27.01.2009 um 03:36 schrieb Chuck Hill:
On Jan 26, 2009, at 6:03 PM, D Tim Cummings wrote:
String attributes called "description" are ok, and EOGenericRecord
is ok with
On 27/01/2009, at 5:11 PM, Chuck Hill wrote:
FireBug and FireFox. Take a look at the Net log. You can see all
the traffic back and forth. Often these things came in an Ajax
update and so don't show up in the page source (as originally
loaded). Look at the response content in FireBug and
On Jan 26, 2009, at 10:37 PM, Paul Hoadley wrote:
On 27/01/2009, at 1:10 PM, Chuck Hill wrote:
On Jan 26, 2009, at 5:25 PM, Paul Hoadley wrote:
On 27/01/2009, at 7:55 AM, Chuck Hill wrote:
Should this also work in Application.handleException()? I've
got this:
public WOResponse handl
On 27/01/2009, at 1:10 PM, Chuck Hill wrote:
On Jan 26, 2009, at 5:25 PM, Paul Hoadley wrote:
On 27/01/2009, at 7:55 AM, Chuck Hill wrote:
Should this also work in Application.handleException()? I've got
this:
public WOResponse handleException(Exception anException,
WOContext aContex
I just remembered I started backing up to my iDisk using the Backup
app after my time machine backup disk died (Doh!). Just did a backup
this morning. Restored it and everything is functioning again.
Without the suggestions of restoring from backup and using version
control I'd probably
As luck would have it, my backup disk stopped functioning a couple
days ago. Would creating a new workspace and importing from the old
one possibly work?
You can reimport, but you'll have to rebuild your dependencies.
Incidentally, I'll reiterate that even single developer shops should
10
It seems like there might be some problems from the last few days.
You might want to hold off if you can...
On Jan 26, 2009, at 7:26 PM, Jeff Schmitz wrote:
Guess I could give it a try (new version), but my track record on
doing this is not good (as you probably know), especially since I'
Guess I could give it a try (new version), but my track record on
doing this is not good (as you probably know), especially since I'm
going to have to upgrade my deployment machine too. Maybe I'll try
the new "all in one" installer.
On Jan 26, 2009, at 9:20 PM, Chuck Hill wrote:
On Ja
On Jan 26, 2009, at 7:15 PM, Jeff Schmitz wrote:
As luck would have it, my backup disk stopped functioning a couple
days ago. Would creating a new workspace and importing from the old
one possibly work?
I'd doubt it. New Hotness upgrades your .classpath file (and I think
a couple of ot
As luck would have it, my backup disk stopped functioning a couple
days ago. Would creating a new workspace and importing from the old
one possibly work?
On Jan 26, 2009, at 9:10 PM, Chuck Hill wrote:
On Jan 26, 2009, at 7:05 PM, Jeff Schmitz wrote:
Hello,
I accidentally opened my WO
On Jan 26, 2009, at 7:05 PM, Jeff Schmitz wrote:
Hello,
I accidentally opened my WOLips projects workspace with Eclipse
3.4, and now when I try to run under Eclipse 3.3 I get:
Exception in thread "main" java.lang.NoClassDefFoundError: er/
extensions/appserver/ERXApplication
Also, I no
Hello,
I accidentally opened my WOLips projects workspace with Eclipse
3.4, and now when I try to run under Eclipse 3.3 I get:
Exception in thread "main" java.lang.NoClassDefFoundError: er/
extensions/appserver/ERXApplication
Also, I no longer have a WO Frameworks "folder" in my project,
On Jan 26, 2009, at 5:25 PM, Paul Hoadley wrote:
On 27/01/2009, at 7:55 AM, Chuck Hill wrote:
Should this also work in Application.handleException()? I've got
this:
public WOResponse handleException(Exception anException,
WOContext aContext) {
AMErrorPage errorPage = (AMErrorPage)
On Jan 26, 2009, at 6:03 PM, D Tim Cummings wrote:
String attributes called "description" are ok, and EOGenericRecord
is ok with relationships called "description". However
ERXGenericRecord has a method description() which returns toString()
hence you can't call a relationship "descriptio
String attributes called "description" are ok, and EOGenericRecord is
ok with relationships called "description". However ERXGenericRecord
has a method description() which returns toString() hence you can't
call a relationship "description" or it tries to override the return
type and gives
On 27/01/2009, at 7:55 AM, Chuck Hill wrote:
Should this also work in Application.handleException()? I've got
this:
public WOResponse handleException(Exception anException, WOContext
aContext) {
AMErrorPage errorPage = (AMErrorPage)
pageWithName(AMErrorPage.class
On Jan 26, 2009, at 7:24 PM, Mike Schrag wrote:
I ditched subversive and went back to subclipse ... I'm a happier
person, mostly.
Seconded; subversive is/was wonky in bad ways
___
Do not post admin requests to the list. They will be ignored.
W
I've trashed my copy of eclipse, downloaded a new copy and re-
installed everything from scratch and re-imported my old projects
already. Sorry.
On Jan 26, 2009, at 10:58 PM, Mike Schrag wrote:
Jan 26 08:00:46 Iron [0x0-0x69069].org.eclipse.eclipse[1204]:
java.lang.NullPointerException
Jan
On Jan 26, 2009, at 2:34 PM, Mike Schrag wrote:
Entity Modeler USED to (maybe still does) warn about this ... If you
look at EOEnterpriseObject, there's:
String eoDescription() -- Returns a String that describes the
receiver.
so maybe it was renamed? I think I dodged "description" for a
Do I see here a nice feature for the WOLips modeler? A new warning
like "the attribute name may cause conflits with all the
underlying stuff"?
We already do have a bunch of these, actually.
ms
___
Do not post admin requests to the list. They will
Hi All,
I would like to use EOF to extend an existing axis application
deployed with tomcat. Has anyone done this?
At the moment I get this exception in the deployed app:
Caused by: java.lang.ExceptionInInitializerError
at
com
.webobjects
.eoaccess.EOModelGroup.modelGroupForLoadedBu
I ditched subversive and went back to subclipse ... I'm a happier
person, mostly.
ms
On Jan 26, 2009, at 6:15 PM, Atli Páll Hafsteinsson wrote:
I just spent this morning setting up a fresh eclipse+wolips and
subversive
.. Freaking svn connector took me almost allmorning before I checked
t
Mike Schrag wrote:
I think I dodged "description" for a really long time until someone
said "you don't have to" a year or so ago ... probably was Chuck.
Pre-Wonder, I happily created entity() relationships in three
projects/EOs. Post-Wonder, not so happily renamed them to entitee()
which o
"Warning: Extended use of WebObjects may cause head pain and
dizziness."?
On Jan 26, 2009, at 2:59 PM, Miguel Arroz wrote:
Hi!
Do I see here a nice feature for the WOLips modeler? A new warning
like "the attribute name may cause conflits with all the
underlying stuff"?
Yours
Migue
I just spent this morning setting up a fresh eclipse+wolips and subversive
.. Freaking svn connector took me almost allmorning before I checked the
right combination of comboxes in the eclipse install manager .. G... !
On 1/26/09 8:26 PM, "Chuck Hill" wrote:
>
> On Jan 26, 2009, at 12:22 P
Hi!
Do I see here a nice feature for the WOLips modeler? A new warning
like "the attribute name may cause conflits with all the
underlying stuff"?
Yours
Miguel Arroz
On 2009/01/26, at 21:49, Chuck Hill wrote:
That depends on the plug-in, not all of them quote.
Chuck
On Jan 26,
Entity Modeler USED to (maybe still does) warn about this ... If you
look at EOEnterpriseObject, there's:
String eoDescription() -- Returns a String that describes the receiver.
so maybe it was renamed? I think I dodged "description" for a really
long time until someone said "you don't have
On 27/01/2009, at 8:24 AM, Ken Anderson wrote:
Doesn't it still? I NEVER use it :)
I believe it's still the case... unless that was Entity Modeler
complaining. Can't recall.
On Jan 26, 2009, at 4:22 PM, Mark Morris wrote:
Back in the old days, an attribute named "description" would caus
Hi Henrique,
are you able to share your experiences with wars? I'm not familiar
with this.
On 27/01/2009, at 7:38 AM, William Hatch wrote:
On Jan 26, 2009, at 8:15 AM, Lachlan Deck wrote:
Just testing this, it appears you might need to configure the pom
for the resources:
war
That depends on the plug-in, not all of them quote.
Chuck
On Jan 26, 2009, at 1:43 PM, JR Ruggentaler wrote:
The JDBC API provides:
DatabaseMetaData dbMetaData = connection.getMetaData();
dbMetaData.getIdentifierQuoteString();
to quote reserved words. I think EOF uses the ap
The JDBC API provides:
DatabaseMetaData dbMetaData = connection.getMetaData();
dbMetaData.getIdentifierQuoteString();
to quote reserved words. I think EOF uses the appropriate quotes based
on the reserved words in the model.
JR
On Jan 26, 2009, at 3:36 PM, Ken Anderson wrote
And don't use 'desc' instead - messes up Oracle! I always use
'descr' :)
On Jan 26, 2009, at 4:30 PM, Mark Morris wrote:
That was (is) the NSObject's version of toString, so I think it
might be okay now that we're in Javaland. But I never use it
either, out of habit
-- Mark
On Ja
That was (is) the NSObject's version of toString, so I think it might
be okay now that we're in Javaland. But I never use it either, out of
habit
-- Mark
On Jan 26, 2009, at 3:24 PM, Ken Anderson wrote:
Doesn't it still? I NEVER use it :)
On Jan 26, 2009, at 4:22 PM, Mark Morris wro
On Jan 23, 2009, at 7:15 PM, Paul Hoadley wrote:
Hi Chuck,
On 20/01/2009, at 7:09 AM, Chuck Hill wrote:
...
if (AjaxUtils.isAjaxRequest(aContext.request()))
{
AjaxUtils.redirectTo(errorPage);
return errorPage.context().response();
}
r
Doesn't it still? I NEVER use it :)
On Jan 26, 2009, at 4:22 PM, Mark Morris wrote:
Back in the old days, an attribute named "description" would cause
you grief. ;-)
-- Mark
On Jan 25, 2009, at 9:50 AM, James Cicenia wrote:
Don't feel so bad. I once named a component "Request". Took me
Back in the old days, an attribute named "description" would cause you
grief. ;-)
-- Mark
On Jan 25, 2009, at 9:50 AM, James Cicenia wrote:
Don't feel so bad. I once named a component "Request". Took me a
whole day to finally figure out it was the name of the component
that fubar'd it.
On Jan 23, 2009, at 11:11 AM, Kieran Kelleher wrote:
On one slow G4 xserve, I have had situation about once month
whereby I get an email (presumably from wotaskd) from the specific
server reporting one or two "Deaths" on an instance running on that
machine. I look at the time of the email
Bill
On Jan 26, 2009, at 8:15 AM, Lachlan Deck wrote:
Just testing this, it appears you might need to configure the pom
for the resources:
war
MavenWOApp
src/main/resources
On Jan 26, 2009, at 12:22 PM, Michael Welles wrote:
Preferences -> Team SVN -> Client -> "Java HL (JNI) Not Available"
Yes, it still says "Not Available", but this is eclipse, and it's
lying
ROFL!
Yes! Been there...
--
Chuck Hill Senior Consultant / VP Development
Practi
I posted this earlier to an internal list, and it was suggested that
it might be of help to some if I reposted here. Apologies in advance
if its not
How to setup Eclipse + Subclipse + JavaHL for use with svn+ssh
repositories via macports on OSX
-
Jan 26 08:00:46 Iron [0x0-0x69069].org.eclipse.eclipse[1204]:
java.lang.NullPointerException
Jan 26 08:00:46 Iron [0x0-0x69069].org.eclipse.eclipse[1204]: at
org
.objectstyle
.wolips
.wizards.EOModelCreationPage.getProject(EOModelCreationPage.java:216)
Jan 26 08:00:46 Iron [0x0-0x69069].org
On 26/01/2009, at 4:21 PM, William Hatch wrote:
Thanks Lachlan,
So our pom's, web.xml's and build.properties both look good. I'm
curious if you have the same issue when deploying your resulting war.
As I mentioned, I don't deploy to servlets / war. But ...
I noticed you're also using 2.0.
So what if we continue on nightly? Is it going through changes not
recommended for production use? Can you warns us in advance if that's
the case?
Regards,
Henrique Gomes
___
Do not post admin requests to the list. They will be ignored.
Webobj
43 matches
Mail list logo
