July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-889) Cannot parse package-info.java

by Yann Albou (JIRA)

[ https://issues.jboss.org/browse/FORGE-889?page=com.atlassian.jira.plugin.... ] Yann Albou commented on FORGE-889: ---------------------------------- new one: https://github.com/forge/java-parser/pull/4 > Cannot parse package-info.java > ------------------------------ > > Key: FORGE-889 > URL: https://issues.jboss.org/browse/FORGE-889 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.2.3.Final, 2.0.0.Alpha3 > Reporter: Yann Albou > Fix For: 1.3.3.Final, 2.0.0.Alpha7 > > > The parsing of package-info.java file (see http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/javadoc.html...) raises the following exeption: > "org.jboss.forge.parser.ParserException: Could not find type declaration in Java source - is this actually code?" > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-889) Cannot parse package-info.java

by Yann Albou (JIRA)

[ https://issues.jboss.org/browse/FORGE-889?page=com.atlassian.jira.plugin.... ] Yann Albou updated FORGE-889: ----------------------------- Git Pull Request: https://github.com/forge/java-parser/pull/4 (was: https://github.com/forge/java-parser/pull/3) > Cannot parse package-info.java > ------------------------------ > > Key: FORGE-889 > URL: https://issues.jboss.org/browse/FORGE-889 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.2.3.Final, 2.0.0.Alpha3 > Reporter: Yann Albou > Fix For: 1.3.3.Final, 2.0.0.Alpha7 > > > The parsing of package-info.java file (see http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/javadoc.html...) raises the following exeption: > "org.jboss.forge.parser.ParserException: Could not find type declaration in Java source - is this actually code?" > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-889) Cannot parse package-info.java

by Yann Albou (JIRA)

[ https://issues.jboss.org/browse/FORGE-889?page=com.atlassian.jira.plugin.... ] Yann Albou updated FORGE-889: ----------------------------- Git Pull Request: https://github.com/forge/java-parser/pull/3 (was: https://github.com/forge/java-parser/pull/1) > Cannot parse package-info.java > ------------------------------ > > Key: FORGE-889 > URL: https://issues.jboss.org/browse/FORGE-889 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.2.3.Final, 2.0.0.Alpha3 > Reporter: Yann Albou > Fix For: 1.3.3.Final, 2.0.0.Alpha7 > > > The parsing of package-info.java file (see http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/javadoc.html...) raises the following exeption: > "org.jboss.forge.parser.ParserException: Could not find type declaration in Java source - is this actually code?" > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-889) Cannot parse package-info.java

by Yann Albou (JIRA)

[ https://issues.jboss.org/browse/FORGE-889?page=com.atlassian.jira.plugin.... ] Yann Albou commented on FORGE-889: ---------------------------------- Hi George, Based on your comments, here is my 2nd pull request: https://github.com/forge/java-parser/pull/3 Thanks > Cannot parse package-info.java > ------------------------------ > > Key: FORGE-889 > URL: https://issues.jboss.org/browse/FORGE-889 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.2.3.Final, 2.0.0.Alpha3 > Reporter: Yann Albou > Fix For: 1.3.3.Final, 2.0.0.Alpha7 > > > The parsing of package-info.java file (see http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/javadoc.html...) raises the following exeption: > "org.jboss.forge.parser.ParserException: Could not find type declaration in Java source - is this actually code?" > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-916) Faces scaffold does not handle deletion of entities with bidirectional relationships

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-916?page=com.atlassian.jira.plugin.... ] Vineet Reynolds closed FORGE-916. --------------------------------- Resolution: Done > Faces scaffold does not handle deletion of entities with bidirectional relationships > ------------------------------------------------------------------------------------ > > Key: FORGE-916 > URL: https://issues.jboss.org/browse/FORGE-916 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.5.Final, 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.2.Final > > > The generated Faces scaffold contains code to handle deletion. But this works only for some scenarios. > For bidirectional relationships, the generated code in the View Beans should perform deletion on both sides of the relationship. Currently, this is performed on only one side - the side corresponding to the view from where deletion was triggered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-916) Faces scaffold does not handle deletion of entities with bidirectional relationships

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-916?page=com.atlassian.jira.plugin.... ] Vineet Reynolds commented on FORGE-916: --------------------------------------- [~k.arun406] I'm closing this. Please track FORGE-974 for the issue you're describing. > Faces scaffold does not handle deletion of entities with bidirectional relationships > ------------------------------------------------------------------------------------ > > Key: FORGE-916 > URL: https://issues.jboss.org/browse/FORGE-916 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.5.Final, 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.2.Final > > > The generated Faces scaffold contains code to handle deletion. But this works only for some scenarios. > For bidirectional relationships, the generated code in the View Beans should perform deletion on both sides of the relationship. Currently, this is performed on only one side - the side corresponding to the view from where deletion was triggered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-916) Faces scaffold does not handle deletion of entities with bidirectional relationships

by Arun Kumar Kandakatla (JIRA)

[ https://issues.jboss.org/browse/FORGE-916?page=com.atlassian.jira.plugin.... ] Arun Kumar Kandakatla edited comment on FORGE-916 at 7/7/13 2:22 PM: --------------------------------------------------------------------- Hi, I am unable to delete the records in bidirectional relationship. Simulation Steps. First create a web-project(name: sample) 1. Create entity User.java with firstName and lastName as string fields. 2. Create entity Address.java with addressType, street, city, State and zip as string fields. 3. Create bidirectional oneToMany relationship between User and Address entities. 4. Generate the code using Scaffold from-entity. 5. Build the project and deploy in jboss AS 7. 6. Open the application in browser. 7. Create the user with multiple Addresses and save. 8. Now try to edit the user and add additional Address record using + command link. Dont click on save. 9. Try to remove the newly added record. record never get deleted. 10. But able to delete the old address records. was (Author: k.arun406): Hi, I am unable to delete the records in bidirectional relationship. Simulation Steps. 1. Create entity User.java with firstName and lastName as string fields. 2. Create entity Address.java with addressType, street, city, State and zip as string fields. 3. Create bidirectional oneToMany relationship between User and Address entities. 4. Generate the code using Scaffold from-entity. 5. Build the project and deploy in jboss AS 7. 6. Open the application in browser. 7. Create the user with multiple Addresses and save. 8. Now try to edit the user and add additional Address record using + command link. Dont click on save. 9. Try to remove the newly added record. record never get deleted. 10. But able to delete the old address records. > Faces scaffold does not handle deletion of entities with bidirectional relationships > ------------------------------------------------------------------------------------ > > Key: FORGE-916 > URL: https://issues.jboss.org/browse/FORGE-916 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.5.Final, 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.2.Final > > > The generated Faces scaffold contains code to handle deletion. But this works only for some scenarios. > For bidirectional relationships, the generated code in the View Beans should perform deletion on both sides of the relationship. Currently, this is performed on only one side - the side corresponding to the view from where deletion was triggered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-916) Faces scaffold does not handle deletion of entities with bidirectional relationships

by Arun Kumar Kandakatla (JIRA)

[ https://issues.jboss.org/browse/FORGE-916?page=com.atlassian.jira.plugin.... ] Arun Kumar Kandakatla reopened FORGE-916: ----------------------------------------- Hi, I am unable to delete the records in bidirectional relationship. Simulation Steps. 1. Create entity User.java with firstName and lastName as string fields. 2. Create entity Address.java with addressType, street, city, State and zip as string fields. 3. Create bidirectional oneToMany relationship between User and Address entities. 4. Generate the code using Scaffold from-entity. 5. Build the project and deploy in jboss AS 7. 6. Open the application in browser. 7. Create the user with multiple Addresses and save. 8. Now try to edit the user and add additional Address record using + command link. Dont click on save. 9. Try to remove the newly added record. record never get deleted. 10. But able to delete the old address records. > Faces scaffold does not handle deletion of entities with bidirectional relationships > ------------------------------------------------------------------------------------ > > Key: FORGE-916 > URL: https://issues.jboss.org/browse/FORGE-916 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.5.Final, 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.2.Final > > > The generated Faces scaffold contains code to handle deletion. But this works only for some scenarios. > For bidirectional relationships, the generated code in the View Beans should perform deletion on both sides of the relationship. Currently, this is performed on only one side - the side corresponding to the view from where deletion was triggered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-998) xml-parser: Ability to insert an xml node after or before another one

by Yann Albou (JIRA)

Yann Albou created FORGE-998: -------------------------------- Summary: xml-parser: Ability to insert an xml node after or before another one Key: FORGE-998 URL: https://issues.jboss.org/browse/FORGE-998 Project: Forge Issue Type: Enhancement Components: Parsers / File Manipulation Affects Versions: 2.0.0.Alpha6, 1.3.2.Final Reporter: Yann Albou Ability to insert an xml node after or before another one. For instance in the web.xml file when we want to add a new servlet + servlet-mapping nodes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-997) bean new-bean not working for all types

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-997?page=com.atlassian.jira.plugin.... ] Vineet Reynolds commented on FORGE-997: --------------------------------------- Thanks for catching this. I think it would be appropriate to respond with a more suitable error message here (and for other reserved words). Even if a new bean were to be created, the 'import' keyword would be in the incorrect context, thus rendering the class syntactically invalid. The only suitable way of handling this is to validate the user inputs (and the generated code). > bean new-bean not working for all types > --------------------------------------- > > Key: FORGE-997 > URL: https://issues.jboss.org/browse/FORGE-997 > Project: Forge > Issue Type: Bug > Affects Versions: 1.3.2.Final > Environment: Eclipse Kepler + Jboss tools 4 > Reporter: Hubert Schumacher > > forge command "beans new-bean --type abc.import.cde.ExampleJava" throws exception if type has 'import' in its path. Maybe other magic words as well?! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2013