[JBoss JIRA] Created: (JBSEAM-4731) backbuttoningAfterLogoutWithAjaxTest causes ServletException on JBoss AS 6
by Jozef Hartinger (JIRA)
backbuttoningAfterLogoutWithAjaxTest causes ServletException on JBoss AS 6
--------------------------------------------------------------------------
Key: JBSEAM-4731
URL: https://jira.jboss.org/browse/JBSEAM-4731
Project: Seam
Issue Type: Bug
Components: Test Harness
Affects Versions: 2.2.1.CR2
Environment: JBoss AS 6 CR1
Seam 2.2.1-SNAPSHOT
Reporter: Jozef Hartinger
Assignee: Jozef Hartinger
Priority: Minor
Fix For: 2.2.1.CR3
Attachments: backbuttoningAfterLogoutWithAjaxTest.html
The backbuttoningAfterLogoutWithAjaxTest fails for every booking-like example with the attached exception. I am not able to reproduce the exception manually. Therefore, it seems that it is Selenium-related.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Updated: (JBSEAM-4705) Itext example part Chartimage, renders incorrectly when hiding series in 3D graph
by Martin Gencur (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-4705?page=com.atlassian.jira.plugi... ]
Martin Gencur updated JBSEAM-4705:
----------------------------------
Affects Version/s: 2.2.1.Final
> Itext example part Chartimage, renders incorrectly when hiding series in 3D graph
> ---------------------------------------------------------------------------------
>
> Key: JBSEAM-4705
> URL: https://issues.jboss.org/browse/JBSEAM-4705
> Project: Seam
> Issue Type: Bug
> Components: Examples
> Affects Versions: 2.2.0.GA, 2.2.1.CR1, 2.2.1.CR2, 2.2.1.CR3, 2.2.1.Final
> Environment: sun jdk 1.6; openjdk 1.6; ibm jdk 1.6
> Reporter: Peter Lenyi
> Assignee: Marek Novotny
> Attachments: screenshot.png
>
>
> Itext, a Seam example, renders graph in example part Chartimage incorrectly, when the graph is set as 3D and some of the data series have been marked as hidden by user.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (SEAMFORGE-28) Should provide ability to specify mutually exclusive command options
by Lincoln Baxter III (JIRA)
Should provide ability to specify mutually exclusive command options
--------------------------------------------------------------------
Key: SEAMFORGE-28
URL: https://issues.jboss.org/browse/SEAMFORGE-28
Project: Seam Forge
Issue Type: Feature Request
Components: Plugin API
Affects Versions: 1.0.0.Alpha1
Reporter: Lincoln Baxter III
Priority: Minor
When developing Plugin @Commands, it is sometimes convenient to specify options from which only one must be selected
For example:
* providing a maven GAV "org.jboss.seam.forge:forge-parent:1.0.0"
* specifying the path to said project "~/projects/forge/"
Both inputs are valid, but only one is required. If one is selected, the other should be hidden from completion. (Or some such interaction.)
If both are missing, Forge should prompt for one to be completed.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBSEAM-4766) jboss-seam-2.2.1.CR3 / examples / seambay / webservices issues
by Xavier Neidoo (JIRA)
jboss-seam-2.2.1.CR3 / examples / seambay / webservices issues
--------------------------------------------------------------
Key: JBSEAM-4766
URL: https://issues.jboss.org/browse/JBSEAM-4766
Project: Seam
Issue Type: Bug
Components: Examples
Affects Versions: 2.2.1.CR3
Environment: Windows 7 Enterprise 32-bit
jboss-6.0.0.Final
jboss-seam-2.2.1.CR3
- examples/seambay
Reporter: Xavier Neidoo
Fix For: 2.2.1.Final
jboss-seam-2.2.1.CR3 > examples > seambay has the following issues:
1. wrong endpoint in the web frontend
Is: /auction/AuctionService, and should be: /auction/AuctionService/AuctionService.
2. parameters not working (at least on the "Login" command) in the web frontend
Manually setting the parameters in the request helps.
3. sessions not working (i.e. for the "List Categories" command)
Sessions work on jboss-5.1.0.GA with the same distribution.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBSEAM-4769) remoting/chatroom example not working with JBossAS 6 Final
by Martin Gencur (JIRA)
remoting/chatroom example not working with JBossAS 6 Final
----------------------------------------------------------
Key: JBSEAM-4769
URL: https://issues.jboss.org/browse/JBSEAM-4769
Project: Seam
Issue Type: Bug
Components: Examples
Affects Versions: 2.2.1.CR3
Environment: JBossAS 6 Final
Reporter: Martin Gencur
Fix For: The future
JBossAS shows the following error during deployment of the example. It's then possible to load the initial page of the example but it really doesn't work as expected.
10:34:53,761 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Real: name=vfs:///home/mgencur/Java/jboss6/jboss6final/jboss-6.0.0.Final/server/default/deploy/jboss-seam-chatroom-service.xml state=PreReal mode=Manual requiredState=Real: org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.mq.destination:service=Topic,name=chatroomTopic
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.GA]
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:125) [:6.0.0.Final]
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:49) [:6.0.0.Final]
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [:2.2.0.GA]
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1571) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_21]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_21]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_21]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_21]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_21]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: java.lang.ClassNotFoundException: org.jboss.mq.server.jmx.Topic from BaseClassLoader@42045478{vfs:///home/mgencur/Java/jboss6/jboss6final/jboss-6.0.0.Final/server/default/deploy/jboss-seam-chatroom-service.xml}
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:480) [jboss-classloader.jar:2.2.0.GA]
at java.lang.ClassLoader.loadClass(ClassLoader.java:248) [:1.6.0_21]
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:1216) [:6.0.0.GA]
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:288) [:6.0.0.GA]
at org.jboss.system.ServiceCreator.installPlainMBean(ServiceCreator.java:217) [:6.0.0.Final (Build SVNTag:JBoss_6.0.0.Final date: 20101228)]
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:133) [:6.0.0.Final (Build SVNTag:JBoss_6.0.0.Final date: 20101228)]
at org.jboss.system.microcontainer.InstantiateAction.installAction(InstantiateAction.java:73) [:2.2.0.GA]
at org.jboss.system.microcontainer.InstantiateAction.installAction(InstantiateAction.java:46) [:2.2.0.GA]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:301) [:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.system.ServiceController.doChange(ServiceController.java:671) [:6.0.0.Final (Build SVNTag:JBoss_6.0.0.Final date: 20101228)]
at org.jboss.system.ServiceController.install(ServiceController.java:257) [:6.0.0.Final (Build SVNTag:JBoss_6.0.0.Final date: 20101228)]
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:93) [:6.0.0.Final]
... 42 more
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (SOLDER-67) Add @Mock alternative stereotype
by Dan Allen (JIRA)
Add @Mock alternative stereotype
--------------------------------
Key: SOLDER-67
URL: https://issues.jboss.org/browse/SOLDER-67
Project: Seam Solder
Issue Type: Feature Request
Components: Core
Affects Versions: 3.0.0.Beta1
Reporter: Dan Allen
Naturally, each application is going to have it's own set of stereotypes and qualifiers, some of which will be used for project stage or target environment control. But then there are those roles that are so universal, that they would find a fit in nearly every application, like the @Model stereotype provided by the CDI spec. Solder should provide a @Mock alternative stereotype that can be used to control deployment of development-time beans. @Mock is even cited in the CDI api.
Providing a @Mock annotation centrally is beneficial to example projects and helps to raise awareness of the utility of a bean alternative.
@Alternative
@Stereotype
@Target(TYPE)
@Retention(RUNTIME)
public @interface Mock {}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months