I know that there is more information around why the application behaves this way and possible ways to get the behaviour that you desired so I’m assuming that you’ve pressed Publish before you meant to.
FOL usually means that someone has tried to work something “against” the design principles (often for a really good reason) so it’s often a case of trying to understand what they were “really” trying to acheive and then figure out ways to help them get that.
In that particular case the actual issue was around personalization (and was logged in 2002) and centered around getting the right runtime events to fire to support the customer’s needs… as often happens with UI level events the caching that helps with performance was skewing the behaviour so the event wasn’t firing when it was needed.
I think perhaps the outbound communication could have been worded in a slightly more “friendly” way
UN:F [1.8.2_1042]
please wait...
Rating: 0.0/5 (0 votes cast)
UN:F [1.8.2_1042]
Rating: 0 (from 0 votes)
Leave a comment
No trackbacks yet.
Subscription
Fill out the form below to signup to our blog newsletter and we'll drop you a line when new articles come up.
2:17 pm on December 19th, 2008
Did you forget to finsih your blog entry?
I know that there is more information around why the application behaves this way and possible ways to get the behaviour that you desired so I’m assuming that you’ve pressed Publish before you meant to.
3:59 pm on December 19th, 2008
>> Graham:
This wat not the answer to an issue I logged, I just found it funny. I was not criticizing an answer from Oracle.
4:10 pm on December 19th, 2008
Just thought I’d check
FOL usually means that someone has tried to work something “against” the design principles (often for a really good reason) so it’s often a case of trying to understand what they were “really” trying to acheive and then figure out ways to help them get that.
In that particular case the actual issue was around personalization (and was logged in 2002) and centered around getting the right runtime events to fire to support the customer’s needs… as often happens with UI level events the caching that helps with performance was skewing the behaviour so the event wasn’t firing when it was needed.
I think perhaps the outbound communication could have been worded in a slightly more “friendly” way