[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1751) Remoting doesn't appear to work with GlassFish
by Samuel Doyle (JIRA)
Remoting doesn't appear to work with GlassFish
----------------------------------------------
Key: JBSEAM-1751
URL: http://jira.jboss.com/jira/browse/JBSEAM-1751
Project: JBoss Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.0.0.BETA1
Environment: GlassFish V2 build 56 using IE Version 7 and Firefox 2.0 for testing
Reporter: Samuel Doyle
Assigned To: Shane Bryzak
Hi there,
I was trying to get remoting working with a project I am working on it was constantly failing without any indication of error in the Seam debug window or the server logs.
The Seam debug window indicates that the server side request is being invoked and looks fine but when testing the debug window just says response packet followed by nothing. My server method code never gets hit.
After playing around with my existing project for a bit I decided just to try the bare bones and the HelloWorld example in your head branch in cvs produced the same results. I have been using DWR up to this point and has proven to be reliable. Since I'm using Seam I would like to be able to use it for all the interactions including the JavaScript AJAX interactions with introducing additional frameworks.
I posted a lot more information on the forum. Please see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=114820 for more details.
--
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
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1641) redirect do proper page in pageflow as out of order request comes in
by Michael Kozak (JIRA)
redirect do proper page in pageflow as out of order request comes in
--------------------------------------------------------------------
Key: JBSEAM-1641
URL: http://jira.jboss.com/jira/browse/JBSEAM-1641
Project: JBoss Seam
Issue Type: Feature Request
Components: BPM
Reporter: Michael Kozak
I'll describe scenario.
Pages used in page flow "p1, p2, p3, pfinal".
Transitions:
p1 to p2
p2 to p3
p3 to pfinal
eg. p1 -> p2 -> p3 -> pfinal
p1 starts conversation, pfinal ends conversation
p2,p3,pfinal requires conversation.
Now let's consider out of order requests.
I enter page p1, conversation is started.
Next I point the browser manually to page p3 with cid included.
Page p3 is displayed with "garbage" - no logic in p2 was executed.
Buttons on page redirect to p1 of course.
Feature request: redirect the request to page p3 to go to proper page (p1 in this case).
This applies only when conversation is in progress as other requests are handled by no-conversation-view-id.
Seam has org.jboss.seam.core.pageflow in conversation scope with "page" and "node" properties set to "p1" but it seems that it is checked only on POST requests.
--
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
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1650) NPE thrown when attempting to configure pojo as Seam component
by Michael Youngstrom (JIRA)
NPE thrown when attempting to configure pojo as Seam component
--------------------------------------------------------------
Key: JBSEAM-1650
URL: http://jira.jboss.com/jira/browse/JBSEAM-1650
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.CR1
Reporter: Michael Youngstrom
Fix For: 2.0.0.CR1
NPE thrown when attempting to configure pojo as Seam component.
<component name="expanderState" class="java.util.HashMap" auto-create="true" scope="conversation"/>
throws:
java.lang.RuntimeException: Could not create Component: expanderState
at org.jboss.seam.init.Initialization.addComponent(Initialization.java:910)
at org.jboss.seam.init.Initialization.installComponents(Initialization.java:841)
at org.jboss.seam.init.Initialization.init(Initialization.java:508)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:448)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
Caused by:
java.lang.NullPointerException
at org.jboss.seam.init.DeploymentDescriptor.<init>(DeploymentDescriptor.java:33)
at org.jboss.seam.Seam.getEjbDescriptor(Seam.java:51)
at org.jboss.seam.Seam.getComponentType(Seam.java:102)
at org.jboss.seam.Component.<init>(Component.java:216)
at org.jboss.seam.Component.<init>(Component.java:207)
at org.jboss.seam.init.Initialization.addComponent(Initialization.java:896)
--
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
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1593) New processing for stateful bean @Destroy and @Remove causes problems.
by Chris Rudd (JIRA)
New processing for stateful bean @Destroy and @Remove causes problems.
----------------------------------------------------------------------
Key: JBSEAM-1593
URL: http://jira.jboss.com/jira/browse/JBSEAM-1593
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.BETA1
Reporter: Chris Rudd
I have an EJB that has several methods marked as @Remove, as I want the bean remove whenever those methods are executed.
One of which is marked as @Destroy, which is the ONLY one that should be called because the object is being destroyed (ie from a call to Component.destroy. The problem is that under the new processing rules the "defaultRemoveMethod is set to the last parameterless @Remove method.
I would suggest that the defaultRemoveMethod only be set to a "found @Remove" method if the @Destroy method has not been defined / does not have the @Remove annotation.
my class :
class Foo {
@Destroy
@Remove
public void cleanup() { /* does state cleanup*/ }
@Remove
public String removeEntity() { /* does some work*/ }
}
For this class cleanup is executed because its the destroy method, then removeEntity is executed since it was the last @Remove method found.
--
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
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1602) exception handler not recognizing end-conversation
by Hung Tang (JIRA)
exception handler not recognizing end-conversation
--------------------------------------------------
Key: JBSEAM-1602
URL: http://jira.jboss.com/jira/browse/JBSEAM-1602
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.BETA1
Environment: Seam-CVS
Reporter: Hung Tang
In my application, I'm using pages.xml exception handling mechanism to automatically end conversations when optimistic locking exceptions ever arise.
This is what I have
<exception class="javax.persistence.OptimisticLockException">
<end-conversation/>
<redirect view-id="/p/home.xhtml">
<message severity="ERROR">#{messages['concurrentmodification']}</message>
</redirect>
</exception>
However, when it does come up, the conversation is not ending as I want.
I could reproduce this error in the contact-list example. Just add begin propagation to the editContact and the exception handler will recognize it as a javax.persistence.PersistenceException, but it will not end the conversation as you have told it to.
--
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