Seam 3 CR2 testing status
by Martin Gencur
Hi,
QA team finished the testing.
What was tested?
- the structure of the distribution (if everything is in place)
- new dependencies in the lib subdirectory (if they are the same as
those required by particular Seam projects - via dependency:tree)
- Forge - basic functionality, documentation
- seam-booking application - with JBoss 6 Final, Glassfish 3.1
Issues filed:
SEAM-34 - Multiple SLF4J bindings for Forge
SEAM-35 - Documentation issues (SEAMFORGE-60 - a duplicate for Forge)
SEAMFORGE-58 - Failing to install forge.api facet - missing Forge API
version to choose
SEAM-38 - new-entity command throws java.lang.NoSuchMethodError:
org.eclipse.jdt.internal....
SEAMFORGE-63 - Ensure readability of Forge prompts and messages
SEAM-40 - seam-booking does not work correctly with Glassfish 3.1
SEAM-39 - Incorrect artifacts bundled in the lib directory
SEAMSECURITY-41 - openid4java dependencies missing in the dist. bundle
--
Martin Gencur
Seam QA Associate
14 years, 10 months
is it working on glassfish 3.1 ?
by Sebastian E. Ovide
Hi All,
I have an application working on Glassfish 3.0. Now I'm trying to deploy on
3.1 but I'm getting errors such as:
SEVERE: Exception while loading the app : WELD-001408 Unsatisfied
dependencies for type [Bundles] with qualifiers [@Default] at injection
point [[field] @Inject
org.jboss.seam.international.status.builder.BundleTemplateMessageImpl.bundles]
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
dependencies for type [Bundles] with qualifiers [@Default] at injection
point [[field] @Inject
org.jboss.seam.international.status.builder.BundleTemplateMessageImpl.bundles]
at
org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:305)
at
org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:139)
at
org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162)
at
org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:385)
at
org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:371)
at
org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:390)
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:190)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128)
at
org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:298)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
at
org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:370)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1067)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1247)
at
com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
at
com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:465)
at
com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:222)
at
com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
at
com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234)
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:636)
thanks
--
Sebastian E. Ovide
14 years, 10 months
Seam JCR & Pull Requests in JIRA
by John D. Ament
Dan/Shane,
Could either of you look at the JCR module's Git pull request linking? I
just realized that it's not working right - it doesn't give the box for
linking pull request, just the comments box.
John
14 years, 10 months
Proposal for new module (Seam Report)
by George Gastaldi
Hello,
I have a new proposal for a new Seam 3 Module:
Seam Report: Integrate JasperReports, BIRT and other report solutions
providing an unified bridge for compiling and populating data. Could use
some stuff already on Seam Mail (Velocity templates, for example) and also
Flying Saucer (https://xhtmlrenderer.dev.java.net/) for generating PDFs
based on XHTML.
What do you guys think ?
Regards,
George
14 years, 10 months
Seam 3.0 CR2 released
by Shane Bryzak
Announcement is here:
http://in.relation.to/Bloggers/Seam300CR2Released
The major change in this release is the inclusion of Seam Forge, and the
Seam Booking example. The good news for the QE team is that none of the
other modules have been updated, meaning that minimal testing should be
necessary (although I think I recall Lincoln saying that he dared anyone
to find a bug in Forge).
With the CR2 release done, we should now all be concentrating on getting
the final releases out for all of the modules. With a tentative release
date of the end of next week for the final release, I'd like to see all
modules reach final by Wednesday next week (16th March). Not only will
that give me something to talk about for my JBUG talk next week, it will
also allow me time to put the finishing touches on the distribution, get
example names, readme files and developer credits sorted out, and
generally ensure that the release is befitting of the 3.0.0.Final tag.
It's been a long road to get to this point, and I really appreciate the
efforts made by the whole team. This really is a community project in
every sense, and I'm proud to have been a part of this great group of
passionate developers. Thanks guys!
14 years, 10 months
need advice for tests
by Antoine Sabot-Durand
Hi team
I need some advice regarding Social module and tests. Most of the job of the module is to dialog with remote services. I don't feel like mocking Twitter or LinkedIn service behavior to create my test. Do you have any suggestion to set those tests ? for the moment, all I see is to create a test account on these services to post update and request timeline, but it won't really test OAuth authentication since this ask user interaction. Any thought ?
Thanks
Antoine SABOT-DURAND
---------------------------------------
Twitter ; http://twitter.com/antoine_sd
LinkedIn : http://fr.linkedin.com/in/antoinesabotdurand
14 years, 10 months
JCR Repository Decorator
by George Gastaldi
Hello all,
I wrote a sample code to decorate a JCR Repository Object, but I did not
manage to be loaded on CDI context (Already placed on beans.xml)
My intention is to register an EventListener when a call to
repository.login() (and its overloaded methods) are called.
Here is the code: https://gist.github.com/861586
WDYT ?
14 years, 10 months
