JSS Does not update Paramater names in Outline and BLOCKS JSS

Changed Resolution from Open to Works as Designed

Changed Status from New to Closed

Changed Assigned User from - to @User_306070

---

The change is notified when the textbox loses the focus (i.e: hit tab button or select Description text field).

Changed Reproducibility from Sometimes to Always

Changed Resolution from Works as Designed to Open

Changed Status from Closed to New

Changed Assigned User from @User_306070 to @anonymous

---

No it's not. That's why I'm reporting this.Tab'ing away doesn't update the paramater. Clicking in any other field doesn't update the paramater.Only thing that updates the paramater is restarting JSS.Kind regards,Maarten

Changed Status from New to Feedback Requested

---

Are you using the last integration build or the official 5.6.0?I just tried and I didn't noticed any issue.Were you able to try in different OS?I will ask internally to quick test the problem into a Mac OS X 10.9.3. If I'm not wrong, you are using that version. Correct?Regards,Massimo.

Still happening. In addition, with the second (I made 2 in 2 different data sets, none showing the set name) paramater JSS refused to save it's name even. Quitting JSS and trying again is the answer.

 

Jaspersoft Studio 5.6.1.SNAPSHOT.beta.v201407070946

Java 7

Mac OS 10.9.4

Changed Priority from Normal to High

Changed Severity from Major to Block

Changed Status from Feedback Requested to New

---

Hi,How to reproduce: Create Variables or Paramaters in subdatasets. Sometimes it takes 2-3 to make the bug trigger.Since JSS 5.6.0 and all betas. Currently (v201407231036) only happening in Subdatasets.

Changed Status from New to Feedback Requested

---

Hi,can you please attach a screencast of the operations you perform. It seems we are not able to reproduce.Maybe there something else you do that is raising the problem.Thanks in advance.Best regards,Massimo.

Hi,

 

I did further testing. It consequently happens after you paste in a more complex subdatasource.

Screencast: http://cl.ly/WmEr

 

Further remarks:

- Once the subdatasource is added, top level paramaters also no longer can have name changed.

- Pressing Tab on keyboard no longer tabs to the next element/saves name.

- JSS seems to remember the name of first paramater entered.

- After first paramater, no name is remembered.

- Creating new fields no longer auto selects that field, causing unable to create second field without clicking around. http://community.jaspersoft.com/jaspersoft-studio/issues/3795

- Copy pasting seems to stop working often also

 

We prefer not to share our test subdatasource, so what it contains:

- 30+ fields with names and descriptions and string+float classes.

- 1 Paramater specific you our implementation of JRDatasourceProvider.

- This subdatasource is copied from a pre-generated .jrxml from our implementation.

 

Kind regards,

Maarten @ Yesplan

Hi,

I asked to verify in Mac OS X 10.9.4 with the latest integration build to one of my colleagues.

Response: not reproducible.

First test: remaining in property dialog and changing focus to different field

Second test: after entering name - leaving property panel without setting focus to different field

http://screencast.com/t/QWMqffRI5u

 

Is it possible you have environment specific settings in Mac OS X, maybe related to focus or similar?

 

Regards,

Massimo.

Hi,

 

No, nothing special. What I do have is I forced JSS to run in Java 7, instead of Java 6.

 

I will send an email with a file.

If you did not modified the Jaspersoft Studio.ini file, JSS was already using the JVM 1.7: the one bundled with the package.

 

Regards,

Massimo.

We discussed this, the one bundled is NOT being loaded. Never has (since I've been testing). If I forcibly point to the bundled version, it gives me the error that it's an invalid runtime. As I've previously explained.

 

The Eclipse will happily run on JVM 1.6 and compile against 1.7 without problems. But if you check your configuration details of JSS, you'll see it has used the system's JVM 1.6.

 

I use:

-vm

/Library/Java/JavaVirtualMachines/jdk1.7.0_65.jdk/Contents/Home/bin

 

Changed Priority from High to Immediate

Changed Status from Feedback Requested to Acknowledged

---

Again, this issue is just the tip of the iceberg. This is the indication that JSS is going wrong. Edits are no longer saved, copy-paste starts failing... In a way I'm glad I can spot it early on and save before I lose too many changes.With the latest build and just working on a report (nothing too special, not even manipulating subdatasets) I'm encountering it every 30 minutes.

Immediately editing a parameter after previewing a report usually causes this also.

Changed Assigned User from - to @User_306070

---

May this have something to do that we have parameters with our own java classes?

Changed Assigned User from @User_306070 to @anonymous

---

Hi,resuming the thread. I tried to reproduce again the issue. I'm currently using a Mac OS X 10.10.1. Still not able to.Are you still experiencing the issue.Regards,Massimo.

Yes, me and all my colleagues are still experiencing this. I tried reproducing this on a Windows VM, same issue.

 

For testing purposes, I attached a 'base' file that will trigger the issue with 100% chance on Mac and windows with any recent version go JSS.

 

Steps:

- Change a name of an existing parameter.

 

Our common setup: Java 7, JSS 6.0.3, Mac OS X 10.10.2 (14C109)

 

Kind regards,

Maarten @ Yesplan

Changed Assigned User from @anonymous to @mrabbi

---

Ok thanks Maarten.I'll investigate using the attached report.Regards,Massimo.

Changed Resolution from Open to Fixed

Changed Status from Acknowledged to Resolved

---

Hi Marteen,just checked with you report. It appeared to be a NPE error.It was caused by a missing null check on the dataset query object.For some reasons, in your report there was not this kind of JRXML section: That's the reason why I was not able to reproduce in the past attempts. Usually creating the test report with SampleDB or another DA I was always ending up having it in my JRXML code.Just for curiosity, how did you created the report? I've checked in the null check and now it works fine.I will produce another integration build tomorrow or Wednesday that will contain also this fix.Regards,Massimo.

Thank you.

 

1) We build a jrxml generator that produces a jrxml with the correct fields in main and subdata sets. We use these as a foundation. (highly dynamic fields)

 

2) We did not use the "queryString" in the past, because we use more complex expressions that talk directly with the provider plugin. Maybe not the most elegant solution we have build, but definitely one that is quite flexible to (attempt to) match the dynamic nature of our main product.

 

 

Kind regards,

Maarten @ Yesplan

Thanks!! I've been testing the latest beta build and this is such a relief! This removes 73% of my stress.

 

 

Kind regards,

Maarten Van Coile