September 2010 - jboss-user - Jboss List Archives

by Tomás Lobo

Tomás Lobo [http://community.jboss.org/people/jtomaslobo] created the discussion "Is jBPM supposed to..." To view the discussion, visit: http://community.jboss.org/message/560978#560978 -------------------------------------------------------------- Hello guys, I've been asked to research on GUI automation tools for a software enterprise. They asked me to find a tool that could be able to: - Record a mouse-keyboard sequence on ASPx and VB 6 screens, which will generate me some results that must be automatically checked - Query data from a database or a notepad, so it can be used as input to obtain some screen output that also must be checked Is jBPM suitable for this job? I would really appreciate your help. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/560978#560978] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 7 months

2
3
0 / 0

[JBoss Tools] - Re: How to make JSF components do nice previews?

by Denis Golovin

Denis Golovin [http://community.jboss.org/people/dgolovin] created the discussion "Re: How to make JSF components do nice previews?" To view the discussion, visit: http://community.jboss.org/message/561261#561261 -------------------------------------------------------------- Do you mean icons on components palette, don't you? Yo can take a look at plug-ins for spring JSF components here https://anonsvn.jboss.org/repos/jbosstools/trunk/vpe/plugins/org.jboss.to... https://anonsvn.jboss.org/repos/jbosstools/trunk/vpe/plugins/org.jboss.to... or more complex example for Richfaces JSF Components here https://anonsvn.jboss.org/repos/jbosstools/trunk/jsf/plugins/org.jboss.to... https://anonsvn.jboss.org/repos/jbosstools/trunk/jsf/plugins/org.jboss.to.... They should be pretty explanatory. I guess they might be added through extension point, but I cannot tell now for sure. I'll check this out and answer later. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/561261#561261] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 7 months

1
0
0 / 0

[EJB 3.0] - Deploying ejb3.0 jars with ejb2.1 jars

by Anurag Bhatia

Anurag Bhatia [http://community.jboss.org/people/ab_99] created the discussion "Deploying ejb3.0 jars with ejb2.1 jars" To view the discussion, visit: http://community.jboss.org/message/561345#561345 -------------------------------------------------------------- I am trying to deploying ejb3.0 jars with ejb2.1 jars in an ear file. I keep geting this warning - 17:38:54,245 WARN [EjbUtil] DeploymentInfo org.jboss.deployment.DeploymentInfo@484e0b4d { url=file:/C:/tools/jboss-4.2.2.GA/server/CustomServer/tmp/deploy/tmp1967561862872673155100customapp.ear-contents /customgroupsEJB.jar } deployer: MBeanProxyExt[jboss.ejb3:service=EJB3Deployer] status: Deployed state: STARTED watch: file:/C:/tools/jboss-4.2.2.GA/server/CustomServer/tmp/deploy/tmp1967561862872673155100customapp.ear-contents/customgroupsEJB.jar altDD: null lastDeployed: 1284120495856 lastModified: 1284120489372 mbeans: is not an EJB .jar file! The jar that contains the ejb3 beans is never deployed properly. I donot have any ejb-jar.xml in the jar that contains the ejb3 sessin bean. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/561345#561345] Start a new discussion in EJB 3.0 at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 7 months

1
0
0 / 0

[jBPM] - Re: Duedate expressions in the past

by Alejandro Guizar

Alejandro Guizar [http://community.jboss.org/people/alex.guizar%40jboss.com] created the discussion "Re: Duedate expressions in the past" To view the discussion, visit: http://community.jboss.org/message/561415#561415 -------------------------------------------------------------- The patch contibuted by Per Christian Henden in http://https://jira.jboss.org/browse/JBPM-2813 JBPM-2813 addresses the past due date problem, returning the current date instead. This update will be delivered with jBPM 4.5. We have not settled on a release date yet, but you can download a stable snapshot from the https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbp... Maven repository. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/561415#561415] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 7 months

1
0
0 / 0

[Beginner's Corner] - Looking for Examples

by Marco Barber

Marco Barber [http://community.jboss.org/people/violentstormm] created the discussion "Looking for Examples" To view the discussion, visit: http://community.jboss.org/message/560592#560592 -------------------------------------------------------------- Hi, Im really new to the jboss AS and want to test the performance on different hardware. Therefor Im looking for some good applications or examples, which takes the AS to the limit. I've found some good examples bundled with the SEAM framework but they are not complex enogh. So please tell me some good examples or applications :-) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/560592#560592] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 7 months

3
2
0 / 0

[Beginner's Corner] - Unable to Add New Queue through Admin Console (AS 5.1)

by William Folger

William Folger [http://community.jboss.org/people/whf3] created the discussion "Unable to Add New Queue through Admin Console (AS 5.1)" To view the discussion, visit: http://community.jboss.org/message/561212#561212 -------------------------------------------------------------- In the process of evaluating JBoss AS for SOA platform. Anyway, just installed JBoss AS 5.1 and went to the admin console and tried to add a queue @ JMS Destinations > Queues. When I try to add one I get the following error: Failed to add Resource (see app server log for additional details): java.lang.RuntimeException:Failed to process template. -> java.lang.RuntimeException:java.io.FileNotFoundException: C:\Software\JBoss\jboss-5.1.0.GA\server\default\deploy\queue\Test-service.xml (The system cannot find the path specified) -> java.io.FileNotFoundException:C:\Software\JBoss\jboss-5.1.0.GA\server\default\deploy\queue\Test-service.xml (The system cannot find the path specified) I understand the error and even tried a work around by manually creating that XML but then the queue was not bound when I did the jndi lookup. In any event, I would assume that adding a queue through the Admin Console would be straight forward and without such errors? Is there somethign wrong with my install? Any thoughts? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/561212#561212] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 7 months

1
0
0 / 0

[JBoss Tools] - Create GWT Projects with JBoss Tools and Eclipse WTP

by Andre Dietisheim

Andre Dietisheim [http://community.jboss.org/people/adietish] modified the document: "Create GWT Projects with JBoss Tools and Eclipse WTP" To view the document, visit: http://community.jboss.org/docs/DOC-15794 -------------------------------------------------------------- h1. Use Eclipse WTP, get there with the standard If you want to create GWT applications you unfortunately cannot do it the WTP way and create a so called dynamic web project. The Google plugins implement their own set of views, wizards, launchers and mostly duplicate what's already present and defacto standard in WTP. The consequence is that you'd have to deal with workarounds if you want to get functionalities (run/deploy on JBoss etc.) Google does not offer. We therefore developed an experimental integration plugin for GWT that allows you to create GWT projects in the way most Eclipse users are used to: by creating Dynamic Web Projects. h1. Preface Eclipse offers nice tools to create web applications. The base framework's what we call the Eclipse Web Tools Platform (WTP). Eclipse WTP delivers a standard for most aspects involved when you create web applications. The google web toolkit, GWT, is a nice framework to develop web applications. Google delivers a plugin for Eclipse and developing with GWT is a very pleasant experience. The GWT plugin uses an embedded jetty to run the application that you develop. Google unfortunately did not base its work on Eclipse WTP and does not comply to the Eclipse project structure for web application. So if you want to use JBoss instead of jetty, the approach to take is not as handy and intuitive as it could be. Furthermore there's no way to use and integrate into plugins that other solution providers offer. You mostly have to proceed by workarounds to get what Google does not offer. We developed a set of (experimental) plugins that create GWT projects by extending Eclipse WTP. Our plugins implement well known usage patterns and integrate well with all Eclipse components that use the common standard for web projects. The most obvious benefit is that deploying to JEE application servers (and JBoss partcullarly) is as easy as it is with any other web project. h1. Solution Install and use the JBoss GWT Integration. You'll then be able to create GWT projects the WTP way and fully enjoy it's full-blow features and standardized usage patterns. This How-To shows you all the steps to install the plugins and how to create a dynamic web project that's GWT enabled. h2. Install JBoss GWT Integration Add the Google Eclipse Plugins update site: > http://dl.google.com/eclipse/plugin/3.6/ http://dl.google.com/eclipse/plugin/3.6/ Add the JBoss Tools update site: > http://download.jboss.org/jbosstools/updates/nightly/jbosstools-3.2.0.M2/ http://download.jboss.org/jbosstools/updates/nightly/jbosstools-3.2.0.M2/ And Install the JBoss GWT Integration http://community.jboss.org/servlet/JiveServlet/showImage/6254/Picture+4.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6254/Picture... h2. Create a Dynamic Web Application Project Make sure you have a JEE server (JBoss application server for instance) in your Eclipse environment. If not, download and declare it to your Eclipse IDE: http://community.jboss.org/servlet/JiveServlet/showImage/6260/Picture+12.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6260/Picture... http://community.jboss.org/servlet/JiveServlet/showImage/6259/Picture+11.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6259/Picture... You're now ready to create a *Dynamic Web Project*. http://community.jboss.org/servlet/JiveServlet/showImage/6256/Picture+5.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6256/Picture... The wizard picks your server (runtime) and allows you to configure the various characteristic of your web project. The *configuration* group allows you to pick the different facets of your project. We provide a *Google Web Toolkit* facet that will configure the GWT related characteristics. Hit *Modify...* http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-16-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-16... and select the *Google Web Toolkit* facet. http://community.jboss.org/servlet/JiveServlet/showImage/6262/Picture+14.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6262/Picture... A few wizard steps further, you may choose to get some GWT *sample code*. http://community.jboss.org/servlet/JiveServlet/showImage/6411/generate-sa... http://community.jboss.org/servlet/JiveServlet/downloadImage/6411/generat... You get the Hello World sample that you get when you use the Google Wizard. We just put it to the *WebContent* folder you configured in your Dynamic Web Project wizard (WTP default opposed to what Google does in their plugin). The sample's a fully working GWT application that allows you to get a first impression of what developing with GWT looks like. h1. Cross compile to Javascript GWT is about programming in Java and getting javascript for the browser. GWT achieves this with a cross-compiler that creates the javascript for you. In order to get the project up and running you now need to cross compile the sample's client java code to javascript. Our project has the *GWT nature* and therefore offers the Google compiler in the context menu. http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-16-627... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-16... h1. Deploy to JBoss We are now ready to deploy our application. We strictly use the standard Eclipse *WTP* infrastructure in our setup, So you may deploy your GWT application in the same manner you usually deploy and run classic web applications with Eclipse WTP. You have to add the application to a server that's registered in the WTP *servers view*. We deploy our application to our JBoss application server by selecting it in the and choosing *Add and Remove...* http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-16-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-16... You can now add the GWT application to your server. WTP will make sure that it gets deployed and the deployed artifacts are in sync with your workspace (even when you change code, resources, configurations, etc.) http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-16-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-16... h1. Run your application and launch your browser You may now run your application. We completely comply to the views and steps Eclipse WTP offers to web developers. So there's no custom way to start a server in our setup. We select our JBoss instance in the *Servers view* and *start* it. http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-16-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-16... You can now point your browser to the address and port that your JBoss server's bound to. http://community.jboss.org/servlet/JiveServlet/showImage/6271/Picture+2.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6271/Picture... h2. Speed up my development cycle! The approach we've choosen so far uses an extra cross compile step to deploy the application after each change. That's very reliable but it gets tedious at development time. Google delivers a so called hosted/development mode. Its major benefit is that you dont need to cross compile on each change but you can change and test on the fly. This magic is achieved with a browser plugin and a google runtime that interprets your java code at runtime. Changing, testing, changing, testing etc. gets much faster and pleasant, the cross-compilation step's not needed any more. h2. Launch GWT Codeserver If you launch your application as Google Web Application, you'll be able to code and test on the fly. The GWT browser plugin will communicate with the GWT code server and execute your changes on the fly. http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-16-646... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-16... You need to tell the browser plugin where your code server may be reached. You do that by using an *additional url parameter*. Your browser URL now reads as follows: > http://localhost:8080/gwt-test/?gwt.codesvr=127.0.0.1:9997 http://localhost:8080/gwt-test/?gwt.codesvr=127.0.0.1:9997 Point your browser to this URL and you'll get the same page as before, nothing spectacular so far. Now get back to your client code and change the button label, to see if changes are picked on the fly now. http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-16-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-16... Do not cross-compile, get back to your browser and reload. What you see reflects the changes in your code. You don't need to cross compile to develop your app! http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-16-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-16... To be picky on the issue you could now go to the launch configuration and disable the jetty google usually uses to serve your GWT application: http://community.jboss.org/servlet/JiveServlet/showImage/6413/disable-bui... http://community.jboss.org/servlet/JiveServlet/downloadImage/6413/disable... -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-15794] Create a new document in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

15 years, 7 months

1
0
0 / 0

[JBoss Tools] - Could not detect registered XULRunner to use: Please help

by Raj Kumar

Raj Kumar [http://community.jboss.org/people/indokely] created the discussion "Could not detect registered XULRunner to use: Please help" To view the discussion, visit: http://community.jboss.org/message/560508#560508 -------------------------------------------------------------- org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use] at org.eclipse.swt.SWT.error(SWT.java:3910) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:473) at org.eclipse.swt.browser.Browser.<init>(Browser.java:119) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:88) at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:153) at org.jboss.tools.vpe.editor.mozilla.XulRunnerPreview.<init>(XulRunnerPreview.java:22) at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.createPartControl(MozillaPreview.java:79) at org.jboss.tools.vpe.editor.VpeEditorPart.createPreviewBrowser(VpeEditorPart.java:907) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:219) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:425) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271) at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1417) at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:942) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1384) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/560508#560508] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 7 months

4
4
0 / 0

Re: [jboss-user] [JBoss Tools] - JBoss Tools 3.2.0.M2 Delta Cloud, GWT, Teiid and more

by Alexey Kazakov

Alexey Kazakov [http://community.jboss.org/people/akazakov] commented on "JBoss Tools 3.2.0.M2 Delta Cloud, GWT, Teiid and more" To view all comments on this blog post, visit: http://community.jboss.org/community/jbosstools/blog/2010/09/09/jboss-too... -------------------------------------------------- Max, the link to https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pro... What's New and Noteworthy actually is broken and links to JIRA. I guess it should be http://docs.jboss.org/tools/whatsnew/index.html http://docs.jboss.org/tools/whatsnew/index.html --------------------------------------------------

15 years, 7 months

1
0
0 / 0

[JBoss Tools] - Create GWT Projects with JBoss Tools and Eclipse WTP

by Andre Dietisheim

Andre Dietisheim [http://community.jboss.org/people/adietish] modified the document: "Create GWT Projects with JBoss Tools and Eclipse WTP" To view the document, visit: http://community.jboss.org/docs/DOC-15794 -------------------------------------------------------------- h1. Use Eclipse WTP, get there with the standard If you want to create GWT applications you unfortunately cannot do it the WTP way and create a so called dynamic web project. The Google plugins implement their own set of views, wizards, launchers and mostly duplicate what's already present and defacto standard in WTP. The consequence is that you'd have to deal with workarounds if you want to get functionalities (run/deploy on JBoss etc.) Google does not offer. We therefore developed an experimental integration plugin for GWT that allows you to create GWT projects in the way most Eclipse users are used to: by creating Dynamic Web Projects. h1. Preface Eclipse offers nice tools to create web applications. The base framework's what we call the Eclipse Web Tools Platform (WTP). Eclipse WTP delivers a standard for most aspects involved when you create web applications. The google web toolkit, GWT, is a nice framework to develop web applications. Google delivers a plugin for Eclipse and developing with GWT is a very pleasant experience. The GWT plugin uses an embedded jetty to run the application that you develop. Google unfortunately did not base its work on Eclipse WTP and does not comply to the Eclipse project structure for web application. So if you want to use JBoss instead of jetty, the approach to take is not as handy and intuitive as it could be. Furthermore there's no way to use and integrate into plugins that other solution providers offer. You mostly have to proceed by workarounds to get what Google does not offer. We developed a set of (experimental) plugins that create GWT projects by extending Eclipse WTP. Our plugins implement well known usage patterns and integrate well with all Eclipse components that use the common standard for web projects. The most obvious benefit is that deploying to JEE application servers (and JBoss partcullarly) is as easy as it is with any other web project. h1. Solution Install and use the JBoss GWT Integration. You'll then be able to create GWT projects the WTP way and fully enjoy it's full-blow features and standardized usage patterns. This How-To shows you all the steps to install the plugins and how to create a dynamic web project that's GWT enabled. h2. Install JBoss GWT Integration Add the Google Eclipse Plugins update site: > http://dl.google.com/eclipse/plugin/3.6/ http://dl.google.com/eclipse/plugin/3.6/ Add the JBoss Tools update site: > http://download.jboss.org/jbosstools/updates/nightly/jbosstools-3.2.0.M2/ http://download.jboss.org/jbosstools/updates/nightly/jbosstools-3.2.0.M2/ And Install the JBoss GWT Integration http://community.jboss.org/servlet/JiveServlet/showImage/6254/Picture+4.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6254/Picture... h2. Create a Dynamic Web Application Project Make sure you have a JEE server (JBoss application server for instance) in your Eclipse environment. If not, download and declare it to your Eclipse IDE: http://community.jboss.org/servlet/JiveServlet/showImage/6260/Picture+12.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6260/Picture... http://community.jboss.org/servlet/JiveServlet/showImage/6259/Picture+11.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6259/Picture... You're now ready to create a *Dynamic Web Project*. http://community.jboss.org/servlet/JiveServlet/showImage/6256/Picture+5.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6256/Picture... The wizard picks your server (runtime) and allows you to configure the various characteristic of your web project. The *configuration* group allows you to pick the different facets of your project. We provide a *Google Web Toolkit* facet that will configure the GWT related characteristics. Hit *Modify...* http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-13-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-13... and select the *Google Web Toolkit* facet. http://community.jboss.org/servlet/JiveServlet/showImage/6262/Picture+14.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6262/Picture... A few wizard steps further, you may choose to get some GWT *sample code*. http://community.jboss.org/servlet/JiveServlet/showImage/6411/generate-sa... http://community.jboss.org/servlet/JiveServlet/downloadImage/6411/generat... You get the Hello World sample that you get when you use the Google Wizard. We just put it to the *WebContent* folder you configured in your Dynamic Web Project wizard (WTP default opposed to what Google does in their plugin). The sample's a fully working GWT application that allows you to get a first impression of what developing with GWT looks like. h1. Cross compile to Javascript GWT is about programming in Java and getting javascript for the browser. GWT achieves this with a cross-compiler that creates the javascript for you. In order to get the project up and running you now need to cross compile the sample's client java code to javascript. Our project has the *GWT nature* and therefore offers the Google compiler in the context menu. http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-13-627... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-13... h1. Deploy to JBoss We are now ready to deploy our application. We strictly use the standard Eclipse *WTP* infrastructure in our setup, So you may deploy your GWT application in the same manner you usually deploy and run classic web applications with Eclipse WTP. You have to add the application to a server that's registered in the WTP *servers view*. We deploy our application to our JBoss application server by selecting it in the and choosing *Add and Remove...* http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-13-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-13... You can now add the GWT application to your server. WTP will make sure that it gets deployed and the deployed artifacts are in sync with your workspace (even when you change code, resources, configurations, etc.) http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-13-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-13... h1. Run your application and launch your browser You may now run your application. We completely comply to the views and steps Eclipse WTP offers to web developers. So there's no custom way to start a server in our setup. We select our JBoss instance in the *Servers view* and *start* it. http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-13-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-13... You can now point your browser to the address and port that your JBoss server's bound to. http://community.jboss.org/servlet/JiveServlet/showImage/6271/Picture+2.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6271/Picture... h2. Speed up my development cycle! The approach we've choosen so far uses an extra cross compile step to deploy the application after each change. That's very reliable but it gets tedious at development time. Google delivers a so called hosted/development mode. Its major benefit is that you dont need to cross compile on each change but you can change and test on the fly. This magic is achieved with a browser plugin and a google runtime that interprets your java code at runtime. Changing, testing, changing, testing etc. gets much faster and pleasant, the cross-compilation step's not needed any more. h2. Launch GWT Codeserver If you launch your application as Google Web Application, you'll be able to code and test on the fly. The GWT browser plugin will communicate with the GWT code server and execute your changes on the fly. You need to declare though, where your code server's may be reached. You do that by using an *additional url parameter*. Your URL now reads as follows: > http://localhost:8080/gwt-test/?gwt.codesvr=127.0.0.1:9997 http://localhost:8080/gwt-test/?gwt.codesvr=127.0.0.1:9997 Change the button in your GWT java client code, to see if changes are picked on the fly now. http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-13-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-13... Do not cross-compile, get back to your browser and reload (without cross-compiling again). What you see reflects the changes in the code. http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-13-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-13... To be picky on the issue you could now go to the launch configuration and disable the jetty google usually uses to serve your GWT application: http://community.jboss.org/servlet/JiveServlet/showImage/6413/disable-bui... http://community.jboss.org/servlet/JiveServlet/downloadImage/6413/disable... -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-15794] Create a new document in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

15 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user September 2010