Skip to Main Content
Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Merative External Privacy Statement: https://www.merative.com/privacy

Status Future consideration
Created by Application Delivery
Created on Mar 17, 2022

Upgrade Axis2 to 1.8.0 to support Java 8

Currently, Curam Social Program Management 8.0 uses Axis2 version 1.6.2. This causes runtime exceptions when a Curam workflow calls a server Java class compiled in Java 8 or later:


Workflow:RUN_ID_INVALID_PROCESS_DEFINITION: The workflow process definition is invalid against the schema. The schema error is "Error looking for paramter names in bytecode: unexpected bytes in file"

nested exception is:

java.lang.IllegalStateException: Error looking for paramter names in bytecode: unexpected bytes in file

at org.apache.axis2.description.java2wsdl.bytecode.ClassReader.readCpool(ClassReader.java:354)

at org.apache.axis2.description.java2wsdl.bytecode.ParamReader.<init>(ParamReader.java:78)

at org.apache.axis2.description.java2wsdl.bytecode.ParamReader.<init>(ParamReader.java:57)

at curam.util.internal.workflow.impl.BPOMethodMappingUtil.getFormalParameterName(BPOMethodMappingUtil.java:550)


Curam needs to use Axis2 version 1.8.0 in CuramSDEJ, which supports Java 8 and later. See this Apache Axis commit which fixes this issue: https://github.com/apache/axis-axis2-java-core/commit/10e0963bdbbf1a6cdf3d059ec15945495175fb0d

Customer Name ReturnToWorkSA
Persona Based Summary

As a developer, I want to be able to call Java 8 code from Curam workflows.

Market Segment General
Type of Request Idea
Market Opportunity

This idea will allow current versions of Java to be used in Curam development.

CURAM:Workarounds + Proposed Solution

I have had to patch CuramSDEJ/lib/axis2/axis2-kernel-1.6.2.jar with an updated ClassReader class from Axis2 1.8.0 to handle Java 8.

  • Attach files
  • Guest
    Reply
    |
    Apr 7, 2022

    Hi Andrew,

    We have reviewed your enhancement suggestion.

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:

    You are requesting that we upgrade to the latest version of Axis 2.

    The theme is aligned with our current strategy for our product, and we have accepted your suggestion as a consideration for a future release.

    Not all items under consideration will make it into a release. As plans are confirmed, you will be notified when a specific release includes this enhancement.

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    Regards,
    Sheryl Brenton, SPM Product Management Team

  • Guest
    Reply
    |
    Mar 22, 2022

    Hi Andrew,

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    We will review the information you have provided and get back to you within 30 days. If additional details are required to complete our evaluation, we will send you a request for more information.

    Thank you,
    Sheryl Brenton, SPM Product Management Team