Re: [seam-dev] seam-faces 3.0.0.Final java.lang.NoClassDefFoundError: org/jboss/seam/exception/control/ExceptionToCatch
by Sebastian E. Ovide
I have not idea.... I thought that maven would do all the class path
magic....
On Thu, Mar 31, 2011 at 6:12 PM, José Rodolfo Carrijo de Freitas <
jose.freitas(a)softplan.com.br> wrote:
> Do you have seam catch in your classpath?
>
>
>
> *De:* seam-dev-bounces(a)lists.jboss.org [mailto:
> seam-dev-bounces(a)lists.jboss.org] *Em nome de *Sebastian E. Ovide
> *Enviada em:* quinta-feira, 31 de março de 2011 14:10
> *Para:* seam-dev(a)lists.jboss.org
> *Assunto:* [seam-dev] seam-faces 3.0.0.Final
> java.lang.NoClassDefFoundError:
> org/jboss/seam/exception/control/ExceptionToCatch
>
>
>
> after migrating to seam-faces 3.0.0.Final and to Glassfish 3.1 I can read
> this exception from the glassfish console:
>
> WARNING: StandardWrapperValve[FacesServlet]: PWC1406: Servlet.service() for
> servlet FacesServlet threw exception
> java.lang.NoClassDefFoundError:
> org/jboss/seam/exception/control/ExceptionToCatch
> at
> org.jboss.seam.faces.exception.CatchExceptionHandler.handle(CatchExceptionHandler.java:53)
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119)
> at
> com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:410)
> at
> org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1534)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215)
> at
> org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:61)
> at
> org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)
> at
> org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)
> at
> org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:81)
> at
> org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:66)
> at
> org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:359)
> at
> org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:275)
> at
> org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)
> at
> org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)
> at
> org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:344)
> at
> org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:272)
> at
> org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:81)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> at
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
> at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
> at
> com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:91)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162)
> at
> org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227)
> at
> com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170)
> at
> com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
> at
> com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
> at
> com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
> at
> com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
> at
> com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
> at
> com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
> at
> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
> at
> com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
> at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
> at
> com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
> at
> com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
> at java.lang.Thread.run(Thread.java:662)
>
> any ideas ?
> --
> Sebastian E. Ovide
>
>
>
>
--
Sebastian E. Ovide
13 years, 8 months
chat room guidelines
by Dan Allen
We are absolutely thrilled to have so much participation in the IRC
channels. #seam-dev in particular is visited by many of the core developers
throughout the day and is a catalyst for ideas and innovations.
With that said, the line is also starting to blur between which questions
and discussions are appropriate for the chat room and those that aren't. We
want to keep it fun and productive and we want to make sure you are asking
for help in the place you will most likely receive it. Therefore, we have
established a draft of guidelines for conduct in the chat rooms. (Feedback
welcome)
http://seamframework.org/Seam3/Chat#H-ChatRoomConduct
We ask that you respect these guidelines. In return, everyone can expect
their experience in the chatroom to be a positive one.
I'd like to stress that I want the Seam community to be a place of respect
amongst members. Constructive criticism is central to the peer feedback
system that OSS fosters. Yelling and swearing are not. Let's keep it fun and
productive.
Cheers,
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
13 years, 8 months
org.jboss.seam.faces 3.0.0.Final problems
by Sebastian E. Ovide
Hi All,
I've just updated my pom replacing 3.0.0.Alpha3 with 3.0.0.Final and I've
got a couple of errors.
I've fixed the first error just adding
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
<version>1.6.2</version>
</dependency>
is is ok to define seam dependencies manually ? should not that dependency
been part of seam ?
the second error that I'm getting is
org.glassfish.deployment.common.DeploymentException:
java.lang.NoClassDefFoundError: Lorg/jboss/logmanager/Logger$AttachmentKey;
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:167)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:125)
at
org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:224)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:338)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183)
any ideas ?
(using Glassfish 3.0)
thanks
--
Sebastian E. Ovide
13 years, 8 months
Code freeze
by Shane Bryzak
Hi all,
Code freeze is effective immediately for all modules being included in
the release. If you're working on a module that's not in the 3.0
release, please disregard and go about your business ;)
I'll update again when the release is completed.
Thanks,
Shane
13 years, 8 months
Example names
by Shane Bryzak
Guys, we've got to come up with a standard naming scheme for our example
names, because the ones we have look like an rhinoceros sat on them or
something:
helloworld
idmconsole
model
openid-rp
princess-rescue
seam-catch-example-basic-servlet
seam-international-example-timeanddate
seam-jaxrs-exceptions
seam-tasks-statistics
seam-wicket-example-numberguess
short.ly
simple
validation
validation-helloworld
I'm just as guilty as anyone else (in fact I think mine are the most
ambiguous of all). What I propose to clean this up is to prefix the
example name with the module name - e.g:
helloworld becomes remoting-helloworld
simple becomes security-simple
You get the idea. Also, the Maven artifact names for the examples
should be standardised too. We currently have all sorts of variations
here also, so how about we use seam-{module}-example-{name}, as this
seems to be what most people are already using (and therefore would
require the least work).
Using the previous two examples, that would give us artifact names like so:
seam-remoting-example-helloworld
seam-security-example-simple
What do you think?
13 years, 8 months
seam Wiki down?
by Denis Forveille
The Wiki was slower and slower those days
Now it appears to be totally down
13 years, 8 months
seam-booking from CR3 preliminary testing results on WebSphere v8 beta
by Denis Forveille
I'm trying to deploy the seam-booking app on WebSphere v8 beta (WAS).
It still fails to start. My discoveries:
Extension that have their constructor in scope "package" instead of "public" that makes the initialization to fail in WAS:
- org.jboss.seam.servlet.ServletExtension --> Dan you wrote in a previous mail that it was solved in CR3, it is not
- org.jboss.seam.servlet.logging.TypedMessageBundleAndLoggerExtension
- org.jboss.seam.solder.logging.TypedMessageLoggerExtension
- org.jboss.seam.solder.messages.TypedMessageBundleExtension
- org.jboss.seam.solder.serviceHandler.ServiceHandlerExtension
They may be other but they have not been "seen" by the initialization process..
Dan, if you want to create JIRA for those, please let me know
Missing jar in CR3 distribution. Both were included in CR2
- ocpsoft-pretty-time.jar (Used by org.jboss.seam.examples.booking.booking.BookingAgent)
- prettyfaces-jsf2.jar. Not sure for this one, but there is a file name pretty-config.xml under WEB-INF...Maybe this is the later
file that should not be there.
If you want me to create JIRAs for those, I will
And now I'm stuck with this exception at startup:
An error occured while initializing MyFaces: null
java.util.NoSuchElementException
at java.util.HashMap$AbstractMapIterator.makeNext(HashMap.java:124)
at java.util.HashMap$KeyIterator.next(HashMap.java:195)
at org.jboss.seam.faces.event.AbstractListener.getListeners(AbstractListener.java:27)
at org.jboss.seam.faces.event.DelegatingSystemEventListener.getEventListeners(DelegatingSystemEventListener.java:48)
at org.jboss.seam.faces.event.DelegatingSystemEventListener.processEvent(DelegatingSystemEventListener.java:36)
at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43)
at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2110)
at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:118)
at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2204)
at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:557)
at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:251)
at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:143)
at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:112)
at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1635)
I will try to investigate why this occur
Denis
13 years, 8 months
