Hi list,
as there are some people from Apple reading this mailing list I will just drop
in my question and hoping to get any response.
Currently working with the different JDBC adaptors of Wonder I stumbled on the
deprecation warnings of the classes
com.webobjects.eoaccess.EOSchemaGeneration
Hi
Very simple question about WOLips and Eclipse.
Is there a way to click to add a WOElement and for the name to be auto
populated so I don't have to add a new name for every WOTextField I
add to large forms?
WOBuilder used to just increment?
Thanks
GIno
Gino
If you use inline bindings, ognl?, then you don't need names. I actually
dislike the auto increment names, leads to maintenance problems in the future.
Sent from my iPad
On Jan 19, 2012, at 4:09 AM, Gino Pacitti ginok...@mac.com wrote:
Hi
Very simple question about WOLips and
Le 2012-01-18 à 17:53, Daniel Beatty a écrit :
LOL,
That is the funny thing isn't it. If Apple could make a quick, nearly
effortless buck off of it, they would not hesitate. Even if it involved a
little investment, but a good return Apple would be in.
With the amount of cash they make
Good morning,
I added Twitter notifications on GitHub for Wonder and WOLips, and also for
when WOLips builds are done on Jenkins (on wocommunity.org), so if you want to
get those notifications on Twitter, please follow @WOComNotifs
And I just saw that the notifications for Wonder to the
Hi All...
I have been building a project in WOLips and now coming to do a
deployment...
But although it compiles and runs in Eclipse it does not want to start
using WOMonitor?
Is there any sort of special config to do ?
GIno
___
Do not post
You did build the .woa with Ant (in Eclipse, right-click on project - WOLips
Ant Tools - Install)? If so, if the app don't start, it's probably file
permissions. What is the deployment platform? Did you set a log in Monitor? If
so, what the log is saying?
(We really need an easier way of
27 organizations so far, last year we had 86. I'm sure we can beat that?
Good morning everyone,
The annual surveys are now available:
Organization (e.g., your business answers):
https://www.survs.com/survey/XLRMBX7JB7
Individual (e.g., your personal answers) :
http://developer.apple.com/legacy/mac/library/documentation/InternetWeb/Reference/WO542Reference/com/webobjects/eoaccess/synchronization/EOSchemaSynchronization.html
It's there. It's in the interfaces. Just do a command-shift-T and you'll find
it.
Ramsey
On Jan 19, 2012, at 2:06 AM, Johann
The individual survey is jumping from page 1 to page 3.
Ramsey
On Jan 17, 2012, at 7:51 AM, Pascal Robert wrote:
Good morning everyone,
The annual surveys are now available:
Organization (e.g., your business answers):
https://www.survs.com/survey/XLRMBX7JB7
Individual (e.g., your
That's normal, page 2 is for people who have less than one year of WO
experience (e.g., you go to page 2 if you answer Yes on the first page).
The individual survey is jumping from page 1 to page 3.
Ramsey
On Jan 17, 2012, at 7:51 AM, Pascal Robert wrote:
Good morning everyone,
The
yeah, the EOSchemaSynchronization is there I know, it's the (new)
EOSynchronizationFactory that is missing
Am 19.01.2012 um 16:20 schrieb Ramsey Gurley:
it's just a typo in the @deprecated tag .. EOSchemaSynchronizationFactory was
the replacement in 5.4.x
ms
On Jan 19, 2012, at 10:35 AM, Johann Werner wrote:
yeah, the EOSchemaSynchronization is there I know, it's the (new)
EOSynchronizationFactory that is missing
Am 19.01.2012 um 16:20
Thanks for the clarification, Mike!
jw
Am 19.01.2012 um 16:37 schrieb Mike Schrag:
it's just a typo in the @deprecated tag .. EOSchemaSynchronizationFactory was
the replacement in 5.4.x
ms
On Jan 19, 2012, at 10:35 AM, Johann Werner wrote:
yeah, the EOSchemaSynchronization is there
To close the move of everything to wocommunity.org and GitHub, Jira on
issues.objectstyle.org will be shutdown next monday (Jan. 23). If you have
issues on Jira that are still valid, please recreate them on GitHub.
Same thing for the woproject-dev mailing list. Since almost everyone is using
Still very strange...
I can run the app from command line and it goes through start up
listing out all the initialization stuff and it ends with Waiting for
Requests ... so It should have compiled fine...
Yet it will not start in JavaMonitor?
Anyone else has had the same in the past and
Hi ...
Is there a way to get EOGenerator to not create this syntax:
public static NSArrayBordereau fetchAllBordereaus
Error: The type NSArray is not generic; it cannot be parameterized
with arguments
Bordereau
How do I get it to do just this:
public static NSArray fetchAllBordereaus
Le 2012-01-19 à 13:47, Gino Pacitti a écrit :
Still very strange...
I can run the app from command line and it goes through start up listing out
all the initialization stuff and it ends with Waiting for Requests ... so It
should have compiled fine…
You are starting it by command line
That means you are using the Wonder templates without using Wonder, or having a
wrongly ordered class path. Do you have ERExtensions and ERJars in this project?
Hi ...
Is there a way to get EOGenerator to not create this syntax:
public static NSArrayBordereau fetchAllBordereaus
Error:
Yes... I do... both
What is the correct order?
Thanks for your help Pascal :)
On 19 Jan 2012, at 18:53, Pascal Robert wrote:
That means you are using the Wonder templates without using Wonder,
or having a wrongly ordered class path. Do you have ERExtensions and
ERJars in this project?
ERExtensions and ERJars should be over the core WO frameworks:Yes... I do... bothWhat is the correct order?Thanks for your help Pascal :)On 19 Jan 2012, at 18:53, Pascal Robert wrote:That means you are using the Wonder templates without using Wonder, or having a wrongly ordered class path. Do you
They don't need to be checked, checking is to tell to export the libraries.
That's useful if you want to export JAR archives that you have in frameworks so
that other projects see them in Eclipse. No need to do that for WO frameworks.
Thanks Pascal
Do they need to be checked?
Why are
Le 2012-01-18 à 17:53, Daniel Beatty a écrit :
LOL,
That is the funny thing isn't it. If Apple could make a quick, nearly
effortless buck off of it, they would not hesitate. Even if it involved a
little investment, but a good return Apple would be in.
With the amount of cash
How would you later update your repository with the latest changes from
github.com? Sorry - git newbie here. Just trying to wrap my head around how
to manage Wonder source changes.
- Patrick
On Dec 13, 2011, at 10:23 PM, Kieran Kelleher wrote:
FYI,
If you want to have a simple
Patrick
I think you would just do a pull from the remote repository.
--
Paul Yu
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Thursday, January 19, 2012 at 2:49 PM, Patrick Robinson wrote:
How would you later update your repository with the latest changes from
github.com
git fetch origin
git merge origin/master
How would you later update your repository with the latest changes from
github.com? Sorry - git newbie here. Just trying to wrap my head around how
to manage Wonder source changes.
- Patrick
On Dec 13, 2011, at 10:23 PM, Kieran Kelleher
A friendly reminder for your friendly WOWODC organizer. We need more people to
present at WOWODC 2012! You can see the list of topics and suggestions here:
http://wocommunity.org/apps/WebObjects/WOWODC.woa/ra/sessions/listPapers.html
Don't forget, WOWODC 2012 is June 30, July 1st and 2nd
Patrick,
... or you can do:
$ git pull
which does the exact same thing as doing the two commands given below by
Pascal.
Regards, Kieran
PS. Come to WOWODC - there will be a presentation on using git there.
On Jan 19, 2012, at 3:10 PM, Pascal Robert wrote:
git fetch origin
git merge
I don't think the Wonder source BUILD.txt file is correct (or at least, it's
not sufficient). It says:
3. A wobuild.properties file should be placed in, on Mac OS X, the ~/Library
directory.
You can also symlink ~/Library/wobuild.properties to your existing
~/Library/Application
If you don't know what to change, create an Issue for it here please:
https://github.com/projectwonder/wonder/issues
On Jan 19, 2012, at 4:23 PM, Patrick Robinson wrote:
I don't think the Wonder source BUILD.txt file is correct (or at least, it's
not sufficient). It says:
3. A
com.webobjects.appserver._private.WOComponentRequestHandler: Exception
occurred while handling request:
sun.misc.InvalidJarIndexException: Invalid index
[2012-1-19 18:6:30 CST] WorkerThread1 sun.misc.InvalidJarIndexException:
Invalid index
at
Hi:
We have an application that has been running for many years. In the
application class' constructor we called:
this.setPageRefreshOnBacktrackEnabled(false);
We discovered an issue that caused data loss. The issue was that when a
user saved a form and then pressed the browsers refresh
Le 2012-01-19 à 14:29, Johnny Miller a écrit :
Le 2012-01-18 à 17:53, Daniel Beatty a écrit :
LOL,
That is the funny thing isn't it. If Apple could make a quick, nearly
effortless buck off of it, they would not hesitate. Even if it involved a
little investment, but a good return
this.setPageRefreshOnBacktrackEnabled(false);
All this setting actually does is change the response headers like Expires
and Cache-Control, etc which browsers use to determine whether a page from
the cache can be used instead of contacting the server. You can set these
headers on the response
34 matches
Mail list logo
