Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [birt-dev] problem with linking report parameters with DataSetparametersonBIRT 2.2.2
Hi Ernesto

It wasn't the reply.
i need to ask if anybody can help me out on this issue.
 



Thanks ,
With Kind Regards 
Riyaz Tak | Associate Engineering| GlobalLogic India
The Leader in Global Product Development
Site 438, Sagar Complex, Bhosari, Pune
Phone: +91-020-66316600-678| Fax: +91-020-66316641
Mobile: +919820101855  






----- Original Message ----
From: Ernesto Reinaldo Barreiro <ereinaldob@xxxxxx>
To: For developers on the BIRT project <birt-dev@xxxxxxxxxxx>
Sent: Wednesday, 30 April, 2008 5:35:44 PM
Subject: Re: [birt-dev] problem with linking report parameters with DataSetparametersonBIRT 2.2.2

Hi,

The problem I have is not with running the report (In fact this report will produce no out-put) but with the report designer which will fail to edit the DataSet with name DataSet222 because version 2.2.2 of the designer is generating a faulty XML (see bellow). I don't know if this is because I'm missing something but the fact is that this doesn't happen when using version 2.2.1.1 of the designer (connecting to the same database and using the same informix SQL driver). I guess this report will not run on your server as I have replaced the sensible parts of the connection URL  with XXXX... I just attached it to illustrate the differences between the XML 2.2.1.1 generated and the XML generated by version 2.2.2....  I might try to use sample database included with BIRT to build this example and see if this is not depending on the connection to our database (but I don't think so because it was also happening when connecting to our own ODA extensions which do not use  JDBC)...

Thanks for your answer

Ernesto
Hi

I tried to run report using  frameset in birt  but what i came to know there is no problem with frameset.
but what is happening here is that at runtime when i am trying to create to report and displaying it at a same time  it's giving
me errors coz it's keeping that report in memory ( http://dev.eclipse.org/newslists/news.eclipse.birt/msg16121.html).
 
Then what i tried i created report at run time and saved it somewhere and then at next time i just tried to display that
Report and it worked.So i guess i need to find out some way by which it don't keep report in memory at run time.
 
I guess just coz of that my Tomcat is running out of memory very frequently.
 
But this thing is happening with Frameset only. With run servlet it's working fine.
 
Your suggestions are most welcome.
 



Thanks ,
With Kind Regards 
Riyaz Tak | Associate Engineering| GlobalLogic India
The Leader in Global Product Development
Site 438, Sagar Complex, Bhosari, Pune
Phone: +91-020-66316600-678| Fax: +91-020-66316641
Mobile: +919820101855  






----- Original Message ----
From: Ernesto Reinaldo Barreiro <ereinaldob@xxxxxx>
To: birt-dev@xxxxxxxxxxx
Sent: Wednesday, 30 April, 2008 4:36:52 PM
Subject: [birt-dev] problem with linking report parameters with DataSet parameters onBIRT 2.2.2


Dear BIRT developers,

After migrating from BIRT 2.2.1.1 to BIRT 2.2.2 I'm not able anymore to
link DataSet parameters to "dynamic" report parameters which are
associated to a DataSet. I discover this while working with our own ODA
extensions and at first I though this was because we were missing
something or doing something wrong. After debugging  a bit I discover
that the steps involved in the creation of the "standard "
JdbcSelectDataSet where exactly the same as the ones involved in the
creation of our extension.. So, I decided to try to build example using
only JdbcSelectDataSets.

With version 2.2.1.1 I'm able to create a DataSet, link it to dynamic
parameters and later on edit it (DataSet2211). With version 2..2.2 I can
create the DataSet (see DataSet222) but not edit it. I think the problem
arises because 2.2.2 is failing to correctly create the XML tag:
<design:dynamicValueChoices>: it creates something like:

<design:dynamicValueChoices>
            <design:enabled>false</design:enabled>
</design:dynamicValueChoices>

while version 2.2.1.1 creates something like:

<design:dynamicValueChoices>
<design:dataSetDesign>
              <design:name>Equipos</design:name>
             
<design:odaExtensionDataSetId>org.eclipse.birt.report.data.oda.jdbc.JdbcSelectDataSet</design:odaExtensionDataSetId>
              <design:dataSourceDesign>
                <design:name>Informix</design:name>
               
<design:odaExtensionId>org.eclipse.birt.report.data.oda.jdbc</design:odaExtensionId>
                <design:publicProperties>
                  <design:properties>
                    <design:nameValue>
                      <design:name>odaDriverClass</design:name>
                     
<design:value>com.informix.jdbc.IfxDriver</design:value>
                    </design:nameValue>
                  </design:properties>
                  <design:properties>
                    <design:nameValue>
                      <design:name>odaURL</design:name>
                     
<design:value>jdbc:informix-sqli://blifx1:1526/ma_prc_maquinaria:INFORMIXSERVER=olblifx1;user=Fccsg\ema;password=Fccsa2004;DBDATE=DMY4;IFX_TRIMTRAILINGSPACES=1;IFX_USEPUT=1;IFX_BATCHUPDATE_PER_SPEC=0;OPTOFC=1;DB_LOCALE=es_es.CP1252</design:value>
                    </design:nameValue>
                  </design:properties>
                  <design:properties>
                    <design:nameValue>
                      <design:name>odaUser</design:name>
                    </design:nameValue>
                  </design:properties>
                  <design:properties>
                    <design:nameValue>
                      <design:name>odaPassword</design:name>
                    </design:nameValue>
                  </design:properties>
                  <design:properties>
                    <design:nameValue>
                      <design:name>odaJndiName</design:name>
                    </design:nameValue>
                  </design:properties>
                  <design:properties>
                    <design:nameValue>
                      <design:name>OdaConnProfileName</design:name>
                    </design:nameValue>
                  </design:properties>
                  <design:properties>
                    <design:nameValue>
                      <design:name>OdaConnProfileStorePath</design:name>
                    </design:nameValue>
                  </design:properties>
                </design:publicProperties>
              </design:dataSourceDesign>
              <design:query>
                <design:queryText>select * from maqeqc</design:queryText>
              </design:query>
              <design:publicProperties>
                <design:properties>
                  <design:nameValue>
                    <design:name>queryTimeOut</design:name>
                  </design:nameValue>
                </design:properties>
              </design:publicProperties>
              <design:resultSets>
                <design:resultSetDefinitions>
                  <design:resultSetColumns>
                    <design:resultColumnDefinitions>
                      <design:attributes>
                        <design:name>equ_eqc</design:name>
                        <design:position>1</design:position>
                       
<design:nativeDataTypeCode>12</design:nativeDataTypeCode>
                        <design:uiHints>
                          <design:displayName>equ_eqc</design:displayName>
                        </design:uiHints>
                      </design:attributes>
                    </design:resultColumnDefinitions>
                    <design:resultColumnDefinitions>
                      <design:attributes>
                        <design:name>com_eqc</design:name>
                        <design:position>2</design:position>
                       
<design:nativeDataTypeCode>12</design:nativeDataTypeCode>
                        <design:uiHints>
                          <design:displayName>com_eqc</design:displayName>
                        </design:uiHints>
                      </design:attributes>
                    </design:resultColumnDefinitions>
                    <design:resultColumnDefinitions>
                      <design:attributes>
                        <design:name>den_eqc</design:name>
                        <design:position>3</design:position>
                       
<design:nativeDataTypeCode>12</design:nativeDataTypeCode>
                        <design:uiHints>
                          <design:displayName>den_eqc</design:displayName>
                        </design:uiHints>
                      </design:attributes>
                    </design:resultColumnDefinitions>
                  </design:resultSetColumns>
                </design:resultSetDefinitions>
              </design:resultSets>
            </design:dataSetDesign>
            <design:enabled>true</design:enabled>
           
<design:valueColumn>dataSetRow[&quot;equ_eqc&quot;]</design:valueColumn>
           
<design:displayNameColumn>dataSetRow[&quot;den_eqc&quot;]</design:displayNameColumn>
          </design:dynamicValueChoices>
       
(See attachment for complete report XML).

Am I missing something? Or is this a bug?


Best regards,

Ernesto


*************************************************************
Este correo ha sido procesado por el antivirus del Grupo FCC.
*************************************************************


Bring your gang together. Do your thing. Find your favourite Yahoo! Group.
************************************************************
Este correo ha sido procesado por el antivirus del Grupo FCC
************************************************************
 

_______________________________________________
birt-dev mailing list
birt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/birt-dev

*************************************************************
Este correo ha sido procesado por el antivirus del Grupo FCC.
*************************************************************


Bollywood, fun, friendship, sports and more. You name it, we have it.

Back to the top