[JBoss JIRA] Created: (SEAMREMOTING-3) Seam Remoting does not compile on Java 5
by Jozef Hartinger (JIRA)
Seam Remoting does not compile on Java 5
----------------------------------------
Key: SEAMREMOTING-3
URL: https://jira.jboss.org/jira/browse/SEAMREMOTING-3
Project: Seam Remoting
Issue Type: Bug
Affects Versions: 3.0.0.Beta1
Environment: Java 1.5.0_19
Apache Maven 2.2.1
Reporter: Jozef Hartinger
Fix For: 3.0.0.CR1
[INFO] Compilation failure
/home/jharting/jboss/Seam_3/modules/remoting/core/src/main/java/org/jboss/seam/remoting/model/Model.java:[159,62] cannot find symbol
symbol : method isEmpty()
location: class java.lang.String
/home/jharting/jboss/Seam_3/modules/remoting/core/src/main/java/org/jboss/seam/remoting/Call.java:[61,62] cannot find symbol
symbol : method isEmpty()
location: class java.lang.String
/home/jharting/jboss/Seam_3/modules/remoting/core/src/main/java/org/jboss/seam/remoting/ExecutionHandler.java:[71,67] cannot find symbol
symbol : method isEmpty()
location: class java.lang.String
/home/jharting/jboss/Seam_3/modules/remoting/core/src/main/java/org/jboss/seam/remoting/model/ModelHandler.java:[84,70] cannot find symbol
symbol : method isEmpty()
location: class java.lang.String
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3493) The EntityHome should not preserve the value of its instance property after entering a nested transaction when having the @PerNestedConversation annotation
by Francisco Jose Peredo Noguez (JIRA)
The EntityHome should not preserve the value of its instance property after entering a nested transaction when having the @PerNestedConversation annotation
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3493
URL: https://jira.jboss.org/jira/browse/JBSEAM-3493
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.2.SP1
Reporter: Francisco Jose Peredo Noguez
I have a reflective 1-n associations like
Person childof Person.
I would like to create a child from the PersonEdit.xhtml created by seam-gen then adapted by hands...
When I put @PerNestedConversation annotation to my PersonHome the behavior seems to be ok: Each conversation has it's own instance of PersonHome BUT: all of those instances is wired to the same instance of Person (the Entity)...
I've tried to trace modifications on the "instance" field of Home but it's never setted so it should stay to null and then call my createInstance() overrided method....but this never happen because (as I said) Person instance is the same as the parent conversation one....
Did I miss something?
Or is this a limitation of the CRUD framework?
nowhere on the code the field "instance" is setted so I believe this is due to javassist proxying that my eclipse debugger can't see...
If this feature isn't working how would you implement my "Create child" button to create a new Person has a child of the current conversation "personHome.instance" ?...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBSEAM-4601) Seambay example - web services page doesn't work with JBossAS 6.0.0.M2
by Martin Gencur (JIRA)
Seambay example - web services page doesn't work with JBossAS 6.0.0.M2
----------------------------------------------------------------------
Key: JBSEAM-4601
URL: https://jira.jboss.org/jira/browse/JBSEAM-4601
Project: Seam
Issue Type: Bug
Components: Examples
Affects Versions: 2.2.1.CR1
Environment: JBossAS 6.0.0.M2
Reporter: Martin Gencur
Unable to invoke any of the services on web services test page.
For example: login as demo/demo after selecting login service. The result is the following stacktrace in the response area:
<html><head><title>JBoss Web/3.0.0-beta-2 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 404 - /jboss-seam-bay-jboss-seam-bay/AuctionService</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>/jboss-seam-bay-jboss-seam-bay/AuctionService</u></p><p><b>description</b> <u>The requested resource (/jboss-seam-bay-jboss-seam-bay/AuctionService) is not available.</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/3.0.0-beta-2</h3></body></html>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months