Skip to main content

BPEL Validation Errors in NetBeans 5.5.1

Image
By
I‘ve recently updated my production NetBeans 5.5 environment to NetBeans 5.5.1 and have been having some issues with BPEL modules.

If I create a BPEL module in NB 5.5, everything works as expected, however if I try to build the same codebase on NB 5.5.1, I get the following error.

Interestingly enough, I get the same problem with NB 6 M10

<target name="pre-dist"> 
09-Jul-2007 13:08:44  
org.netbeans.modules.bpel.project.anttasks.IDEValidateBPELProject 
loadAndValidateExistingBusinessProcess 
SEVERE: Validation has errors on /home/david/NetBeansProjects/EchoBPEL/src/EchoProcess.bpel 
Error Message -  
org.netbeans.modules.xml.wsdl.validator.spi.ValidatorSchemaFactory.getSchemaSource() 
Ljavax/xml/transform/Source; 
09-Jul-2007 13:08:44  
org.netbeans.modules.bpel.project.anttasks.IDEValidateBPELProject  
loadAndValidateExistingBusinessProcess 
SEVERE:  
org.netbeans.modules.xml.wsdl.validator.spi.ValidatorSchemaFactory.getSchemaSource() 
Ljavax/xml/transform/Source; 
/home/david/NetBeansProjects/EchoCompositeApp/nbproject/build-impl.xml:104:  
The following error occurred while executing this line: 
/home/david/NetBeansProjects/EchoBPEL/nbproject/build-impl.xml:155:  
java.lang.AbstractMethodError:  
org.netbeans.modules.xml.wsdl.validator.spi.ValidatorSchemaFactory. 
getSchemaSource()Ljavax/xml/transform/Source; BUILD FAILED (total time: 0 seconds)

Does anyone else have this problem? The workaround I have found at the moment is to comment out the BPEL validation code in the ant script (build-impl.xml line 155) as follows:

<target name="pre-dist"> 
        <!-- Empty placeholder for easier customization. -->
  
        <!-- You can override this target in the ../build.xml file. -->
        <mkdir dir="${build.dir}"/> 
        <!-- run the validation task here. -->
<!– 
        <BpelProjectValidate buildDirectory=”${basedir}/${build.dir}” 
        sourceDirectory=”${basedir}/${src.dir}” 
        projectClassPath=”${javac.classpath}” 
        buildDependentProjectDir=”${basedir}/${build.dir}/dependentProjectFiles” 
        classpathRef=”ant.task.classpath.validation”  
        allowBuildWithError=”${allow.build.with.error}”/> 
–>
Labels:

Comments

Post a Comment

Popular posts from this blog

Creating a Joke Application in React

By
Introduction I've recently started learning React. I've been a backend developer for a long time, but have started to love doing client side work. As they say, the best way to learn is to practise. So here is a simple joke application that I've written in React. The source code for the application can be found on GitHub at: https://github.com/doobrie/react-joke Creating the project Whilst practising, I've quite often created projects from scratch, but this is quite tedious as the same steps need to be taken for each project. I needed to create the project structure, configure Babel, write some control scripts etc. Instead of doing that this time, I've used the create-react-app tool to scaffold the basics of an application. npx create-react-app This sets up everything that you need to get started with a React app. Coding As this is a simple project, I've created one react component, function app() . I've created this as a functional c...
Post a Comment
Read more

Changing Default Search Provider in Firefox on Linux Mint

By
On Linux Mint, the default version of Firefox is installed and configured to allow the following search engines to be queried directly from the address bar: Yahoo! Startpage DuckDuckGo Wikipedia Mint defines these as the default available set of search engines based upon 3 criteria (funding to Linux Mint, privacy support and whether the search engine is non-commercial). Other search engines such as Google, Bing or Twitter, etc. can easily be added into the default version of Firefox however. To add a different search provider, browse to Search Engines At the bottom of the page, click on the icon of the requested search engine, then click on the ... button in the URL bar and select the Add Search Engine option. You then have the option to change the default search engine within Firefox preferences to your new choice.
Post a Comment
Read more

The new Eclipse logo

By Anonymous
In a blog post today, Ian Skerrett has announced the new logo for Eclipse. Last fall we [The Eclipse Foundation] started a process to  update the Eclipse logo . The existing logo had not been change since Eclipse was launched and it was showing its age. I am happy to announce we have finished the process and am pleased to introduce the updated Eclipse logo. The new logo has a fresh modern look to it, which I think is a good improvement and will stand Eclipse in good stead for the future. The new logo will be included with the next Eclipse release train, Luna, and gradually rolled out across the Eclipse site and projects. What do you think?  Do you like the new logo?  Add your comments below.
Post a Comment
Read more