View Single Post
  #6  
Old December 12th 06, 09:40 PM posted to rec.aviation.soaring
[email protected]
external usenet poster
 
Posts: 57
Default OLC North America

OK, still works fine for me on IE XP Pro.

Did you try clicking HELP on the OLC page? Same problem? You can never
get to any of the Help pages? or the FAQ even?

Email your issue to:

I suggest telling them your browser name and version, Windows or Mac
version etc.

I doubt you are the only one with the issue and they may have a
suggestion.

Since it's a work in progress, try again later, you may 'catch' them in
mid-fix.

Doubtless they are using bleeding edge software and since there is a
varety of browsers and not everyone keeps theirs updated, they are
going to draw out every bug in every browser and PC setup out there.
The 'old days' of plain old HTML are gone, and the fancy new stuff can
cause grief.

Bob




hans wrote:
Hi Bob!

this is what I get when I try your link:


An Error has occurred in this application.

org.springframework.web.util.NestedServletExceptio n: Request processing
failed; nested exception is java.lang.NullPointerException
java.lang.NullPointerException
at
de.instantsolutions.olc.web.PlainJspController.han dleRequest(PlainJspController.java:31)
at
org.springframework.web.servlet.mvc.SimpleControll erHandlerAdapter.handle(SimpleControllerHandlerAda pter.java:44)
at
org.springframework.web.servlet.DispatcherServlet. doDispatch(DispatcherServlet.java:723)
at
org.springframework.web.servlet.DispatcherServlet. doService(DispatcherServlet.java:663)
at
org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:394)
at
org.springframework.web.servlet.FrameworkServlet.d oGet(FrameworkServlet.java:348)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
at
org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at
org.springframework.orm.hibernate3.support.OpenSes sionInViewFilter.doFilterInternal(OpenSessionInVie wFilter.java:174)
at
org.springframework.web.filter.OncePerRequestFilte r.doFilter(OncePerRequestFilter.java:77)
at
org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at
org.displaytag.filter.ResponseOverrideFilter.doFil ter(ResponseOverrideFilter.java:125)
at
org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at
com.opensymphony.module.sitemesh.filter.PageFilter .parsePage(PageFilter.java:118)
at
com.opensymphony.module.sitemesh.filter.PageFilter .doFilter(PageFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at
de.instantsolutions.olc.web.MessageFilter.doFilter (MessageFilter.java:49)
at
org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve..java:214)
at
org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve..java:178)
at
org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyo teHandler.java:306)
at org.apache.jk.common.HandlerRequest.invoke(Handler Request.java:385)
at org.apache.jk.common.ChannelSocket.invoke(ChannelS ocket.java:745)
at
org.apache.jk.common.ChannelSocket.processConnecti on(ChannelSocket.java:675)
at org.apache.jk.common.SocketConnection.runIt(Channe lSocket.java:868)
at
org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)

Best Regards


Hans


schrieb:
You certainly *can* feedback to the development team directly, I got a
reply on the calendar bug within one hour, stating the programmer was
en route home and would fix it. It worked soon thereafter.

To ask questions or report problems, click on the HELP tab at bottom
left on every page viewed. You will see the tabs "Imprint" "Search"
"Print" and "Help"... click on HELP

(URL:
http://www3.onlinecontest.org/olc-2....refix_jsp=help
)

A large FAQ is shown, and above it the words:
(start quote)
answered by OLC-administrator Johannes Niesslbeck (AC München) last
update December 5th 2006

Please read the FAQ first, only if Your problem is not mentioned there,
write a Mail to: (end quote)

So to ask a question, click on the email address link. And each country
has a volunteer coordinator you can also email for help, Doug Haluza
for the USA, Tony Firmin for Canada.


A modest suggestion to all.... please be patient and understanding of
this large scale international volunteer effort. They had to get it up
for the start of the 2007 contest year to capture your flight logs in
the new database format, that had to be Priority One. Getting correct
outputs was obviously secondary in importance and they are chugging
away at it and many outputs are working now. The Google Earth output is
a very nice tool, and will not be seen as a frill once you see your own
flights in it.

Think of all the issues they have in hosting a worldwide audience of
Type A's like us, all the languages, every time zone, everything new
and everything volunteer. And keep the old system up for a while too by
the way.

Wish them well, congratulate their successes, ignore the little bugs
for now for soon they will be gone.

I am not part of that team, I just think they need our support and not
so much of our gripes. This is for fun.

All the best!
Bob





5Z wrote:
On Dec 10, 8:57 am, "Dan" wrote:
Anyone know how to navigate the new OLC?
All I can get is OLC Worldwide, I can't seem to make it display just
North America.
Works OK for me... It does have a habit of reverting back to worldwide
a lot - perhaps it's not using cookies effectively?

Also seem to have a lot of trouble with the calendar. I have to go
back and forward to make it show results for the current day. Also the
calendar is somewhat tricky.
Yes, it seems to have no "memory" for one's time zone (cookies again),
so in the USA, if it's evening, it's already tomorrow to the OLC. The
calendar app has a problem with ging back a day in this case, so the
solution is tt go back a month, then forward and all is well. I really
miss the buttons on the main meny that let you go back & forward a day
at a time.

I really enjoy the OLC, I sure hope it is running better by next
season.
Overall, in the last few weeks, it's gotten to the point that, for me,
it's close to the functionality of last year's. One can now click
onthe pilot's name or takeoff site and get a list of all flights for
that item. It's reall starting to get quite good.

As a software developer myself, I understand the challenge of putting
together a website such as this with a huge dynamic content. How many
of us would have volunteered to test this new version "offline" to get
the bugs out? Probably not enough to really wring it out. So they did
the next best thing, and just "forced" it on us and we had to suffer a
little through the growing pains.

What is critical to making this a better product is good problem
reporting by the users back to the developers. And unfortunately, it
seems this forum is the only obvious place to do that at this time. I
see nothing on the OLC website for user feedback. This shoud be an
open forum such as SeeYou has. Users can post their wishes and
troubles openly. Then the developers should reply in a timely fashion.
But at the same time other users can perhaps offer solutions, or just
chime in with "me too", so the problem or feature is identified as
popular.

-Tom