Francesco Marchioni

If you are interested to migrate to JSF there are many tools that let generate the web pages directly from a database schema. Take a look at JBoss Forge f.e.
BTW also Netbeans has got some nice plugins for generating JSF from a DB schema. See this tutorial about building a Java EE app from a DB schema
regards

Answering to your first question- I'm afraid it's not possible out of the box as it would require an URLClassloader to pickup at runtime classes. You could write a new Classloader and deploy it into the application server though- but I'm not pretty sure it is going to work.

If you mean invoke a Servlet, a simple form Submit (pointing to the Servlet in the action) will do it.
If you want to embed the Servlet within the JSP then you could add:
<jsp:include page="/servletURL" />
Hope it helps

I'd suggest the Advanced JAX-WS Web services book which has been just published by Alessio Soldano, which is the JBossWS project lead. I've read it and found really an excellent and well written book.
Hope it helps

Hi Al!
sorry for late reply. Well as far as it concerns the main issue, that is deployment timeout, you can configure it via the deployment-timeout attribute. For example, the following CLI sets the deployment timeout to 100 seconds (default 60)

/subsystem=deployment-scanner/scanner=default:write-attribute(name="deployment-timeout ",value=100)
Although I have not tested it, you could use a BeanShell expression for the attribute and set it at server startup (for example via the -D argument):
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="${deployment.timeout:100}"/>
If you fail to start the application server due to an Eclipse timeout, I remember about writing it on a tutorial how to change the Eclipse timeout.
Lastly, about the jBPM upgrade unfortunately I cannot help further, I've come across this issue on the jBPM forums and I believed that an upgrade to jBPM 5.4 could help. Sorry.

Hope it helps,
Best regards
Francesco

It was great being with you here. I'll be be around JavaRanch in the future as well checking for interesting topics.
All the best and congrats to the winners!
Francesco

Al Koch wrote:

2) It often takes 3 to 4 attempts to launch JBoss 7. The Kepler console shows about 600+ lines of output but I cannot see anything that reveals why we fail to launch. All I do is try again and after a couple of tries we finally launch and deploy. Note however, on some days we do launch on the 1st try! Do you know if Wildfly will be more reliable when launched? Here is an excerpt:
11:58:26,467 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "jbpm-human-task-war.war" was rolled back with no failure message 11:58:26,467 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "jbpm-gwt-console.war" was rolled back with no failure message 11:58:26,467 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "jbpm-gwt-console-server.war" was rolled back with no failure message 11:58:26,467 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "jbpm-form-builder.war" was rolled back with no failure message 11:58:26,467 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "drools-guvnor.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"drools-guvnor.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"drools-guvnor.war\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"drools-guvnor.war\""}} 11:58:26,467 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "designer.war" was rolled back with no failure message

Hi Al,
sorry for late reply due to different time zones :-)
Well jaikiran already replied for two points. About point 2) I'd suggest at first investigating on the jBPM side, by upgrading your jBPM runtime. I've found some threads that are discussing about similar issues and managed to solve it by upgrading jBPM. Yet you should anyway include a deployment timeout when deploying jBPM artifacts to avoid locking up the application server.
Hope it helps
Francesco

Linda Dimartino wrote:
-Does the book contains examples about the new role based access control ?

Yes RBAC it's a core new feature of WildFly 8 therefore it is discussed in detail showing off the role capabilities at different levels (Standalone RBAC, Server Group Scoped RBAC, Host Scoped RBAC)

Linda Dimartino wrote:
-About developing application, does this book contains hints for developing applications on WildFly ?

No the book focus on Server Administration. In the near future (Q2 of this year) a Java EE 7 Development with WildFly is going to be published and in Q3 a WildFly Tuning book as well.
Stay tuned :-)

Sai Hegde wrote:

Jaikiran Pai wrote:Furthermore, Wildfly now only uses a single port (8080 by default) for all communication and is backed by the HTTP upgrade feature.

Love this feature.

Yes cloud users will love this feature a lot :-)

As an addition, you should also check that your application does not contain a "pruned" technologies in the Java EE 7 specification (See section EE.6.1.3 Pruned Java Technologies of java EE specification) which are not mandatory to implement. For example Entity EJB 2.1 won't deploy on WildFly (See https://issues.jboss.org/browse/AS7-4100)
Hope it helps
Francesco

Hi Sai,
post your question in the thread: https://coderanch.com/t/631454/JBoss/WildFly-Administration-Guide
You will get a reply and a chance to win WildFly's book ;-)
Regards
Francesco

Hi Rogerio,
well I haven't a deep knowledge of Google App Engine but AFAIK it's a framework that leverages standard Web components like Servlets, JPA, Java Mail, etc. So as long as you are using standard Java EE components in your Google App Engine it won't be too difficult migrating your applications to JBoss/WildFly. Other components like JDO still can be installed in JBoss/Wildfly but that's not out of the box. see for example: https://community.jboss.org/wiki/GettingStartedWithJDOOnJbossAS7InSevenSteps
Hope it helps
Francesco

Hi Paul,
well, it's not a departure from the AS7 route but it does contain several enhancements mostly in Security Area (the new Role Base Access Control), in the Management Area (Port reduction, just one port for managing the application server) and a new Web server implementation named Undertow web server which can run inside the application server or even standalone. From the developer's point of view, it is a Java EE 7 compliant container, which means lots of new API for your applications.
Hope it helps
Regards
Francesco

Hi guys,
glad to be here again with you. Feel free to shoot questions, I'll be sitting in the ranch waiting for them ;-)

Hi all!
Just a short note to inform you that tomorrow there will be on JavaRanch a giveaway for the WildFly 8 Administration Guide. No Jokes, even if it's 1st April ;-)
Don't miss it!
Francesco