Forge 1.0.1.Final Released
by Lincoln Baxter, III
http://jboss.org/forge
Now with support for scaffolding reverse-engineered database Models. Over
22 features/bugs/issues completed. Thanks to Pete Muir, Burr, and Koen Aers
for being the uber-usability-testers. Special thanks to Thomas Fruebeck and
Richard Kennard for fixing the scaffolding custom @Id fields issue, and for
everyone else who made this release a success.
Start writing plugins for your projects! ;)
https://docs.jboss.org/author/display/FORGE/Reference+the+Forge+APIs
Bug
- [FORGE-486 <https://issues.jboss.org/browse/FORGE-486>] - Scaffolding
an entity with an enum fails
- [FORGE-490 <https://issues.jboss.org/browse/FORGE-490>] - Cannot
access configuration outside of an active Project context
- [FORGE-491 <https://issues.jboss.org/browse/FORGE-491>] - REST plugin
creates compilation errors when "id" setter is not called "setId()"
- [FORGE-492 <https://issues.jboss.org/browse/FORGE-492>] - REST facet
does not recognize Application class with ApplicationPath annotation
- [FORGE-493 <https://issues.jboss.org/browse/FORGE-493>] - ServletFacet
requires web.xml to detect servlet environment
- [FORGE-497 <https://issues.jboss.org/browse/FORGE-497>] - EJB facet
requires JTA API in POM
- [FORGE-498 <https://issues.jboss.org/browse/FORGE-498>] - faces setup
fails if faces-config.xml already exists
- [FORGE-501 <https://issues.jboss.org/browse/FORGE-501>] - Faces
scaffold creates compilation errors when "id" getter is not called "getId()"
- [FORGE-503 <https://issues.jboss.org/browse/FORGE-503>] - Erroneous
f:convertNumber added
- [FORGE-506 <https://issues.jboss.org/browse/FORGE-506>] - Ensure all
plugins use same style of dependencyManagement
- [FORGE-512 <https://issues.jboss.org/browse/FORGE-512>] - Scaffold
setup should ensure JSF API is installed
- [FORGE-513 <https://issues.jboss.org/browse/FORGE-513>] -
AnnotationImpl.removeValue(String) does nothing
- [FORGE-514 <https://issues.jboss.org/browse/FORGE-514>] - Scaffold
targetDir should be stored from setup
- [FORGE-515 <https://issues.jboss.org/browse/FORGE-515>] - Scaffold
targetDir does not relocate index.html and index.xhtml
- [FORGE-516 <https://issues.jboss.org/browse/FORGE-516>] -
org.jboss.modules.ModuleNotFoundException: Module not found in local module
loader
- [FORGE-519 <https://issues.jboss.org/browse/FORGE-519>] - Cannot
execute scaffolding after installing a plugin
Enhancement
- [FORGE-496 <https://issues.jboss.org/browse/FORGE-496>] -
--scaffoldType faces redundant
Feature Request
- [FORGE-213 <https://issues.jboss.org/browse/FORGE-213>] - Java EE6
Full Project (follows the EE6 full profile)
- [FORGE-305 <https://issues.jboss.org/browse/FORGE-305>] - Forge should
inform users when they are attempting to run on an unsupported JRE version
- [FORGE-458 <https://issues.jboss.org/browse/FORGE-458>] - Specify
prefix or target directory for generated CRUD so as to not clobber existing
app
- [FORGE-489 <https://issues.jboss.org/browse/FORGE-489>] - Should be
able to define/specify one or more "plugin directories" from which to load
plugins during bootstrap
Task
- [FORGE-337 <https://issues.jboss.org/browse/FORGE-337>] - Document
scaffolding usage, and how to enhance application beyond generated pages
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
13 years, 10 months
- 2
- 1
Problem with unmarshalling resource with jaxb unmarshaller
by Max Schwaab
Hey there,
I've got another tricky problem with my hibersap plugin
I'm using the HibersapJaxbXmlParser to parse a hibersap.xml file.
What the parser does is the following:
* creating a JAXB context [ jaxbContext = JAXBContext.newInstance(
HibersapConfig.class ); ]
* creating a JAXB unmarshaller [ unmarshaller =
jaxbContext.createUnmarshaller(); ]
* unmarshall the given resource stream [ unmarshalledObject =
unmarshaller.unmarshal( resourceStream ); ]
The problem is:
It unmarshalles the file to the correct class, but some content gets lost.
The funny thing:
If I try this in a seperate test without forge, it works!
The test is part of the plugin and can be found at the github repo
(https://github.com/forge/plugin-hibersap)
What I want it to do:
Unmarshall a hibersap.xml file and recognize the hibersap config AND the
session manager in the config.
Within Forge it seems to recognize only the hibersap config and not the
session manager.
The hibersap.xml is something like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<hibersap xmlns="http://hibersap.org/xml/ns/hibersap-config">
<session-manager name="SM001">
<context>org.hibersap.execution.jco.JCAContext</context>
.
.
.
</session-manager>
</hibersap>
Here is the code from the HibersapJaxbXmlParser:
public HibersapConfig parseResource( final InputStream resourceStream,
final String resourceName )
throws HibersapParseException
{
Unmarshaller unmarshaller;
try
{
unmarshaller = jaxbContext.createUnmarshaller();
}
catch ( final JAXBException e )
{
throw new InternalHiberSapException( "Cannot create an
unmarshaller. ", e );
}
Object unmarshalledObject;
try
{
unmarshalledObject = unmarshaller.unmarshal( resourceStream );
}
catch ( final JAXBException e )
{
throw new HibersapParseException( "Cannot parse the
resource " + resourceName, e );
}
if ( unmarshalledObject == null )
{
throw new HibersapParseException( "Resource " +
resourceName + " is empty." );
}
if ( !( unmarshalledObject instanceof HibersapConfig ) )
{
throw new HibersapParseException( "Resource " + resourceName
+ " does not consist of a hibersap specification. I
found a "
+ unmarshalledObject.getClass().getSimpleName() );
}
return ( HibersapConfig ) unmarshalledObject;
}
Thank you for your help and best regards
Max
13 years, 10 months
- 2
- 4
As7 Deploy command is failing for me...
by Anand S. Anandan
I am new Forge as well as Java and JBoss. When I execute the as7 deploy command I get the following error. I am assuming forge will download and install JBoss AS7 image. Or should I install JBoss AS7 before hand for this command to work. I appreciate any help. As well if you can point me to any documentation on this, I will appreciate it. Thank you.
[INFO] Executing goal deploy on server localhost (127.0.0.1) port 9999.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.683s
[INFO] Finished at: Sat Mar 03 10:27:49 CST 2012
[INFO] Final Memory: 25M/61M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.1.0.
CR1:deploy (default-cli) on project stest: Could not execute goal deploy on stes
t.war. Reason: java.net.ConnectException: JBAS012174: Could not connect to remot
e://localhost:9999. The connection failed: Connection refused: no further inform
ation -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
xception
[stest] stest $
13 years, 10 months
- 2
- 2
- ← Newer
- 1
- Older →