• Type: Bug Report
• Resolution: Won't Fix
• Priority: L3 - Default
• Fix Version/s: 7.4.x
• Affects Version/s: 7.4.0-alpha2
• Component/s: cockpit, dmn-ui
• Labels:

  None

This is the controller panel for Smart Panels app

1. 

   camunda_cockpit_dmn.png

   122 kB

   12/Nov/15 11:38 PM

2. DT_neu_40000.dmn11.xml

   58 kB

   12/Nov/15 11:39 PM

3. 

   screenshot-2.png

   85 kB

   12/Nov/15 11:47 PM

[CAM-4963] Non ASCII characters not displayed correctly

Frank Langelage created issue - 12/Nov/15 11:42 PM

Frank Langelage made changes - 12/Nov/15 11:47 PM

Attachment

New: screenshot-2.png [ 21062 ]

Collapse comment: Frank Langelage added a comment - 12/Nov/15 11:49 PM

Frank Langelage added a comment - 12/Nov/15 11:49 PM

Using "Navigate to deployment" the umlauts in the column headers are displayed correctly.

Expand comment: Frank Langelage added a comment - 12/Nov/15 11:49 PM

Frank Langelage added a comment - 12/Nov/15 11:49 PM Using "Navigate to deployment" the umlauts in the column headers are displayed correctly.

Robert Gimbel made changes - 13/Nov/15 12:05 PM

Fix Version/s

New: 7.4.0 [ 13505 ]

Robert Gimbel made changes - 13/Nov/15 12:06 PM

Assignee

New: Sebastian Menski [ sebastian.menski ]

Collapse comment: Sebastian Menski added a comment - 13/Nov/15 1:02 PM

Sebastian Menski added a comment - 13/Nov/15 1:02 PM

Hi langfr,

how did you create the DMN table? Did you manually edited it or used the modeler at http://camunda.org/dmn/demo-stage?

Cheers,
Sebastian

Expand comment: Sebastian Menski added a comment - 13/Nov/15 1:02 PM

Sebastian Menski added a comment - 13/Nov/15 1:02 PM Hi langfr , how did you create the DMN table? Did you manually edited it or used the modeler at http://camunda.org/dmn/demo-stage? Cheers, Sebastian

Thorben Lindhauer made changes - 13/Nov/15 1:02 PM

Comment

[ Hi Frank, How did you deploy the model? As part of a process application deployment, via REST or Java API? If via Java API, which code did you use? Cheers, Thorben ]

Collapse comment: Frank Langelage added a comment - 13/Nov/15 2:06 PM

Frank Langelage added a comment - 13/Nov/15 2:06 PM

The XML file attached was created by another application.
The file is read into an byte[] fileContent and then deployed using the Java-API:

        DeploymentBuilder deploymentBuilder = this.repositoryService.createDeployment();
        deploymentBuilder.enableDuplicateFiltering( true );
        deploymentBuilder.addInputStream( fileName, new ByteArrayInputStream( fileContent ) );
        deploymentBuilder.name( fileName );
        Deployment deployment = deploymentBuilder.deploy();

But as the umlauts are there on different views in camunda cockpit (lower part of screenshot 1 and screenshot 2) it cannot be a problem of deploying.

Expand comment: Frank Langelage added a comment - 13/Nov/15 2:06 PM

Frank Langelage added a comment - 13/Nov/15 2:06 PM The XML file attached was created by another application. The file is read into an byte[] fileContent and then deployed using the Java-API: DeploymentBuilder deploymentBuilder = this .repositoryService.createDeployment(); deploymentBuilder.enableDuplicateFiltering( true ); deploymentBuilder.addInputStream( fileName, new ByteArrayInputStream( fileContent ) ); deploymentBuilder.name( fileName ); Deployment deployment = deploymentBuilder.deploy(); But as the umlauts are there on different views in camunda cockpit (lower part of screenshot 1 and screenshot 2) it cannot be a problem of deploying.

Collapse comment: Sebastian Menski added a comment - 13/Nov/15 2:08 PM

Sebastian Menski added a comment - 13/Nov/15 2:08 PM

Hi sebastian.stamm and roman.smirnov,

does anybody know a reason why we should get the DMN XML encapsulated in a JSON object in the history view? If not I would propose a binary endpoint for the decision definition xml like the binary data endpoint for deployment resources. This way the encoding would be preserved.

Cheers,
Sebastian

Expand comment: Sebastian Menski added a comment - 13/Nov/15 2:08 PM

Sebastian Menski added a comment - 13/Nov/15 2:08 PM Hi sebastian.stamm and roman.smirnov , does anybody know a reason why we should get the DMN XML encapsulated in a JSON object in the history view? If not I would propose a binary endpoint for the decision definition xml like the binary data endpoint for deployment resources. This way the encoding would be preserved. Cheers, Sebastian

Collapse comment: Sebastian Stamm added a comment - 13/Nov/15 2:19 PM

Sebastian Stamm added a comment - 13/Nov/15 2:19 PM

I do not see a reason why we would need it wrapped in JSON. When we introduce a binary data endpoint to retrieve the XML, we should do this for the process definition, too (I assume we have a similar problem there).

Expand comment: Sebastian Stamm added a comment - 13/Nov/15 2:19 PM

Sebastian Stamm added a comment - 13/Nov/15 2:19 PM I do not see a reason why we would need it wrapped in JSON. When we introduce a binary data endpoint to retrieve the XML, we should do this for the process definition, too (I assume we have a similar problem there).

Load more newer events