I've used JSF (MyFaces) on a one year project before moving to WO (two
years ago), here are my feelings:
- A lot of XML configuration needed
- Uneasy component extension/creation
- Needs mixing HTML/JSP/JSF to achieve some goals
- Heavy
This was true two years ago, but now ?
Despite those
Hi all,
Would it not be cool if Java supported streamlined class conversion?
Something like this could be declared in the Object class, to be
overridden in subclasses:
public Class[] convertableTo(){ return new Class[0]}
public T T convertTo(ClassT clazz) throws CanNotConvertException
For some unknown reason safari no longer properly parses my cookie
generated by WOCookie.
The cookies always expire when browser closes. When I look at safari's
properties, my cookies have no expiration dates.
My code:
String hostName = .aspireauctions.com;
String path = /;
NSTimestamp
Which version of WO? Have you updated recently? Have you updated
Safari recently? Have you checked the expires date format in the
Cookie RFC? Is WO generating the wrong format, or is this a Safari bug?
Chuck
On Mar 3, 2008, at 10:39 AM, Michael Kondratov wrote:
For some unknown reason
Looks like Wo 5.4 or 5.4.1 (not sure)
[2008-3-3 18:24:21 EST] main WebObjects version = 5.4
Safari Version 3.0.4 (5523.15)
What's the current proper way of doing cookies in WO? :)
Michael
On Mar 3, 2008, at 1:45 PM, Chuck Hill wrote:
Which version of WO? Have you updated recently? Have you
On Mar 3, 2008, at 10:50 AM, Michael Kondratov wrote:
Looks like Wo 5.4 or 5.4.1 (not sure)
[2008-3-3 18:24:21 EST] main WebObjects version = 5.4
Safari Version 3.0.4 (5523.15)
What's the current proper way of doing cookies in WO? :)
Use WO 5.3.3. :-)
Check the RFC:
The WO-App our team has been developing has the ability to upload files.
The files can be a myriad of types (images, brochures [pdf, etc]). Our
requirements state that these files are then scanned for viruses, and
rejected as appropriate...
Has anyone had experience of integrating a
This is a bug, fixed in 5.4.2. As a workaround, you could use the
timeout instead of the expiration date (max-age vs. expires
attribute). (I know this isn't great for existing code).
-Ryan
On Mar 3, 2008, at 11:54 AM, Chuck Hill wrote:
On Mar 3, 2008, at 10:50 AM, Michael Kondratov
Is 5.4.2 available? I only see 5.4.1.
I've tried to use timeout, but Safari still deletes my cookies on exit.
Michael
On Mar 3, 2008, at 5:50 PM, Ryan Klems wrote:
This is a bug, fixed in 5.4.2. As a workaround, you could use the
timeout instead of the expiration date (max-age vs. expires
I just tried this and also had the same problem under safari. It
would appear that safari is ignoring the max-age attribute, and
treating the cookie as a session cookie. I've filed a radar on the
safari team. Firefox does treat the cookie properly. *sigh*
5.4.2 is not a released
Hello Ryan;
I stuck this...
// [apl 18.feb.2008]
// WebObjects 5.4.1 has a problem dealing with cookies that have their
value as
// an empty string. This little block of code should be able to
remove those
// such that they no longer pose a problem for the WO parser. This
MUST BE
//
11 matches
Mail list logo
