I'm trying to generate a Java Bean Skelleton from a WSDL (actually this will happen with Client generation as well).
So here are the Steps I did:
Rightclick on .wsdl -> WebServices -> Generate Java Bean Skelleton
Select Tomcat 7 and Axis 2
Click next (In this field the Parameters fields are Empty)
Click next, you will receive the following Error - Exception occurred during code generation for the WSDL : null
This Error seems to be thrown if you check out Projects with subversive (actually in the case of our project we see this correlation).
What could be done to fix this issue?
This issue is also an open bug since 2008, Axis2 BugTracker
The only Workarround I found for this, goes as follows:
Create a new DynamicWebProject
Create a new WSDL (You can copy you old one or what ever you like)
Create a new Java Bean Skelleton (or Client)
Now the WSDL2Java will work again for some time till it will be damaged again. You will be able to fix this by regenerate the Java Bean Skelleton. You won't need to create a new Project every time.
Edit:
The actual solution to this Problem was found now. I changed my SVN-Plugin from Subversive to Subclips. Now everything works out fine.
Related
I'm dealing with this issue:
I generated the service stubs using Axis 1.4, with 1.4-redhat-1 as lib to the project.
I read a lot about this error and people said the issue was from the axis stubs generation itself, and the only solution was to regenerate stubs and recompile the projects that consumes them. The thing is: I made a test class in the and called the operation on eclipse using the "old" class without the new element and it works!
After that I copy/paste the test class to the main project that consumes the stubs, and it also worked.
But when I deploy the artifact to jBoss AS 5.1, I got the same "Invalid element" exception, so I'm guessing there's something "wrong" with the jBoss configs.
Does anyone have a tip where to start searching for the fix ? Thanks in advance.
Every time I make a change to some HTML I am editing, this error
comes up:
Errors occurred during the build.
Errors running builder 'Faceted Project Validation Builder' on project 'CateredToYou'.
Could not initialize class oracle.eclipse.tools.weblogic.server.WebLogicServerRuntimeComponentType
I'd like to figure out why the error comes up despite the fact that I am not doing any J2EE development at the moment
OR
how can I shut off whatever is trying to execute this command.
This sounds like a builder that is configured on the project is having problems.
Open the Properties for the project and look in Builders. You will see a list of the builders configured for the project which should include 'Faceted Project Validation Builder'. You can disable it by clearing the check box or remove it entirely.
I accidentally deleted the Java 1.6 needed for Eclipse when I allowed the Java auto update.
As it turns out, the jdk1.6 was not deleted from the system but it was not in the "Installed JRE's" list
I added the JRE, but was still getting the error. I added the jdk to the config and the error went away.
I'm trying to make a hibernate connection to create some reports, but every time I press Test it appears an error window that says org/primefaces/model/UploadedFile, only that.
My classpath already has a jar of my project and the only place where I have the library from the error is inside an entity on the project.
If switch to another's project jar the connection is successful.
I'm using iReport 5.0.4 and Spring 2.9.1.
I'll appreciate any idea of what could be wrong, thanks in advance.
I couldn't figure out what was the problem, so I commented all references to the library and generated the jar that way.
I did it only because there's no related data to the things I commented.
When I export my JSF 1.2 project as WAR file, it is not being created properly in Eclipse Indigo. Namely, when I import it again and run it, then it ends up in the "FacesContext not found" error. How is this caused and how can I solve it?
I checked again, when I import it again and run the url pattern is missing /faces/ . when i append it manually it is coming fine. is there any way in which the url pattern will come same in the imported file also?
You're relying too much on the IDE doing all the necessary magic for you. Your initial project had the JSF project facet set and you were running the project by Run on server using the builtin browser instead of just starting the server and navigate to it yourself in the external browser.
The JSF project facet is an Eclipse specific feature which is completely unrelated to the JSF/Servlet spec. This information is nowhere stored in the WAR. When you import it again, it'll become a default dynamic web project without any specific project facets set. You need to rightclick the project, go to Project Facets section and manually add the JSF project facet. This way the IDE becomes aware that the project is a JSF project and will do the necessary magic such as automagically inlining the FacesServlet mapping in the target URL during Run As.
I want to use Spring ROO 1.2.1 + GWT 2.6.1 in Springsource Tool Suite 2.9.1 in Ubuntu 12.04.
Following guides like the video in http://www.bytespring.com/blog/spring-roo-integration-gwt, I can create with roo a new project via the "expense" script, then run it with mvn gwt:run.
Ok, than I want to manage it in STS and now the problem starts.
It seems to be problem about m2e.
In pom.xml the tag for artifact with ID "exec-maven-plugin" have this error:
Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:exec-maven-plugin:1.2:exec (execution: default, phase: process-classes)
I tried to follow the solution suggested in How to solve "Plugin execution not covered by lifecycle configuration" for Spring Data Maven Builds.
Surrounded "plugins" tag with the "pluginManagement" tag. Now the error no longer appears.
Then I run the application, "Run as -> Web Application"... HTML Page Selection: ApplicationScaffold.html.
The web page appears, but with a window with this error:
Error: One or more exceptions caught, see full set in UmbrellaException#getCause".
The STS console says
"java.lang.RuntimeException: The RequestFactory ValidationTool must be run for the org.springsource.roo.extrack.client.managed.request.ApplicationRequestFactory RequestFactory type".
To solve this problem, I followed the instructions in http://code.google.com/p/google-web-toolkit/wiki/RequestFactoryInterfaceValidation.
1)In Project Properties->Java Compiler->Annotation Properties I enabled project specific settings, annotation processing and processing in editor, gen.source directory: .apt_generated; verbose false.
2) In Factory Path, enabled project specific settings, and added the external requestfactory-apt.jar located in
/home/toni/springsource/sts-2.9.1.RELEASE/plugins/com.google.gwt.eclipse.sdkbundle_2.4.0.v201205091048-rel-r37/gwt-2.4.0
(right??)
(I do not understand if "Validation Tool" and "Maven build" sections are important for me)
Now I tried to re-run (after a rebuild of project) and the same error persists.
Someone solved this problem?? How? Please explain step-by-step because I am not an expert, It's my first approach with spring and gwt...
This looks like the same problem I ran into a short while back, which (after considerable digging) appeared to be down to a bug in AJDT (Eclipse's AspectJ compiler) which means that it currently cannot handle Java 6 annotations (used heavily by Roo).
A comment on a connected GWT bug report describes the following workaround:
move AspectJ builder to be in front (on top) of Java builder in project properties, Builder page.
clean and build the project.
copy and save generated Java/class files in .apt_generated directory to somewhere else.
move Java builder back in front of AspectJ builder.
clean and rebuild the project
copy the class file from 3 above to your project's classpath.
Alternatively, you can build your project outside of Eclipse - the non-IDE AspectJ compiler, ajc, does not suffer from this problem.