[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3056) JPDL navigation and seam
by Florian Keusch (JIRA)
JPDL navigation and seam
------------------------
Key: JBSEAM-3056
URL: http://jira.jboss.com/jira/browse/JBSEAM-3056
Project: Seam
Issue Type: Task
Components: BPM
Reporter: Florian Keusch
hi
In our applications we have a navigation menu. When we use seam and some jpdl pageflows we have the following problem:
if we leave the pageflow with a <s:link propagation="end"> (e.g. clicking on the menu), then the pageflow conversation is ended but also an illegal navigation exception is thrown.
This issue was described on the seam framework: http://www.seamframework.org/Community/ProblemWithJPDLIllegalNavigation but I could not find it in this Jira.
It's not solved. In the code (PageFlow.java) there's a TODO where the illegal navigation ecxeption is thrown:
//now check that the restored view id matches what we expect
//from the pageflow node
//TODO: we need some way to disable this check, since users
// might want some adhoc nav in and out of a pageflow?
String viewId = Pages.getViewId(facesContext);
if ( !viewId.equals( getPage().getViewId() ) )
{
illegalNavigationError();
}
If we use <s:link propagation="none"> in our menu navigation then this will not cause a illegal navigation exception, but in the background the conversations are still there not ended.
fke
--
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
16 years, 10 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2232) Reduce debug log level for events
by Christian Bauer (JIRA)
Reduce debug log level for events
---------------------------------
Key: JBSEAM-2232
URL: http://jira.jboss.com/jira/browse/JBSEAM-2232
Project: JBoss Seam
Issue Type: Task
Components: Core
Reporter: Christian Bauer
Priority: Critical
Debug logging with Seam 2.x is completely useless. The most critical information in the debug log is the instantiation and lookup of components, however, if you enable DEBUG for
org.jboss.seam.Component, you get thousands of these:
12:26:06,282 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events
12:26:06,282 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events
12:26:06,282 DEBUG [Component] done initializing: org.jboss.seam.core.events
We need to exclude the event firing from debug logging, even if we hardcode it. And, are these events really useful? I have no idea why and when I'd want to listen to "context variable initialized" events.
--
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
16 years, 10 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2616) <s:transformImageSize> fills transparent areas with white background
by Manfred Gleirscher (JIRA)
<s:transformImageSize> fills transparent areas with white background
--------------------------------------------------------------------
Key: JBSEAM-2616
URL: http://jira.jboss.com/jira/browse/JBSEAM-2616
Project: JBoss Seam
Issue Type: Bug
Components: JSF Controls
Affects Versions: 2.0.0.GA
Environment: Windows, Jboss 4.2.1, Facelets
Reporter: Manfred Gleirscher
Priority: Minor
if a png-image containing transparent areas is scaled, the transparent areas get filled with white color.
I created my own transformImageSize-component which works properly.
Its applyTransformation method looks like that:
<code>
public void applyTransform(Image image) throws IOException {
...........
BufferedImage in = image.getBufferedImage();
GraphicsConfiguration gc = in.createGraphics().getDeviceConfiguration();
BufferedImage out = gc.createCompatibleImage(scaledWidth, scaledHeight,
Transparency.BITMASK);
Graphics2D g2d = out.createGraphics();
g2d.setComposite(AlphaComposite.Src);
g2d.setRenderingHint(RenderingHints.KEY_INTERPOLATION,
RenderingHints.VALUE_INTERPOLATION_BICUBIC);
g2d.drawImage(in, 0, 0, scaledWidth, scaledHeight, null);
g2d.dispose();
image.setBufferedImage(out);
}
</code>
--
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
16 years, 11 months