JiBX

Programmatically calling CodeGen.generate (from a maven plugin) causes a NullPointerException

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Not A Bug
  • Affects Version/s: JiBX 1.2.1
  • Fix Version/s: None
  • Component/s: CodeGen
  • Labels:
    None
  • Environment:
  • Number of attachments :
    0

Description

Was attempting to write a maven plugin to generate java code and bindings from a schema during the maven build life cycle. Here is what the plugin is doing.

CodeGenCommandLine cmdLine = new CodeGenCommandLine();
cmdLine.processArgs(args);
CodeGen codegen = new CodeGen(cmdLine);
codegen.generate(true);

I am getting a null pointer exception on the generate call. Here is the stack trace.

java.lang.NullPointerException
at org.jibx.schema.codegen.CodeGen.generate(CodeGen.java:1388)

Looking at the source it appears that m_packageDirectory is null as its not being set. In the source it only appears that m_packageDirectory is getting set in the load method which is private and only called by the main method (which is why it works from the command line and not from a codeGen.generate).

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ken Preudhomme added a comment -

I was able to statically call the main method from the CodeGen class to resolve the issue. If that is the intended use of the code generator perhaps the generate method should be moved to private or protected access. Or clearly state as such in the API documentation?

Show
Ken Preudhomme added a comment - I was able to statically call the main method from the CodeGen class to resolve the issue. If that is the intended use of the code generator perhaps the generate method should be moved to private or protected access. Or clearly state as such in the API documentation?
Hide
Permalink
Dennis Sosnoski added a comment -

The usage of this class is obscure and the interface continues to evolve over time. You're definitely best off using the main() method to use the class, if at all possible, since otherwise your code may need to change with future releases.

For instance, I've just restructured the way this works to be usable with Axis2 WSDL2Java code generation, in the process making several methods public and changing the way some of these are used. Unfortunately the methods do need to be public so that they can be used for this type of purpose, but they are intended for JiBX developer use rather than as part of the official JiBX API. I've added comments to this effect in the class JavaDocs.

Show
Dennis Sosnoski added a comment - The usage of this class is obscure and the interface continues to evolve over time. You're definitely best off using the main() method to use the class, if at all possible, since otherwise your code may need to change with future releases. For instance, I've just restructured the way this works to be usable with Axis2 WSDL2Java code generation, in the process making several methods public and changing the way some of these are used. Unfortunately the methods do need to be public so that they can be used for this type of purpose, but they are intended for JiBX developer use rather than as part of the official JiBX API. I've added comments to this effect in the class JavaDocs.

People

  • Assignee:
    Dennis Sosnoski
    Reporter:
    Ken Preudhomme
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: