Perfect, thanks Lachlan:)
On 02/07/2007, at 6:56 PM, WO Dev wrote:
I was talking about how to make the ant file correct the
permission on build, not which file to change the permission.
For example an sample ant file that change the permission:)...
until it is fixed in WOLips;)
Ahh, oka
On 02/07/2007, at 6:56 PM, WO Dev wrote:
I was talking about how to make the ant file correct the permission
on build, not which file to change the permission.
For example an sample ant file that change the permission:)...
until it is fixed in WOLips;)
Ahh, okay - simple...
Helo Lachlan:)
But it seems there's 2 different problems, the first one for me
is Monitor isn't able to start the instance for the updated apps.
Which is a serious issue because all schedule instances won't be
able to restart!
Anyone has an idea why it only happens with applications build
w
On 01/07/2007, at 7:29 PM, WO Dev wrote:
But it seems there's 2 different problems, the first one for me
is Monitor isn't able to start the instance for the updated apps.
Which is a serious issue because all schedule instances won't be
able to restart!
Anyone has an idea why it only happens w
OK,
I'm still trying to figure out why it wouldn't work on the dev
machine and not the deployment server...
I can launch the application and access the main start page (no
request to the database) but when I try to log with a user I got:
2007-07-01 12:33:19 CEST] java.lang.NullPoint
Hello Chuck:)
But it seems there's 2 different problems, the first one for me is
Monitor isn't able to start the instance for the updated apps.
Which is a serious issue because all schedule instances won't be
able to restart!
Anyone has an idea why it only happens with applications build
w
On 28/06/2007, at 4:22 AM, Chuck Hill wrote:
On Jun 27, 2007, at 8:33 AM, WO Dev wrote:
So I've checked all the frameworks, etc and they are all present
and at the same place on both the server and my local machine.
But it seems there's 2 different problems, the first one for me is
Monito
On Jun 27, 2007, at 8:33 AM, WO Dev wrote:
Hi,
Sorry for the late reply on this post...
I'm still trying to make it work "normally".
So I've checked all the frameworks, etc and they are all present
and at the same place on both the server and my local machine.
But it seems there's 2 diffe
Hi,
Sorry for the late reply on this post...
I'm still trying to make it work "normally".
So I've checked all the frameworks, etc and they are all present and
at the same place on both the server and my local machine.
But it seems there's 2 different problems, the first one for me is
Monit
On 24/06/2007, at 3:06 PM, WO Dev wrote:
I checked my project and frameworks, and it appears the framework
with the eomodel was referenced only in the "Java Build Path >
Projects" and not in "Java Build Path > Libraries" so I corrected
this.
That shouldn't matter. It's an either/or case.
Does the framework have any classes or only models and resources? Is
a jar getting created?
On Jun 23, 2007, at 10:43 PM, WO Dev wrote:
That's really weird, I got the same crash when embedding all the
"local" framework...
I don't understand why it would work on my dev machine and not on
Embedding works in fact.
But it's really too long for me to upload all the framework every
time I update the application...
All the framework are installed on the server in /Library/Frameworks
and have a jar file.
Xavier
Is the framework installed? Does it have a jar file? Is it in th
That's really weird, I got the same crash when embedding all the
"local" framework...
I don't understand why it would work on my dev machine and not on the
deployment machine:(
I also don't understand why it won't start using womonitor...
Xavier
I think that error means the prototypes did
Is the framework installed? Does it have a jar file? Is it in the
WebObjects Frameworks library?
On Jun 23, 2007, at 10:06 PM, WO Dev wrote:
Hello Chuck,
I checked my project and frameworks, and it appears the framework
with the eomodel was referenced only in the "Java Build Path >
Pr
Hello Chuck,
I checked my project and frameworks, and it appears the framework
with the eomodel was referenced only in the "Java Build Path >
Projects" and not in "Java Build Path > Libraries" so I corrected this.
But it still has the same error...
I'll try embedding the frameworks...
Xav
I think that error means the prototypes did not get loaded or the
plugin or something else did not get loaded. In either case -- check
the classpath. Make sure that all the relevant frameworks have been
installed if you are not embedding them in the application.
Chuck
On Jun 23, 2007, a
On 24/06/2007, at 8:06 AM, WO Dev wrote:
I forgot something;)
I had to remove:
--NSProjectSearchPath ()
to be able to launch the app...
Yep, that's what I do also when running from the terminal...
I'm sorry - I can't see anything obviously wrong from your logs.
I was actually making some t
I forgot something;)
I had to remove:
--NSProjectSearchPath ()
to be able to launch the app...
Hello Lachlan,
I was actually making some test via the command line.
I was able to start the application by removing:
-
Well, at least it's starting, but I have to find why it wouldn't
start wit
Hello Lachlan,
I was actually making some test via the command line.
I was able to start the application by removing:
-
Well, at least it's starting, but I have to find why it wouldn't
start with the default arguments...
The application is a back office application, so the first page is a
On 24/06/2007, at 6:22 AM, WO Dev wrote:
I though I was ready with Eclipse as all my applications just
compiled and worked under Eclipse (Development)... but I tried to
deploy an updated application today and it wouldn't launch:(
I don't know why it's not working, I have nothing in the
appl
Hi,
I though I was ready with Eclipse as all my applications just
compiled and worked under Eclipse (Development)... but I tried to
deploy an updated application today and it wouldn't launch:(
I don't know why it's not working, I have nothing in the
application's log (as it's not even start
21 matches
Mail list logo
