Good day all, and sorry to spam the list, but his might be useful to one or
more of you (or you may know one or more people looking to work in Cupertino
for Apple!)
My team is looking for :
Senior Software Engineer, responsible for WO and Spring/Hibernate applications
in a client/server and HTM
handleMalformedCookieString() provides the (cookie) string being parsed when
the error occurred and the cookies it parsed successfully. If you have a better
error recovery strategy, have at it.
Tom
On Feb 10, 2011, at 6:16 PM, Dov Rosenberg wrote:
> Is there any way to just skip over
Without analysing the code further, it appears the parser tries all that it can
to continue parsing the cookie string and fails when it doesn't have any other
option.
I guess you could try re-writing it in completely different way if you wanted a
more controllable mechanism.
Regards,
Peter
O
Is there any way to just skip over the bad cookies and continue on - i.e.
Like if the malformed cookie is the third out of 5 cookies
Thanks
Dov Rosenberg
On 2/10/11 8:35 PM, "Peter Vandoros" wrote:
> "Debugging" _WOCookieParser, an IllegalStateException is thrown when it
> encounters a proble
Hi All,
I have no solution to this issue yet.
Let me give some more details.
The sequence does exist. It works fine when the connection broker is not
enabled.
In either case, there are several select statements that work fine, as
expected, before a new EO needs to be created.
Its only when th
"Debugging" _WOCookieParser, an IllegalStateException is thrown when it
encounters a problem. The exception is caught and
WOApplication.application().handleMalformedCookieString() is called. in
WOApplication.application().handleMalformedCookieString(), the initialisation
parameter is checked an
I had the flag running in production on one site for a couple of years (same
situation you mention) with no problems - I don't believe it just quits parsing
on a single error but I don't know. You might want use
WOApplication.handleMalformedCookieString(), which returns cookies successfully
pa
With the initialisation parameter you mention, I believe the CookieParser will
stop parsing subsequent cookies once it encounters a malformed one. This means
that if the malformed cookie happens to be the first one, as sent by the user's
browser, then you application won't receive any subsequent
Possibly because WOLips loads it. If it does.
On Feb 10, 2011, at 2:41 PM, Joe Little wrote:
> A new feature of Eclipse 3.6.1? :)
>
> On Thu, Feb 10, 2011 at 2:37 PM, Chuck Hill wrote:
>> On Feb 10, 2011, at 2:08 PM, Joe Little wrote:
>>> On Thu, Feb 10, 2011 at 2:04 PM, Chuck Hill
>>> wrot
A new feature of Eclipse 3.6.1? :)
On Thu, Feb 10, 2011 at 2:37 PM, Chuck Hill wrote:
> On Feb 10, 2011, at 2:08 PM, Joe Little wrote:
>> On Thu, Feb 10, 2011 at 2:04 PM, Chuck Hill wrote:
>>> On Feb 10, 2011, at 2:01 PM, Joe Little wrote:
>>>
That was it. Why oh why does it work in develop
On Feb 10, 2011, at 2:08 PM, Joe Little wrote:
> On Thu, Feb 10, 2011 at 2:04 PM, Chuck Hill wrote:
>> On Feb 10, 2011, at 2:01 PM, Joe Little wrote:
>>
>>> That was it. Why oh why does it work in development?
>>
>> I am not sure. Is it getting embedded? Is it not installed in your dev
>> env
On Thu, Feb 10, 2011 at 2:04 PM, Chuck Hill wrote:
>
> On Feb 10, 2011, at 2:01 PM, Joe Little wrote:
>
>> That was it. Why oh why does it work in development?
>
> I am not sure. Is it getting embedded? Is it not installed in your dev
> environment, so embedding can't find it?
Its working w/ W
On Feb 10, 2011, at 2:01 PM, Joe Little wrote:
> That was it. Why oh why does it work in development?
I am not sure. Is it getting embedded? Is it not installed in your dev
environment, so embedding can't find it?
> As for your quip about UNIX knowledge, you got me on that one.
Especially
That was it. Why oh why does it work in development? As for your quip
about UNIX knowledge, you got me on that one.
On Thu, Feb 10, 2011 at 1:55 PM, Chuck Hill wrote:
>
> On Feb 10, 2011, at 1:49 PM, Joe Little wrote:
>
>> Its embedded, but I'm wondering if there is a version issue with the
>> c
On Feb 10, 2011, at 1:49 PM, Joe Little wrote:
> Its embedded, but I'm wondering if there is a version issue with the
> classpath, as if something is overriding the methods in a new way.
Do you see WOOGNL.framework in
/Library/WebObjects/Applications/Affiliates.woa/Contents/Frameworks? It is N
Its embedded, but I'm wondering if there is a version issue with the
classpath, as if something is overriding the methods in a new way.
I don't get a classpath when running in development, but Wonder
reports it in deployment, although its not easily parsable to the
naked eye :)
com.webobjects.cla
I think the default was just to preserve compatibility with previous (albeit
broken) versions. I can't think of any security issue or any other reason why
you would want malformed cookies to get into your app code.
Chuck
On Feb 10, 2011, at 12:14 PM, Dov Rosenberg wrote:
> We came across a
Is it missing from the deployment server? Did not get embedded? Classpath is
wrong?
On Feb 10, 2011, at 11:45 AM, Joe Little wrote:
> Yep, it's my status page since I couldn't list multiple entities in one page,
> i am instead getting 4 different arrays and creating listpageinterfaces for
>
We came across a strange issue that took a bit to figure out but thought it
would be worthwhile to let everyone else know what happened
Problem
Some users were having trouble saving a form (WOComponent based)
intermittently. Normally these kinds of problems are nearly impossible to
figure out
Yep, it's my status page since I couldn't list multiple entities in one page, i
am instead getting 4 different arrays and creating listpageinterfaces for each
similar to the excel look demo.
As for wognl, it's enabled, as it works in development mode.
On Feb 10, 2011, at 11:17 AM, David LeBer
On 2011-02-10, at 2:04 PM, Joe Little wrote:
> I'm getting these errors:
>
> Error:
> com.webobjects.appserver._private.WODynamicElementCreationException:
> 'action' is a constant.
> Reason:
> 'action'
> is a constant.
>
> For this section
>
>
>value="$recentN
Again, I get these errors only in deployment.
On Feb 10, 2011, at 11:04 AM, Joe Little wrote:
> I'm getting these errors:
>
> Error:
> com.webobjects.appserver._private.WODynamicElementCreationException:
> 'action' is a constant.
> Reason:
> 'action'
> is a constant.
>
> For this s
You can add an inspect button yo the displayPropertyKeys for your
embedded list (or I tend to use a dedicated inspect link d2w component
that displays a textual property (eg title) that can be given which
inspect pageconfiguration to use.
Mark
--
Dr. Mark Wardle
Specialist registrar, Neurology
(
I'm getting these errors:
Error: com.webobjects.appserver._private.WODynamicElementCreationException:
'action' is a constant.
Reason:
'action'
is a constant.
For this section
In ModernLook. I noticed t
24 matches
Mail list logo
