I want to load the results of a form into a new window and then
redirect the original form page to a different location. I can do
this with a regular link using the technique described here en.wikibooks.org/wiki/Programming:WebObjects/Web_Applications/
Development/Examples/Open_Link_in_New_Win
Has anyone looked into exactly what the problem is with deploying a
war with framework embedding? It APPEARS that you either have an
exploded war (SSDD) and embedding works fine, or you have a war file
and you have to install WO frameworks outside of the war, but you
can't have both? I'm
On Dec 5, 2007, at 12:42 PM, Andrew Lindesay wrote:
Hello;
I am a bit confused about "refuse new sessions". This works for
the built-in component request handler just fine, but for my own
request handler I don't think I fully understand the workings.
I have one instance for which I have
Hello;
I am a bit confused about "refuse new sessions". This works for the
built-in component request handler just fine, but for my own request
handler I don't think I fully understand the workings.
I have one instance for which I have "refuse new sessions" turned on,
but the instance is
On Dec 5, 2007, at 6:53 PM, Gaastra Dennis - WO Lists wrote:
Hi Chuck,
As always, you are the king! Yes that did it.
That, for the record, is the Wonder style or my slightly altered
variation of it. As always, Wonder makes your life easier.
:-)
Do we still need the following two:
So does that mean we should not have used Pascal's script? I think
he did a very nice job for the community with it.
What now? Should we re-run the script with different templates; or
should we change something else?
Pascal's script is great and saves a ton of time ... It works just as
well w
Hi Chuck,
As always, you are the king! Yes that did it.
Do we still need the following two:
On Dec 5, 2007, at 6:33 PM, Gaastra Dennis - WO Lists wrote:
Dear List,
I think we do you the wonder-style, as instructed in Pascal's script.
No, that is the old style.
All pattern sets have not been modified, except for
"resources.include.patternset", we added "/Fonts/**"
Here is a co
This is why I only ever recommend using the Wonder-based project
layout (which is actually the default for all WO app and framework
projects in WOLips as of several builds ago).
I would take a step back from your problem and simplify simplify
simplify. Make a new project using one of the s
Hello Dennis;
OK sorry I misunderstood. Probably not what you want to hear, but
maybe have a look at the standard ant documentation as there are
details on the "fileset/patternset/..." stuff in there and you may be
able to move things into place? I did have this frustration to start
wit
On Dec 5, 2007, at 5:58 PM, Gaastra Dennis - WO Lists wrote:
Dear List,
After 6 hours, still no result. Why can't it just work like with
XCode???
It does, if you use the Wonder style projects.
1. The "Resources" folder has no R, but the Fonts folder does.
2. Added ... to
build.xml.
3
Dear List,
After 6 hours, still no result. Why can't it just work like with
XCode???
1. The "Resources" folder has no R, but the Fonts folder does.
2. Added ... to build.xml.
3. In the "build" subdirectory, everything is fine.
4. The installed framework now has no Fonts directory at all
Hello Dennis;
I had the same problem and added a section for each bunch of
resources so they end up flattened;
cheers.
Yes, we used the import script from Pascal with the Wonder
templates. Everything else seemed to work OK, except for the
Resources: somehow, they
Yes, we used the import script from Pascal with the Wonder templates.
Everything else seemed to work OK, except for the Resources: somehow,
they would always end up within WebServerResources, and not the top-
level one.
With Kind Regards,
Dennis Gaastra, M.B.A.[sfu.ca], B.Sc.[ubc.ca]
Chief
i think you've probably added the "Resources" directory to resources,
instead of just it's contents. Wonder builds create a resources
directory and stuff inside it everything you flag to "include as a
resource". so if you tell it to include the resource dir as a
resource, it pops that insid
Hi Simon,
Yes, originally after the Xcode import, there was a Resources
directory under WebServerResources; so then we moved the contents
(Fonts/) into the top level Resources directory (the one with
Properties), and deleted the one in the WebServerResources. In our
workspace, we just hav
Or he had not used the Wonder version and is getting the flattening
effect of the standard build (which I will try to not say nasty
things about no matter how much it might deserve it as I have no time
to fix it).
What does the woframework task part of your build file look like?
Chuck
On
i think you've probably added the "Resources" directory to resources,
instead of just it's contents. Wonder builds create a resources
directory and stuff inside it everything you flag to "include as a
resource". so if you tell it to include the resource dir as a
resource, it pops that insid
Dear List,
In our Eclipse project, we have a "Fonts" directory within the
"Resources" directory.
When we look at the "build" directory, there correctly appears to be
"ABC.framework/Resources/Fonts" containing the fonts.
However, when we do the ant Install to "/Library/Frameworks", we get
th
The fix has been committed to
http://houdah-webobjects-frameworks.googlecode.com/svn/trunk/HoudahEOAccess/src/com/houdah/eoaccess/qualifiers/ExistsInRelationshipQualifierSupport.java
Pierre
On Dec 5, 2007, at 11:39 PM, David Holt wrote:
Dear Pierre,
I had the entire eocontrol framework added
I have relied on WOLongResponsePage for situations where I have
time-consuming calculations or database processes whose progress I
can track.
I'm now dealing with a page that reports on data from surveys, some
of which can be very long. Obtaining the raw data doesn't seem to be
a problem--tha
On Dec 5, 2007, at 2:50 PM, Pierce T. Wetter III wrote:
I'd guess that it is a problem with NSBundle finding the classes
in it. Try logging out the various things that NSBundle will tell
you. And do that before the above code and see if just calling
those methods makes a difference. Cal
I'd guess that it is a problem with NSBundle finding the classes in
it. Try logging out the various things that NSBundle will tell
you. And do that before the above code and see if just calling
those methods makes a difference. Calling NSBundle.mainBundle()
might be enough. I recall hav
I committed a fix to Wonder this past Sunday for what I believe was
the same exception, but I only saw it when running under a J2EE
deployment. You might try the latest build and see if you still get
this problem.
ms
On Dec 5, 2007, at 12:38 PM, Gordon Belray wrote:
Hi Chuck,
This i
1. addToBothSides() should skip the inverse if it isn't faulted.
Yes! I keep meaning to look into this .. I seem to recall there were
several attempts on the wikibook (or wodev) that show how to do this,
but they all had caveats with them. I suspect this is a slippery
change to make, bu
Dear List,
In our Eclipse project, we have a "Fonts" directory within the
"Resources" directory.
When we look at the "build" directory, there correctly appears to be
"ABC.framework/Resources/Fonts" containing the fonts.
However, when we do the ant Install to "/Library/Frameworks", we get
th
My 2¢:
The following code snippet works for me in most cases, but, it
doesn't work if the app tries to access the to-many relationship
prior to saving the changes to the database. Such access would fire
the fault which would not contain the added object because it hadn't
been saved to th
Hi David!
You don't need to grab all of the frameworks if all you want is the
qualifiers. The frameworks are geared to be a D2W replacement with
lots of extra goodies at the lower levels. Currently the whole thing
lacks a sample application to show off how to use the frameworks as a
whole
Hi Pierre,
Thanks for the reply. I was using the QualifierAdditions available at
your blog, so I am sure that the line numbers don't match with
Daniele's. Chuck sent me an updated version of that framework last
night which didn't work and gives different line numbers than the
error I repo
On Dec 5, 2007, at 9:52 AM, Pierce T. Wetter III wrote:
Problem:
TestNG isn't working for me because even though I can access the
class via Class.forName(), the bowels of WebObjects can't. I'm not
enough of a java head to know why, so I'm asking for help.
In Detail:
So I'm trying t
On 5 Dec 2007, at 17:17, Pierce T. Wetter III wrote:
...
"addToBothSidesOfRelationship"
...
It turns out to be almost never the case that you want to fetch
all "Open Tasks". It tends to be the case for us that you almost
always want to have additional qualifiers on those searches,
Problem:
TestNG isn't working for me because even though I can access the
class via Class.forName(), the bowels of WebObjects can't. I'm not
enough of a java head to know why, so I'm asking for help.
In Detail:
So I'm trying to get started with TestNG. (TestNG is a better
version of
On Dec 5, 2007, at 9:38 AM, Gordon Belray wrote:
Hi Chuck,
This is really a Wonder question and best asked on the Wonder list.
After a very, very quick look at the source, it seems that is is
something malformed that you have on the classpath:
}
Hi Chuck,
This is really a Wonder question and best asked on the Wonder list.
After a very, very quick look at the source, it seems that is is
something malformed that you have on the classpath:
} else if(jar.endsWith(".jar")) {
Hi David!
Seems like you are experiencing the same crash as Daniele.
Unfortunately the line numbers in the stack trace don't much with what
I have in the Google Code repository.
Your stack trace shows a call to
_aliasForRelatedAttributeRelationshipPath at line 99 of
ExistsInRelationshipQua
Hi Daniele,
First off: somehow the line numbers don't match up. Your stack trace
shows a call to _aliasForRelatedAttributeRelationshipPath at line 100
of ExistsInRelationshipQualifierSupport. I find 2 such calls. One at
line 119 and one at 123. Which one is it?
How come the lines don't mat
From a discussion about the danger of using
"addToBothSidesOfRelationship" as default behavior.
It turns out to be almost never the case that you want to fetch all
"Open Tasks". It tends to be the case for us that you almost
always want to have additional qualifiers on those searc
This is really a Wonder question and best asked on the Wonder list.
After a very, very quick look at the source, it seems that is is
something malformed that you have on the classpath:
} else if(jar.endsWith(".jar")) {
On Dec 5, 2007, at 8:40 AM, Pierre Bernard wrote:
Qualifier SQL generation is a very complex subject.
That is for certain!
Chuck
On Dec 5, 2007, at 5:26 PM, Daniele Corti wrote:
Hi,
Same error of David, and I've just up-to-date the houdah
frameworks with the svn checkout http://hou
Hi!
Could you please send me the relevant bit of your source as well as a
complete stack trace using the newest version of the code (so line
numbers match up)?
Chances are there are still bugs in the qualifiers. I have used them
on a couple projects. So did other people. Don't know how ma
Hi,
Same error of David, and I've just up-to-date the houdah frameworks with
the svn checkout *http*://houdah-
webobjects-frameworks.googlecode.com/svn/trunk/houdah-webobjects-frameworks-read-only
Command.
Can it be a source error?
2007/12/5, Pierre Bernard <[EMAIL PROTECTED]>:
>
> The latest ver
On 5-Dec-07, at 11:03 AM, Chuck Hill wrote:
On Dec 5, 2007, at 7:44 AM, Gordon Belray wrote:
Hi,
I'm trying to get Project Wonder integrated into an existing
application and get the following on launch:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAcces
On Dec 5, 2007, at 7:44 AM, Gordon Belray wrote:
Hi,
I'm trying to get Project Wonder integrated into an existing
application and get the following on launch:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.
ERExtensions, ERJars, JavaWOExtensions frameworks.
Gordon
On 5-Dec-07, at 10:50 AM, Daniele Corti wrote:
2007/12/5, Gordon Belray <[EMAIL PROTECTED]>:
Hi,
I'm trying to get Project Wonder integrated into an existing
application and get the following on launch:
Which frameworks did you
2007/12/5, Gordon Belray <[EMAIL PROTECTED]>:
>
> Hi,
>
> I'm trying to get Project Wonder integrated into an existing application
> and get the following on launch:
>
Which frameworks did you include?
java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(
Hi,
I'm trying to get Project Wonder integrated into an existing
application and get the following on launch:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccess
I didn't mean that modeling the inverse is something that should
"never" be done, but more that the Best Practice is to think about
the relationship, before you simply put it in the model.
One of the great things about using an EOGenerator-type tool is that
you can setup the relationship in
Am 05.12.2007 um 14:44 schrieb Mike Schrag:
It turns out to be almost never the case that you want to fetch all
"Open Tasks". It tends to be the case for us that you almost always
want to have additional qualifiers on those searches, which ends up
that you fault a HUGE (many thousands) of
Also it's an urban legend that simply faulting the objects is slow.
This is only true when you either have batch operations where you
are not really interested in the relationship but it will get
fetched because validation needs it. Or you have *huge*
relationships (say >1k objects).
For
Which may or may not be a good idea because you will fetch *every*
time you touch the relationship and this might suck a lot when used in
bindings (which you don't find via "Open Call Hierarchy") or you have
to cache it yourself but then have a bitch of a time to invalidate it
when you actu
Le 07-12-04 à 18:22, David LeBer a écrit :
On 4-Dec-07, at 6:09 PM, Owen McKerrow wrote:
Hi All,
As part of preparing to move to Eclipse we are going back and
updating our projects so they are using packages ( this is the bit
where I run and hide in shame as I have to admit we never used
I think this is a key "best practice". It is something that I
struggled with for a while, while trying to figure out why my
application was so slow. It's logical to add both relationships, but
once you understand what is happening, it is logical to leave the
heavy relationship off and use a
The latest version is at :
http://code.google.com/p/houdah-webobjects-frameworks/
Pierre
On Dec 5, 2007, at 2:58 AM, Chuck Hill wrote:
That looks familiar. Pierre and I fixed a bug in this a while
back. Are you using the current (i.e. up to date) ones from Houdah
frameworks?
Chuck
O
53 matches
Mail list logo
