August 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1802) Reduce atrocious load time when jBPM is used for jPDL pageflow functionality

by Matthew Lieder (JIRA)

Reduce atrocious load time when jBPM is used for jPDL pageflow functionality ---------------------------------------------------------------------------- Key: JBSEAM-1802 URL: http://jira.jboss.com/jira/browse/JBSEAM-1802 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Environment: Java 1.6u2, Tomcat 5.5.23 Reporter: Matthew Lieder Normally Seam starts up in ~10 seconds for me. However, when I use jPDL pageflows, the startup time increases to ~30 seconds! Obviously there's a big inefficiency lurking there. -- 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, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1764) Create / Extend / Modify Seam RuleBase component to utilize JBoss Rules 4.0 BRMS rule pkg deployment model.

by Michael Engel (JIRA)

Create / Extend / Modify Seam RuleBase component to utilize JBoss Rules 4.0 BRMS rule pkg deployment model. ------------------------------------------------------------------------------------------------------------ Key: JBSEAM-1764 URL: http://jira.jboss.com/jira/browse/JBSEAM-1764 Project: JBoss Seam Issue Type: Feature Request Components: Drools Environment: All Reporter: Michael Engel Allow org.jboss.seam.drools.RuleBase to accept and process rule bases from JBossRules 4.0 BRMS. Something along the lines of setting a rules.properties file name (which is in the classpath) or the individual properties in components.xml For example: (from Drools documentation 4.0.0 -- Section 9.4.4. Deployment: Integrating rules with your applications) <drools:rule-base name="ruleSet1"> <property name="newInstance">true</property> <property name="files"></property> <property name="dir">/my/dir</property> <property name="url">http://some.url/here http://some.url/here</property> <property name="localCacheDir">=/foo/bar/cache</property> <property name="pool">30</property> </drools:rule-base> -- 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, 7 months

5
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1885) s:link builds a wrong URL with fragment

by Isabella Kneissl (JIRA)

s:link builds a wrong URL with fragment --------------------------------------- Key: JBSEAM-1885 URL: http://jira.jboss.com/jira/browse/JBSEAM-1885 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: jboss-4.2.0.GA, JBoss Seam 1.2.1.GA, JSF RI 1.2 Reporter: Isabella Kneissl If I use a s:link component with a defined fragment, the built url is wrong: e.g. http://mypage.com?cid=7#anchor it has to be: e.g. http://mypage.com#anchor?cid=7 -- 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, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-974) Document Seam dependencies

by Carsten H?hne (JIRA)

Document Seam dependencies -------------------------- Key: JBSEAM-974 URL: http://jira.jboss.com/jira/browse/JBSEAM-974 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Reporter: Carsten H?hne There is a wiki page here: http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamDependencies But this page is not uptodate. I would like to see an apendix to the documentation where all Seam dependencys are described. This appendix can than be updated every new release. -- 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, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1882) render time if/else tags to avois excessive calls in rendered attribute

by Mikhail Grushinskiy (JIRA)

render time if/else tags to avois excessive calls in rendered attribute ----------------------------------------------------------------------- Key: JBSEAM-1882 URL: http://jira.jboss.com/jira/browse/JBSEAM-1882 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Mikhail Grushinskiy render time if/else tags to avois excessive calls in rendered attribute JSF doesn't have if/else render time tag construct. So if you have many if/else conditions you end up writting rendered= attribute with those conditions and call the same bean methods all over again. This significantly impacts performance. Thanks -- 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, 7 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-910) s:columns

by Peter Muir (JIRA)

s:columns --------- Key: JBSEAM-910 URL: http://jira.jboss.com/jira/browse/JBSEAM-910 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.1.6.GA Reporter: Peter Muir Assigned To: Peter Muir Priority: Optional Iterate over columns as well as rows (similar to t:columns) -- 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, 7 months

5
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1874) todo.jpdl.xml - Error opening the editor (jBPM Graphical Process Designer)

by Joachim Neubert (JIRA)

todo.jpdl.xml - Error opening the editor (jBPM Graphical Process Designer) -------------------------------------------------------------------------- Key: JBSEAM-1874 URL: http://jira.jboss.com/jira/browse/JBSEAM-1874 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.0.BETA1 Environment: Eclipse Europa / JBoss Tools (2.0 beta3) Reporter: Joachim Neubert When I try to open the todo.jpdl.xml, I get a message "Convert to 3.1.x format?" ("older GPD version was detected"). When I confirm the default action "Convert And Open", I get: Error opening editor Reason: null argument ("Details" below) With a new process definition, I get the same error: New -> JBoss jBPM -> Process Definition -> Process Name: test1 creates: test1 +- gdp.xml +- processdefinition.xml Opening the processdefinition.xml in the jBPM Graphical Process Designer results in exactly the same Messages "Details" org.eclipse.core.runtime.AssertionFailedException: null argument: at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:84) at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:72) at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:578) at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:938) at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:660) at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1295) at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:366) at org.eclipse.jface.viewers.AbstractTreeViewer.getFilteredChildren(AbstractTreeViewer.java:615) at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:581) at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:778) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:755) at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:615) at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1460) at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:804) at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1443) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1368) at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:378) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1330) at org.eclipse.jface.viewers.CheckboxTreeViewer.preservingSelection(CheckboxTreeViewer.java:371) at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1432) at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:251) at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1606) at org.jbpm.gd.jpdl.deployment.DeploymentForm.createIncludeClassesSection(Unknown Source) at org.jbpm.gd.jpdl.deployment.DeploymentForm.create(Unknown Source) at org.jbpm.gd.jpdl.editor.JpdlDeploymentEditorPage.createForm(Unknown Source) at org.jbpm.gd.jpdl.editor.JpdlDeploymentEditorPage.createPartControl(Unknown Source) at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:190) at org.jbpm.gd.common.editor.Editor.addPage(Unknown Source) at org.jbpm.gd.jpdl.editor.JpdlEditor.createPages(Unknown Source) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633) at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556) at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340) at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328) at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:190) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) -- 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, 7 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1867) NPE in org.jboss.seam.util.Reflections when an exception arise while accessing a static field

by Thomas Bauer (JIRA)

NPE in org.jboss.seam.util.Reflections when an exception arise while accessing a static field --------------------------------------------------------------------------------------------- Key: JBSEAM-1867 URL: http://jira.jboss.com/jira/browse/JBSEAM-1867 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Environment: MAC OS X 10.4.10, Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164) Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing), G5 PPC Reporter: Thomas Bauer When an exception is thrown while accessing a static field in org.jboss.seam.util.Reflections.get/set (org/jboss/seam/util/Reflections line 46 and 60) the catch-block will throw a NPE when accessing the variable "target" (which is null): Static Fields may have target == null (e.g. call from org.jboss.seam.Component:840: if ( Modifier.isStatic( field.getModifiers() ) ) { Reflections.setAndWrap(field, null, logInstance); // <== HERE 'null' is passed as target } ) public static void set(Field field, Object target, Object value) throws Exception { try { field.set(target, value); } catch (IllegalArgumentException iae) { String message = "Could not set field value by reflection: " + toString(field) + " on: " + target.getClass().getName(); // <== HERE target == null -> NPE! /* snipped */ } } This appears in: cvs status Reflections.java =================================================================== File: Reflections.java Status: Up-to-date Working revision: 1.22 Repository revision: 1.22 /cvsroot/jboss/jboss-seam/src/main/org/jboss/seam/util/Reflections.java,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) You can reproduce the Bug when creating a bean: * import org.apache.commons.logging.Log instead of org.jboss.seam.log.Log * Inject the logger: @Logger private static Log log; Reflections.java:64: field.set(target, value); will throw an IllegalArgumentException because it can't assign the object because of type-mismatch -- 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, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1871) Documentation for OC4J 11g

by Pete Muir (JIRA)

Documentation for OC4J 11g -------------------------- Key: JBSEAM-1871 URL: http://jira.jboss.com/jira/browse/JBSEAM-1871 Project: JBoss Seam Issue Type: Task Reporter: Pete Muir - Build/deploy jee5/booking example to OC4J - Build/deploy seam-gen'd app to OC4J -- 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, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1859) messageformat error blows up

by Pierre Raoul (JIRA)

messageformat error blows up ---------------------------- Key: JBSEAM-1859 URL: http://jira.jboss.com/jira/browse/JBSEAM-1859 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Pierre Raoul When an EL expression is not closed by a brace, an error is thrown. It would be better to show the wrong expression as it is. -- 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, 7 months

3
4
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 August 2007