myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Werner Punz <>
Subject Re: Run-time tomahawk error
Date Tue, 23 Jan 2007 23:59:54 GMT
Ok Simeon, I patched
every possible cause of conflict away, I could find, it committed the
sandbox fixes as we speak, so expect them probably the day after
tomorrow to be compiled
by the nightly build system, or check the code out and try a build yourself.

If some conflicts still persist, I would recommend that you
contact me directly on following address
(sorry for not typing it exactly, I want to keep spam away
werner.punz at, we could make
a direct instant messenger session so that we can patch away
the rest of the problems)

My hands are somewhat bound regarding weblogic currently I do not have a
license, I might look into being able to download
a testing license if possible.
But the best bet for now is, try the latest build and if problems
persist, please contact me directly, so that we can do a test/patch
session on your configuration.



Leyzerzon, Simeon schrieb:
> Thanks for your reply, Werner.  Unfortunately, we are not allowed to use any other app
server here but Weblogic 8.1, so I'll keep posting these little bugs here if you don't mind.
 Is there a way to disable the tld checking on weblogic?
> Thanks,
> Simeon 
> -----Original Message-----
> From: news [] On Behalf Of Werner Punz
> Sent: Tuesday, January 23, 2007 9:36 AM
> To:
> Subject: Re: Run-time tomahawk error
> Leyzerzon, Simeon schrieb:
>> Werner,
>> I was able to update today with the versions dated Jan 22nd and now I'm getting the
following exception:
>>  <Jan 22, 2007 2:01:01 PM EST> <Error> <HTTP> <BEA-101020>

>> <[ServletContext(id=16854421,name=GISWeb,context-path=/GISWeb)] 
>> Servlet failed with Exception
>> weblogic.servlet.jsp.JspException: (line 6): Error in using tag library uri=''
prefix='s': The Tag class 'org.apache.myfaces.custom.suggest.InputSuggestTag' has no setter
method corresponding to TLD declared attribute 'accesskey', (JSP 1.1 spec, 5.4.1)
>> 	at weblogic.servlet.jsp.StandardTagLib.tld_jspException(
>> 	at weblogic.servlet.jsp.StandardTagLib.parseTagDD(
>> 	at weblogic.servlet.jsp.StandardTagLib.parseDD(
>> 	at weblogic.servlet.jsp.StandardTagLib.<init>(
>> 	at weblogic.servlet.jsp.TagLibHelper.loadTagLib(
>> 	at weblogic.servlet.jsp.JspLexer.loadTagLib(
>> 	at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(
>> 	at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(
>> 	at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(
>> 	at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(
>> 	at weblogic.servlet.jsp.JspLexer.mTOKEN(
>> 	at weblogic.servlet.jsp.JspLexer.nextToken(
>> 	at weblogic.servlet.jsp.JspLexer.parse(
>> 	at weblogic.servlet.jsp.JspParser.doit(
>> 	at weblogic.servlet.jsp.JspParser.parse(
>> 	at weblogic.servlet.jsp.Jsp2Java.outputs(
>> 	at weblogic.utils.compiler.CodeGenerator.generate(
>> 	at weblogic.servlet.jsp.JspStub.compilePage(
>> 	at weblogic.servlet.jsp.JspStub.prepareServlet(
>> 	at weblogic.servlet.jsp.JspStub.prepareServlet(
>> 	at weblogic.servlet.internal.ServletStubImpl.getServlet(
>> 	at weblogic.servlet.internal.ServletStubImpl.invokeServlet(
>> 	at weblogic.servlet.internal.ServletStubImpl.invokeServlet(
>> 	at weblogic.servlet.internal.ServletStubImpl.invokeServlet(
>> 	at weblogic.servlet.internal.WebAppServletContext$
>> 	at
>> 	at
>> 	at weblogic.servlet.internal.WebAppServletContext.invokeServlet(
>> 	at weblogic.servlet.internal.ServletRequestImpl.execute(
>> 	at weblogic.kernel.ExecuteThread.execute(
>> 	at
>> Am I doing something wrong?
>> Thank you,
>> Simeon
> Nothing, this seems to be a slight error in the sandbox tld as well, Weblogic seems to
be very unforgiving regarding those issues, way more unforgiving than other app servers, all
I can say is I will try to fix all of those tld issues I can find tonight and tomorrow.
> (Bear in mind I cannot verify them here, since I lack weblogic, so you might get another
bunch of errors until everything is fixed)
> In the meantime you can switch over to a different app server and retry from time to
time. Those issues are a little bit hard to nail down since most app servers do not choke
on those small issues.
> (Tomcat is mostly used for development here)
> It all comes down mostly to small tld errors, ignored by most app servers, (mainly type
declaration errors) in the tlds, Tomahawk core seems to be fixed, since no error is given
there anymore, but the sandbox might be full of them.
> ==============================================================================
> Please access the attached hyperlink for an important electronic communications disclaimer:

> ==============================================================================

View raw message