November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1181) Redirect not working for DocumentStore

by Pete Muir (JIRA)

Redirect not working for DocumentStore -------------------------------------- Key: JBSEAM-1181 URL: http://jira.jboss.com/jira/browse/JBSEAM-1181 Project: JBoss Seam Issue Type: Bug Components: Examples, PDF Reporter: Pete Muir Assigned To: Norman Richards Attachments: screenshot-1.jpg See screenshot -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-669) Scanner and components.xml inside packages

by Peter Muir (JIRA)

Scanner and components.xml inside packages ------------------------------------------ Key: JBSEAM-669 URL: http://jira.jboss.com/jira/browse/JBSEAM-669 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.1.GA Reporter: Peter Muir If you put a components.xml inside a package which has no classes which are seam components inside it then it is not picked up by the scanner. This is because Initialization.installScannedClass attempts to install from the components.xml file for that package BUT for the flow to get to installScannedClass at least one of the classes in the package must be a seam component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

6
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2326) s:conversationId documentation misleading

by Samuel Mendenhall (JIRA)

s:conversationId documentation misleading ----------------------------------------- Key: JBSEAM-2326 URL: http://jira.jboss.com/jira/browse/JBSEAM-2326 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 2.0.0.GA, 2.0.0.CR3, 2.0.0.CR2, 2.0.0.CR1, 2.0.0.BETA1, 1.3.0.ALPHA, 1.2.1.GA, 1.2.0.GA, 1.1.7.CR1, 1.1.6.GA, 1.1.5.GA, 1.1.1.GA, 1.1.0.GA, 1.1.0.CR2, 1.1.0.CR1, 1.1.0.BETA2, 1.1.0.BETA1, 1.0.1, 1.0, 1.0 beta 2, 1.0 beta 1, 2.0.1.GA, 2.0.2.GA, 2.0.x Reporter: Samuel Mendenhall Priority: Minor Fix For: 2.0.1.GA The description of s:conversationId is misleading: "Add the conversation id to an output link (or similar JSF control)" This gives the first impression that the s:conversationId can only be added to an h:outputLink. It can be added to h:commandButton also or h:commandLink -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2248) Bring pageflow-2.0.xsd in sync with jBPM-jPDL 3.2.2 changes

by Matthew Lieder (JIRA)

Bring pageflow-2.0.xsd in sync with jBPM-jPDL 3.2.2 changes ----------------------------------------------------------- Key: JBSEAM-2248 URL: http://jira.jboss.com/jira/browse/JBSEAM-2248 Project: JBoss Seam Issue Type: Task Components: BPM Affects Versions: 2.0.1.GA Reporter: Matthew Lieder Fix For: 2.0.1.GA For instance, the "binding" attribute should be valid on the sub-process element. There could be other changes too. You'll likely want to call the new version pageflow-2.0.1.xsd or something. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Work started: (JBSEAM-1103) Deploying Seam example app into /trunk causes ZipException

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-1103?page=all ] Work on JBSEAM-1103 started by Ales Justin. > Deploying Seam example app into /trunk causes ZipException > ---------------------------------------------------------- > > Key: JBSEAM-1103 > URL: http://jira.jboss.com/jira/browse/JBSEAM-1103 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Environment: r61655 of /trunk and jboss-seam-1.2.0.PATCH1 > Reporter: Charles Crouch > Assigned To: Ales Justin > Fix For: 2.0.x > > Attachments: cglib-nodep-2.1_3.jar, el-api.jar, el-ri.jar, jboss-seam-numberguess.ear > > > Deploying a modified version of jboss-seam-numberguess.ear into the current Beta2 server causes ZipException's to be thrown during startup and trying to hit http://localhost:8080/seam-numberguess produces 500's. Deploying the same app into Beta1 works fine. > Steps to reproduce: > 1) Copy > jboss-seam-1.2.0.PATCH1\lib\el-api.jar > and > jboss-seam-1.2.0.PATCH1\lib\el-ri.jar > to > build\output\jboss-5.0.0.Beta2\server\default\deployers\jbossweb.deployer\jsf-libs > 2) Copy > cglib-nodep-2.1_3.jar (version probably doesn't matter) > to > build\output\jboss-5.0.0.Beta2\server\default\lib > 3) Copy modified jboss-seam-numberguess.ear > to > build\output\jboss-5.0.0.Beta2\server\default\deploy > 4) Start the server and you get several exceptions like the following... > 12:09:11,896 INFO [Catalina] Server startup in 190 ms > 12:09:20,769 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=Dispatcher,service=EJB3 with dependencies: > 12:09:24,244 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.Dispatcher ejbName: Dispatcher > 12:09:24,484 WARN [JBossTimerServiceFactory] TIMER SERVICE IS NOT INSTALLED > 12:09:24,484 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TransactionListener,service=EJB3 with dependencies: > 12:09:26,216 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.TransactionListener ejbName: TransactionListener > 12:09:29,441 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war > 12:09:35,319 INFO [TomcatDeployment] deploy, ctxPath=/seam-numberguess, vfsUrl=jboss-seam-numberguess.ear/jboss-seam-numberguess.war > 12:09:38,895 INFO [ServletContextListener] Welcome to Seam 1.2.0.PATCH1 > 12:09:38,995 INFO [Scanner] scanning: vfsfile:/C:/usr/projects/current/jboss/trunk/build/output/jboss-5.0.0.Beta2/server/default/deploy/jboss-seam-numberguess.ear/jboss-seam.jar > 12:09:38,995 WARN [Scanner] could not read entries > java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:203) > at java.util.zip.ZipFile.<init>(ZipFile.java:234) > at org.jboss.seam.deployment.Scanner.handleArchive(Scanner.java:110) > at org.jboss.seam.deployment.Scanner.scan(Scanner.java:96) > at org.jboss.seam.deployment.NamespaceScanner.getPackages(NamespaceScanner.java:34) > at org.jboss.seam.init.Initialization.addNamespaces(Initialization.java:590) > at org.jboss.seam.init.Initialization.<init>(Initialization.java:80) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3854) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2274) Examples & Documentation for using Seam iText Barcode

by Joshua Partogi (JIRA)

Examples & Documentation for using Seam iText Barcode ----------------------------------------------------- Key: JBSEAM-2274 URL: http://jira.jboss.com/jira/browse/JBSEAM-2274 Project: JBoss Seam Issue Type: Patch Components: PDF Affects Versions: 2.0.0.GA Environment: JBoss 4.2.1.GA Reporter: Joshua Partogi Fix For: 2.0.1.GA Attachments: barcode_example.jpg Page 79 Chapter 16.3 Seam 2.0.0.GA 1. It should be <p:barCode> not <p:barcode> 2. Attributes: type - The barcode type. Available types are * code128 * code39 * codabar * ean * inter25 * postnet code - The code to generate codeType - The code type xpos - The x coordinate to place the barcode. The data type is float. ypos - The y coordinate to place the barcode. Remember that zero coordinate starts from the bottom of the page. The data type is float. rotDegrees - The rotation degrees to rotate the barcode. The data type is float. barHeight - The bar height. The data type is float. textSize - The text size. The data type is float. minBarWidth - The minimum bar width. The data type is float. barMultiplier - The bar multiplier for wide bars or the distance between bars for Postnet and Planet. The data type is float. 3. Usage: <p:document xmlns:p="http://jboss.com/products/seam/pdf"> <p:barCode type="code128" code="SeamRocks" xpos="30" ypos="700" textSize="100" rotDegrees="30" barHeight="25" minBarWidth="0.8" barMultiplier="15"/> </p:document> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-1103) Deploying Seam example app into /trunk causes ZipException

by Charles Crouch (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-1103?page=all ] Charles Crouch reassigned JBSEAM-1103: -------------------------------------- Assignee: Ales Justin Ales, assigning to you for tracking purposes. Can you create a corresponding JBAS issue which is a blocker for JBAS5 beta3 release. > Deploying Seam example app into /trunk causes ZipException > ---------------------------------------------------------- > > Key: JBSEAM-1103 > URL: http://jira.jboss.com/jira/browse/JBSEAM-1103 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Environment: r61655 of /trunk and jboss-seam-1.2.0.PATCH1 > Reporter: Charles Crouch > Assigned To: Ales Justin > Fix For: 2.0.x > > Attachments: cglib-nodep-2.1_3.jar, el-api.jar, el-ri.jar, jboss-seam-numberguess.ear > > > Deploying a modified version of jboss-seam-numberguess.ear into the current Beta2 server causes ZipException's to be thrown during startup and trying to hit http://localhost:8080/seam-numberguess produces 500's. Deploying the same app into Beta1 works fine. > Steps to reproduce: > 1) Copy > jboss-seam-1.2.0.PATCH1\lib\el-api.jar > and > jboss-seam-1.2.0.PATCH1\lib\el-ri.jar > to > build\output\jboss-5.0.0.Beta2\server\default\deployers\jbossweb.deployer\jsf-libs > 2) Copy > cglib-nodep-2.1_3.jar (version probably doesn't matter) > to > build\output\jboss-5.0.0.Beta2\server\default\lib > 3) Copy modified jboss-seam-numberguess.ear > to > build\output\jboss-5.0.0.Beta2\server\default\deploy > 4) Start the server and you get several exceptions like the following... > 12:09:11,896 INFO [Catalina] Server startup in 190 ms > 12:09:20,769 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=Dispatcher,service=EJB3 with dependencies: > 12:09:24,244 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.Dispatcher ejbName: Dispatcher > 12:09:24,484 WARN [JBossTimerServiceFactory] TIMER SERVICE IS NOT INSTALLED > 12:09:24,484 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TransactionListener,service=EJB3 with dependencies: > 12:09:26,216 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.TransactionListener ejbName: TransactionListener > 12:09:29,441 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war > 12:09:35,319 INFO [TomcatDeployment] deploy, ctxPath=/seam-numberguess, vfsUrl=jboss-seam-numberguess.ear/jboss-seam-numberguess.war > 12:09:38,895 INFO [ServletContextListener] Welcome to Seam 1.2.0.PATCH1 > 12:09:38,995 INFO [Scanner] scanning: vfsfile:/C:/usr/projects/current/jboss/trunk/build/output/jboss-5.0.0.Beta2/server/default/deploy/jboss-seam-numberguess.ear/jboss-seam.jar > 12:09:38,995 WARN [Scanner] could not read entries > java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:203) > at java.util.zip.ZipFile.<init>(ZipFile.java:234) > at org.jboss.seam.deployment.Scanner.handleArchive(Scanner.java:110) > at org.jboss.seam.deployment.Scanner.scan(Scanner.java:96) > at org.jboss.seam.deployment.NamespaceScanner.getPackages(NamespaceScanner.java:34) > at org.jboss.seam.init.Initialization.addNamespaces(Initialization.java:590) > at org.jboss.seam.init.Initialization.<init>(Initialization.java:80) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3854) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2322) Programmatic repositioning of jPDL pageflow not working when done inside transition

by Matthew Lieder (JIRA)

Programmatic repositioning of jPDL pageflow not working when done inside transition ----------------------------------------------------------------------------------- Key: JBSEAM-2322 URL: http://jira.jboss.com/jira/browse/JBSEAM-2322 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.0.GA Reporter: Matthew Lieder <page name="repopage" view-id="/message.xhtml"> <redirect /> <action expression="#{pageflow.reposition('destpage')}" /> </page> works, but the following doesn't: <page name="firstpage" view-id="/choice.xhtml"> <redirect /> <transition name="choice2" to="dummypage"> <action expression="#{pageflow.reposition('destpage')}" /> </transition> </page> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2124) Natural conversation ids are broken

by Shane Bryzak (JIRA)

Natural conversation ids are broken ----------------------------------- Key: JBSEAM-2124 URL: http://jira.jboss.com/jira/browse/JBSEAM-2124 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Blocker Fix For: 2.0.0.GA When re-entering an existing conversation that uses a natural conversation id, we currently get a "Conversation id is already in use" exception like the following: Caused by: java.lang.IllegalStateException: Conversation id is already in use: PlaceBid:62748261 at org.jboss.seam.core.Manager.updateCurrentConversationId(Manager.java:90) at org.jboss.seam.faces.FacesManager.beforeRedirect(FacesManager.java:73) at org.jboss.seam.faces.FacesManager.redirect(FacesManager.java:164) at org.jboss.seam.faces.Navigator.redirect(Navigator.java:91) at org.jboss.seam.navigation.RedirectNavigationHandler.navigate(RedirectNavigationHandler.java:53) at org.jboss.seam.navigation.Rule.execute(Rule.java:100) at org.jboss.seam.navigation.Navigation.navigate(Navigation.java:123) at org.jboss.seam.navigation.Pages.navigate(Pages.java:134) at org.jboss.seam.jsf.SeamNavigationHandler.handleNavigation(SeamNavigationHandler.java:83) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:119) at javax.faces.component.UICommand.broadcast(UICommand.java:383) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:447) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97) The workaround for this is to specify the named conversation within the @Begin annotation for the action being called, like so: @Begin(join = true, conversation = "PlaceBid") public void placeBid() { This way, ConversationInterceptor can redirect to the existing named conversation the same way it does a ce.redirect() for standard conversations. However this is less than ideal, as we don't want to introduce yet another annotation attribute here if we can avoid it. The preferred way of configuring this would be in a navigation rule in pages.xml: <page view-id="/auction.xhtml"> <param name="id" value="#{auctionDetail.selectedAuctionId}"/> <navigation from-action="#{bidAction.placeBid}"> <begin-conversation join="true" conversation="PlaceBid"/> <redirect view-id="/bid.xhtml"/> </navigation> </page> The problem with this though is that it happens too late - conversation propagation defined in navigation rules like this get processed in ConversationControl.beginOrEndConversation(), after the action method has already been invoked thereby producing the same "Conversation id already in use" exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2299) Seam Generate Entities creates edit field for @Version annotated fields

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2299?page=comments#action_12389763 ] Max Andersen commented on JBSEAM-2299: -------------------------------------- thinking more about it I agree. many tend to put more meaning into the version field than they should so lets not encourage that and just not show it. > Seam Generate Entities creates edit field for @Version annotated fields > ----------------------------------------------------------------------- > > Key: JBSEAM-2299 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2299 > Project: JBoss Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.0.GA > Reporter: Thorsten Kunz > Assigned To: Dan Allen > Priority: Minor > Fix For: 2.0.1.GA > > Attachments: JBSEAM-2299-v1.txt, JBSEAM-2299-v2.txt > > > When you have an entity with a @Version annotation present (which is the default if you create it with "Seam Entity") and then run "Seam Generate Entities" on the project and select "use existing entities" the resulting CRUD pages will allow the version field to be edited. So you won't be able to create entities because the set accessor for the version was declared private in the entity. This renders the CRUD pages useless. > I think this field should not be editable in the first place. > Cheers, Thorsten -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007