Petals Studio

Sometimes, the JBI builder cannot resolve line numbers

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1.0
  • Fix Version/s: 1.1.1
  • Component/s: Petals Tools
  • Security Level: Public
  • Description:
    Hide

    Sometimes, the JBI builder cannot resolve line numbers.
    It also applies to the BPEL builder.

    There is a stack trace if we launch the studio in debug (or from a console).

    java.lang.NullPointerException
	at com.ebmwebsourcing.petals.common.builder.JbiXmlBuilder.resolveLineNumbers(JbiXmlBuilder.java:214)
	at com.ebmwebsourcing.petals.common.builder.JbiXmlBuilder.validateAndMarkJbiXmlFile(JbiXmlBuilder.java:200)
	at com.ebmwebsourcing.petals.services.su.nature.SuBuilder.access$1(SuBuilder.java:1)
	at com.ebmwebsourcing.petals.services.su.nature.SuBuilder$SuResourceVisitor.visit(SuBuilder.java:178)
	at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:108)
	at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:60)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
	at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:70)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:106)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:90)
	at com.ebmwebsourcing.petals.services.su.nature.SuBuilder.fullBuild(SuBuilder.java:73)
	at com.ebmwebsourcing.petals.common.builder.JbiXmlBuilder.build(JbiXmlBuilder.java:68)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
	at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Show
    Sometimes, the JBI builder cannot resolve line numbers. It also applies to the BPEL builder. There is a stack trace if we launch the studio in debug (or from a console). 
    java.lang.NullPointerException
	at com.ebmwebsourcing.petals.common.builder.JbiXmlBuilder.resolveLineNumbers(JbiXmlBuilder.java:214)
	at com.ebmwebsourcing.petals.common.builder.JbiXmlBuilder.validateAndMarkJbiXmlFile(JbiXmlBuilder.java:200)
	at com.ebmwebsourcing.petals.services.su.nature.SuBuilder.access$1(SuBuilder.java:1)
	at com.ebmwebsourcing.petals.services.su.nature.SuBuilder$SuResourceVisitor.visit(SuBuilder.java:178)
	at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:108)
	at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:60)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
	at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:70)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:106)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:90)
	at com.ebmwebsourcing.petals.services.su.nature.SuBuilder.fullBuild(SuBuilder.java:73)
	at com.ebmwebsourcing.petals.common.builder.JbiXmlBuilder.build(JbiXmlBuilder.java:68)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
	at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
  • Environment:
    Windows XP.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Zurczak added a comment - Mon, 23 Aug 2010 - 11:24:08 +0200

The line resolver utility was copied from the SCA tooling to the Petals tooling (the use of a command seems to be not always safe).
This line resolver is now directly used in both the JBI and BPEL builders.
The marker updater (following a WSDL parsing) now always returns a OK status.

Show
Vincent Zurczak added a comment - Mon, 23 Aug 2010 - 11:24:08 +0200 The line resolver utility was copied from the SCA tooling to the Petals tooling (the use of a command seems to be not always safe). This line resolver is now directly used in both the JBI and BPEL builders. The marker updater (following a WSDL parsing) now always returns a OK status.

People

Dates

  • Created:
    Fri, 20 Aug 2010 - 17:02:18 +0200
    Updated:
    Mon, 23 Aug 2010 - 11:24:14 +0200
    Resolved:
    Mon, 23 Aug 2010 - 11:24:08 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.