[JBoss Tools] - JBoss 7 AS RESTEasy issue with generic type arguments
by Jan Tim
Jan Tim [http://community.jboss.org/people/jantimw] created the discussion
"JBoss 7 AS RESTEasy issue with generic type arguments"
To view the discussion, visit: http://community.jboss.org/message/617055#617055
--------------------------------------------------------------
Before I recently migrated from JBoss 6 to 7, I was using JAX-RS for my RESTful services and everything was went fine. Now that I am working with JBoss 7 I noticed that I can use the build in RESTEasy for my purposes. But unfortunately there seems to be an issue with generic types when used in annotated POST or PUT methods.
To make things clear, I created a small and easy example of what was working for me before but no longer does:
@Path("/g")
public abstract class GenericResource<T extends Person> {
@POST
@Path("/add")
@Consumes("application/json")
@Produces("application/json")
public String doPost(T person) { // The use of a generic type as argument causes an error
return "success";
}
@GET
@Produces("application/json")
public T doGet() {
@SuppressWarnings("unchecked")
T p = (T) new PersonImpl("TestPerson");
return p;
}
}
As you can see, I just build an abstract class with a generic type T and annotated two methods, one with "POST" and one with "GET". This example worked fine with JBoss 6 and JAX-RS, but now I get the following error on sending any request (get or post) through RESTEeasy to this class:
Allocate exception for servlet javax.ws.rs.core.Application: java.lang.RuntimeException: Unable to determine value of type parameter T
at org.jboss.resteasy.util.Types.getActualValueOfTypeVariable(Types.java:319) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.MethodInjectorImpl.<init>(MethodInjectorImpl.java:65) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.InjectorFactoryImpl.createMethodInjector(InjectorFactoryImpl.java:55) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.ResourceMethod.<init>(ResourceMethod.java:71) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.ResourceMethodRegistry.processMethod(ResourceMethodRegistry.java:178) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:123) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:106) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:83) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.core.ResourceMethodRegistry.addPerRequestResource(ResourceMethodRegistry.java:72) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:367) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:225) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:67) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36) [resteasy-jaxrs-2.2.1.GA.jar:]
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:952) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:188) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.0.Final.jar:7.0.0.Final]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.0.Final.jar:7.0.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.CR4.jar:7.0.0.Final]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
If I remove the POST-method, at least the GET-request ist working correctly. Although changing the argument to a type that is not generic fixes the error but that is no long term solution for my problem. Am I doing something wrong or is it a bug that is already known?
Best Regards
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617055#617055]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 8 months
[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 Google Plugin for Eclipse
Add the Google update site
> * JBoss Tools 3.2.x (based on Helios): http://dl.google.com/eclipse/plugin/3.6 http://dl.google.com/eclipse/plugin/3.6
>
> * JBoss Tools 3.3.x (based on Indigo): http://dl.google.com/eclipse/plugin/3.7 http://dl.google.com/eclipse/plugin/3.7
>
And Install the Google Plugin for Eclipse 3.6 and the GWT SDK.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-25-161... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-25...
h2. Install JBoss GWT Integration
Add the JBoss Tools update site:
> * JBoss Tools 3.2.x: http://download.jboss.org/jbosstools/updates/nightly/3.2_stable_branch/ http://download.jboss.org/jbosstools/updates/nightly/3.2_stable_branch/
>
> * JBoss Tools 3.3.x: http://download.jboss.org/jbosstools/updates/nightly/trunk/ http://download.jboss.org/jbosstools/updates/nightly/trunk/
>
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-25-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-25...
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-25-627... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-25...
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-25-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-25...
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-25-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-25...
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-25-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-25...
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-25-646... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-25...
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-25-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-25...
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-25-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-25...
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...]
14 years, 8 months
[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 Google Plugin for Eclipse
Add the Google update site
> JBoss Tools 3.2.x (based on Helios): http://dl.google.com/eclipse/plugin/3.6 http://dl.google.com/eclipse/plugin/3.6
> JBoss Tools 3.3.x (based on Indigo): http://dl.google.com/eclipse/plugin/3.7 http://dl.google.com/eclipse/plugin/3.7
And Install the Google Plugin for Eclipse 3.6 and the GWT SDK.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-23-161... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-23...
h2. Install JBoss GWT Integration
Add the JBoss Tools update site:
> JBoss Tools 3.2.x: http://download.jboss.org/jbosstools/updates/nightly/3.2_stable_branch/ http://download.jboss.org/jbosstools/updates/nightly/3.2_stable_branch/
> JBoss Tools 3.3.x: http://download.jboss.org/jbosstools/updates/nightly/trunk/ http://download.jboss.org/jbosstools/updates/nightly/trunk/
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-23-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-23...
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-23-627... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-23...
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-23-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-23...
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-23-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-23...
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-23-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-23...
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-23-646... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-23...
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-23-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-23...
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-23-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-23...
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...]
14 years, 8 months
Re: [jboss-user] [jBPM] - couldn't parse process definition
by Marco Rietveld
Marco Rietveld [http://community.jboss.org/people/marco.rietveld] commented on the document
"couldn't parse process definition"
To view all comments on this document, visit: http://community.jboss.org/docs/DOC-17031#comment-7122
--------------------------------------------------
Cristóvão,
Michael's right: this is the document section. *Would you mind deleting this article and, if necessary, posting your question to the forum?*
That being said, the problem you're having is probably one of the following:
- you might have to use /'s instead of \'s.
- It looks like youŕe giving the absolute path, but it you aren't you need to.
In short, while the error looks complex, it's simply saying that the File can't be found. Try doing a check on the file first (.exists(), maybe also opening it and checking that the inputStream returns something..?), and then feeding it to the (jpdl) parser.
--------------------------------------------------
14 years, 8 months
