Menu
▾
▴
lmappletserver-developers
|
From: Peter S. <co...@pe...> - 2007-06-21 13:32:42
|
Hi, If we have column names that contain e.g. scandinavian characters like : = =C3=A6=C3=B8=C3=A5 ,=20 or others like =E1=BA=BD =C3=A9 etc. there is a problem with the dynamic be= an setters and=20 getters. Could you propose a solution for this? regards, Peter |
|
From: Peter S. <co...@pe...> - 2007-06-21 13:36:48
|
Just as a follow up. Ideally, the metadata column names should maybe serve = as=20 keys to a language property file? so that the metadata columns also could b= e=20 shown in different languages. In this case one would of course require that= =20 the key names (=3D metadata column names) had valid characters. Take this into account when proposing a solution. Regards, Peter On Thursday 21 June 2007 15:32:05 Peter Salomonsen wrote: > Hi, > > If we have column names that contain e.g. scandinavian characters like : > =C3=A6=C3=B8=C3=A5 , or others like =E1=BA=BD =C3=A9 etc. there is a prob= lem with the dynamic bean > setters and getters. > > Could you propose a solution for this? > > regards, > > Peter > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Lmappletserver-developers mailing list > Lma...@li... > https://lists.sourceforge.net/lists/listinfo/lmappletserver-developers |
|
From: Roberto M. <rob...@gm...> - 2007-06-26 12:45:19
|
Hi Peter, I agree. Database metadata to be created as english (no special characters) names. These names will be used as keys to a property file named column_names.properties. In this property file the metadata keys will be mapped to values as wished (with special characters). These naming will be used only for display purpose. When generating report or xls/csv the database keys will be used, and if so, the class field generator will have no problems. Regards, Roberto Peter Salomonsen wrote: > Just as a follow up. Ideally, the metadata column names should maybe serve as > keys to a language property file? so that the metadata columns also could be > shown in different languages. In this case one would of course require that > the key names (= metadata column names) had valid characters. > > Take this into account when proposing a solution. > > Regards, > > Peter > > On Thursday 21 June 2007 15:32:05 Peter Salomonsen wrote: > >> Hi, >> >> If we have column names that contain e.g. scandinavian characters like : >> æøå , or others like ẽ é etc. there is a problem with the dynamic bean >> setters and getters. >> >> Could you propose a solution for this? >> >> regards, >> >> Peter >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Lmappletserver-developers mailing list >> Lma...@li... >> https://lists.sourceforge.net/lists/listinfo/lmappletserver-developers >> > > > > |
|
From: Peter S. <co...@pe...> - 2007-06-26 13:37:21
|
Sounds good... It's a go then .. cheers, Peter On Tuesday 26 June 2007 14:45:09 Roberto MIlev wrote: > Hi Peter, > > I agree. > > Database metadata to be created as english (no special characters) > names. These names will be used as keys to a property file named > column_names.properties. In this property file the metadata keys will be > mapped to values as wished (with special characters). These naming will > be used only for display purpose. When generating report or xls/csv the > database keys will be used, and if so, the class field generator will > have no problems. > > Regards, > Roberto > > Peter Salomonsen wrote: > > Just as a follow up. Ideally, the metadata column names should maybe > > serve as keys to a language property file? so that the metadata columns > > also could be shown in different languages. In this case one would of > > course require that the key names (=3D metadata column names) had valid > > characters. > > > > Take this into account when proposing a solution. > > > > Regards, > > > > Peter > > > > On Thursday 21 June 2007 15:32:05 Peter Salomonsen wrote: > >> Hi, > >> > >> If we have column names that contain e.g. scandinavian characters like= : > >> =C3=A6=C3=B8=C3=A5 , or others like =E1=BA=BD =C3=A9 etc. there is a p= roblem with the dynamic bean > >> setters and getters. > >> > >> Could you propose a solution for this? > >> > >> regards, > >> > >> Peter > >> > >> ----------------------------------------------------------------------= =2D- > >>- This SF.net email is sponsored by DB2 Express > >> Download DB2 Express C - the FREE version of DB2 express and take > >> control of your XML. No limits. Just data. Click to get it now. > >> http://sourceforge.net/powerbar/db2/ > >> _______________________________________________ > >> Lmappletserver-developers mailing list > >> Lma...@li... > >> https://lists.sourceforge.net/lists/listinfo/lmappletserver-developers |
|
From: Roberto M. <rob...@gm...> - 2007-07-03 12:10:58
|
Hi Peter, The changes for handling special characters are done and committed. Please have a look. Total time spent on this task 14 hours. Regards, Roberto Peter Salomonsen wrote: > Sounds good... It's a go then .. > > cheers, > > Peter > > On Tuesday 26 June 2007 14:45:09 Roberto MIlev wrote: > >> Hi Peter, >> >> I agree. >> >> Database metadata to be created as english (no special characters) >> names. These names will be used as keys to a property file named >> column_names.properties. In this property file the metadata keys will be >> mapped to values as wished (with special characters). These naming will >> be used only for display purpose. When generating report or xls/csv the >> database keys will be used, and if so, the class field generator will >> have no problems. >> >> Regards, >> Roberto >> >> Peter Salomonsen wrote: >> >>> Just as a follow up. Ideally, the metadata column names should maybe >>> serve as keys to a language property file? so that the metadata columns >>> also could be shown in different languages. In this case one would of >>> course require that the key names (= metadata column names) had valid >>> characters. >>> >>> Take this into account when proposing a solution. >>> >>> Regards, >>> >>> Peter >>> >>> On Thursday 21 June 2007 15:32:05 Peter Salomonsen wrote: >>> >>>> Hi, >>>> >>>> If we have column names that contain e.g. scandinavian characters like : >>>> æøå , or others like ẽ é etc. there is a problem with the dynamic bean >>>> setters and getters. >>>> >>>> Could you propose a solution for this? >>>> >>>> regards, >>>> >>>> Peter >>>> >>>> ------------------------------------------------------------------------ >>>> - This SF.net email is sponsored by DB2 Express >>>> Download DB2 Express C - the FREE version of DB2 express and take >>>> control of your XML. No limits. Just data. Click to get it now. >>>> http://sourceforge.net/powerbar/db2/ >>>> _______________________________________________ >>>> Lmappletserver-developers mailing list >>>> Lma...@li... >>>> https://lists.sourceforge.net/lists/listinfo/lmappletserver-developers >>>> > > > > |
|
From: Peter S. <co...@pe...> - 2007-07-04 12:26:36
|
Hi Roberto, The new MetaDataColumnNames.properties file works just perfect. Could we also extend it so that if a key doesn't exist, the metadatacolumn name is showed directly? regards, Peter |
|
From: Roberto M. <rob...@gm...> - 2007-07-08 15:59:37
|
Hi Peter, The change to display the metadatacolumn name is no key exists in property file is commited. Additionally I did anothetr small change to display the localized strings in the search combo box. Regards, Roberto Peter Salomonsen wrote: > Hi Roberto, > > The new MetaDataColumnNames.properties file works just perfect. Could we also > extend it so that if a key doesn't exist, the metadatacolumn name is showed > directly? > > regards, > > Peter > > |
|
From: Peter S. <co...@pe...> - 2007-07-11 10:50:05
|
Hi Roberto, Your question whether we should use region or placemark, makes me think we should generalize this even more. Cause we really want to be able to use everything. The objects might be fixed, but also moving - so the kml must be customizable. So my question is: - Would it be possible to create a report template that produces xml (which in this case will be kml)? - The kml url mention earlier, will then instead of being kml specific, be mapped to a report - so that you can get a report (with any template) on the fly just using a url. How would this be? regards, Peter On Tuesday 10 July 2007 16:58:18 you wrote: > Hi Peter, > > Yes, I started looking into the google-map integration. > > The approach to this task would be to create e a servlet with *.kml > mapping. The request with > http://lmappletserver.lightminds.com/lmas-addons-example/ > kml/mysearch.kml<http://lmappletserver.lightminds.com/lmas-addons-example/k >ml/mysearch.kml>, that mysearch will be the saved search name, this I think > is the best because the Saved search name is unique, and can be used as > identifier. When the servlet is called and executes the saved search a > transformer class will create the mysearch.kml content string from the > result of the search. Then this string will be sent to the client as output > stream. At this moment I look at two approaches, and I would like for you > to tell which one to use, first one is to use the Placemark tag to create a > yellow pin(in Google Earth), and lead the user to that spot. This is done > by kml like this: > > <?xml version="1.0" encoding="UTF-8"?> > <kml xmlns="http://earth.google.com/kml/2.1"> > <Placemark> > <name>Macky Auditorium</name> > <description>University of Colorado.</description> > <LookAt> > <longitude>-105.2727379358738</longitude> > <latitude>40.01000594412381</latitude> > <altitude>0</altitude> > <range>127.2393107680517</range> > <tilt>65.74454495876547</tilt> > <heading>-27.70337734057933</heading> > </LookAt> > </Placemark> > </kml> > > Or we can use the Region tag, and show regions of the airport, and be > visible only when the user reaches certain zooming resolution. This is done > by kml like this: > > <?xml version="1.0" encoding="UTF-8"?> > <kml xmlns="http://earth.google.com/kml/2.1"> > <Document> > <name>romania Document</name> > <Region> > <LatLonAltBox> > <north>50.625</north> > <south>45</south> > <east>28.125</east> > <west>22.5</west> > </LatLonAltBox> > <Lod> > <minLodPixels>128</minLodPixels> > <maxLodPixels>1024</maxLodPixels> > </Lod> > </Region> > </Document> > </kml> > > Here because of the fact that in the current database we have only > latitude, longitude and altitude we have to make coordinate transformation, > therefore I think that this approach is not appropriate for our > application. > > Regards, > Roberto > > On 7/9/07, Peter Salomonsen <co...@pe...> wrote: > > Hi, > > > > This and the checkbox scrollbar looks good as far as I can see.. > > > > Have you looked into the google-map (kml) integration? > > > > regards, > > > > Peter > > > > On Sunday 08 July 2007 17:59:30 you wrote: > > > Hi Peter, > > > > > > The change to display the metadatacolumn name is no key exists in > > > property file is commited. Additionally I did anothetr small change to > > > display the localized strings in the search combo box. > > > > > > Regards, > > > Roberto > > > > > > Peter Salomonsen wrote: > > > > Hi Roberto, > > > > > > > > The new MetaDataColumnNames.properties file works just perfect. Could > > > > we > > > > > > also extend it so that if a key doesn't exist, the metadatacolumn > > > > name > > > > is > > > > > > showed directly? > > > > > > > > regards, > > > > > > > > Peter |
|
From: Roberto M. <rob...@gm...> - 2007-07-16 04:55:25
|
Hi Peter,
I have started working on implementing the feature. I have created a new
servlet - XmlReportServelet. My idea is to be able to use the reporting
template mechanism that we have, but load report templates in XSLT
format. The results of a saved search would be represented in a fixed
defined XML format, for e.g.:
<searchResults latest="true">
<row>
<column name="id" >1</column>
<column name="airportName" >JFK</column>
<column name="latitude" >- 44.98</column>
<column name="longitude" >15.63</column>
<column name="altitude" >128</column>
<column name="windSpeed" >43</column>
</row>
<row>
<column name="id" >2</column>
<column name="airportName" >JFK</column>
<column name="latitude" >- 44.98</column>
<column name="longitude" >15.63</column>
<column name="altitude" >128</column>
<column name="windSpeed" >43</column>
</row>
</searchResults>
The new servlet would apply the XSL transformation to this XML and
return the result. It would receive the the template and search names
(unique IDs) as URL params for e.g.:
/xmlReport/Position.klm?template=Placemark&search=Vehicle1
This would ultimately allow us to have URLs that generate HTML reports,
RSS feeds etc.
If this approach is OK I believe i will be able to deliver the full
implementation by the end of this week.
Regards,
Roberto
Peter Salomonsen wrote:
> Hi Roberto,
>
> Your question whether we should use region or placemark, makes me think we
> should generalize this even more. Cause we really want to be able to use
> everything. The objects might be fixed, but also moving - so the kml must be
> customizable.
>
> So my question is:
>
> - Would it be possible to create a report template that produces xml (which in
> this case will be kml)?
> - The kml url mention earlier, will then instead of being kml specific, be
> mapped to a report - so that you can get a report (with any template) on the
> fly just using a url. How would this be?
>
> regards,
>
> Peter
>
> On Tuesday 10 July 2007 16:58:18 you wrote:
>
>> Hi Peter,
>>
>> Yes, I started looking into the google-map integration.
>>
>> The approach to this task would be to create e a servlet with *.kml
>> mapping. The request with
>> http://lmappletserver.lightminds.com/lmas-addons-example/
>> kml/mysearch.kml<http://lmappletserver.lightminds.com/lmas-addons-example/k
>> ml/mysearch.kml>, that mysearch will be the saved search name, this I think
>> is the best because the Saved search name is unique, and can be used as
>> identifier. When the servlet is called and executes the saved search a
>> transformer class will create the mysearch.kml content string from the
>> result of the search. Then this string will be sent to the client as output
>> stream. At this moment I look at two approaches, and I would like for you
>> to tell which one to use, first one is to use the Placemark tag to create a
>> yellow pin(in Google Earth), and lead the user to that spot. This is done
>> by kml like this:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <kml xmlns="http://earth.google.com/kml/2.1">
>> <Placemark>
>> <name>Macky Auditorium</name>
>> <description>University of Colorado.</description>
>> <LookAt>
>> <longitude>-105.2727379358738</longitude>
>> <latitude>40.01000594412381</latitude>
>> <altitude>0</altitude>
>> <range>127.2393107680517</range>
>> <tilt>65.74454495876547</tilt>
>> <heading>-27.70337734057933</heading>
>> </LookAt>
>> </Placemark>
>> </kml>
>>
>> Or we can use the Region tag, and show regions of the airport, and be
>> visible only when the user reaches certain zooming resolution. This is done
>> by kml like this:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <kml xmlns="http://earth.google.com/kml/2.1">
>> <Document>
>> <name>romania Document</name>
>> <Region>
>> <LatLonAltBox>
>> <north>50.625</north>
>> <south>45</south>
>> <east>28.125</east>
>> <west>22.5</west>
>> </LatLonAltBox>
>> <Lod>
>> <minLodPixels>128</minLodPixels>
>> <maxLodPixels>1024</maxLodPixels>
>> </Lod>
>> </Region>
>> </Document>
>> </kml>
>>
>> Here because of the fact that in the current database we have only
>> latitude, longitude and altitude we have to make coordinate transformation,
>> therefore I think that this approach is not appropriate for our
>> application.
>>
>> Regards,
>> Roberto
>>
>> On 7/9/07, Peter Salomonsen <co...@pe...> wrote:
>>
>>> Hi,
>>>
>>> This and the checkbox scrollbar looks good as far as I can see..
>>>
>>> Have you looked into the google-map (kml) integration?
>>>
>>> regards,
>>>
>>> Peter
>>>
>>> On Sunday 08 July 2007 17:59:30 you wrote:
>>>
>>>> Hi Peter,
>>>>
>>>> The change to display the metadatacolumn name is no key exists in
>>>> property file is commited. Additionally I did anothetr small change to
>>>> display the localized strings in the search combo box.
>>>>
>>>> Regards,
>>>> Roberto
>>>>
>>>> Peter Salomonsen wrote:
>>>>
>>>>> Hi Roberto,
>>>>>
>>>>> The new MetaDataColumnNames.properties file works just perfect. Could
>>>>>
>>> we
>>>
>>>
>>>>> also extend it so that if a key doesn't exist, the metadatacolumn
>>>>> name
>>>>>
>>> is
>>>
>>>
>>>>> showed directly?
>>>>>
>>>>> regards,
>>>>>
>>>>> Peter
>>>>>
>
>
>
>
|
|
From: Peter S. <co...@pe...> - 2007-07-11 11:38:03
|
This is not neccesary in the lmappletserver_addons libraries. This should b= e=20 handled by each implementing application. The lmappletserver_addons urls should be completely open by default. regards, Peter On Wednesday 11 July 2007 13:02:11 Jon =C3=85kerstr=C3=B6m wrote: > Also I'm curious how will the kml be secured? Have you looked into that? > How do we avoid users that are not allowed to view the units in the .kml > gets access to them simply by knowint the url? > > Best regards > Jonte > > On Wed, 2007-07-11 at 12:49 +0200, Peter Salomonsen wrote: > > Hi Roberto, > > > > Your question whether we should use region or placemark, makes me think > > we should generalize this even more. Cause we really want to be able to > > use everything. The objects might be fixed, but also moving - so the kml > > must be customizable. > > > > So my question is: > > > > - Would it be possible to create a report template that produces xml > > (which in this case will be kml)? > > - The kml url mention earlier, will then instead of being kml specific, > > be mapped to a report - so that you can get a report (with any template) > > on the fly just using a url. How would this be? > > > > regards, > > > > Peter > > > > On Tuesday 10 July 2007 16:58:18 you wrote: > > > Hi Peter, > > > > > > Yes, I started looking into the google-map integration. > > > > > > The approach to this task would be to create e a servlet with *.kml > > > mapping. The request with > > > http://lmappletserver.lightminds.com/lmas-addons-example/ > > > kml/mysearch.kml<http://lmappletserver.lightminds.com/lmas-addons-exa= mp > > >le/k ml/mysearch.kml>, that mysearch will be the saved search name, th= is > > > I think is the best because the Saved search name is unique, and can = be > > > used as identifier. When the servlet is called and executes the saved > > > search a transformer class will create the mysearch.kml content string > > > from the result of the search. Then this string will be sent to the > > > client as output stream. At this moment I look at two approaches, and= I > > > would like for you to tell which one to use, first one is to use the > > > Placemark tag to create a yellow pin(in Google Earth), and lead the > > > user to that spot. This is done by kml like this: > > > > > > <?xml version=3D"1.0" encoding=3D"UTF-8"?> > > > <kml xmlns=3D"http://earth.google.com/kml/2.1"> > > > <Placemark> > > > <name>Macky Auditorium</name> > > > <description>University of Colorado.</description> > > > <LookAt> > > > <longitude>-105.2727379358738</longitude> > > > <latitude>40.01000594412381</latitude> > > > <altitude>0</altitude> > > > <range>127.2393107680517</range> > > > <tilt>65.74454495876547</tilt> > > > <heading>-27.70337734057933</heading> > > > </LookAt> > > > </Placemark> > > > </kml> > > > > > > Or we can use the Region tag, and show regions of the airport, and be > > > visible only when the user reaches certain zooming resolution. This is > > > done by kml like this: > > > > > > <?xml version=3D"1.0" encoding=3D"UTF-8"?> > > > <kml xmlns=3D"http://earth.google.com/kml/2.1"> > > > <Document> > > > <name>romania Document</name> > > > <Region> > > > <LatLonAltBox> > > > <north>50.625</north> > > > <south>45</south> > > > <east>28.125</east> > > > <west>22.5</west> > > > </LatLonAltBox> > > > <Lod> > > > <minLodPixels>128</minLodPixels> > > > <maxLodPixels>1024</maxLodPixels> > > > </Lod> > > > </Region> > > > </Document> > > > </kml> > > > > > > Here because of the fact that in the current database we have only > > > latitude, longitude and altitude we have to make coordinate > > > transformation, therefore I think that this approach is not appropria= te > > > for our application. > > > > > > Regards, > > > Roberto > > > > > > On 7/9/07, Peter Salomonsen <co...@pe...> wrote: > > > > Hi, > > > > > > > > This and the checkbox scrollbar looks good as far as I can see.. > > > > > > > > Have you looked into the google-map (kml) integration? > > > > > > > > regards, > > > > > > > > Peter > > > > > > > > On Sunday 08 July 2007 17:59:30 you wrote: > > > > > Hi Peter, > > > > > > > > > > The change to display the metadatacolumn name is no key exists in > > > > > property file is commited. Additionally I did anothetr small chan= ge > > > > > to display the localized strings in the search combo box. > > > > > > > > > > Regards, > > > > > Roberto > > > > > > > > > > Peter Salomonsen wrote: > > > > > > Hi Roberto, > > > > > > > > > > > > The new MetaDataColumnNames.properties file works just perfect. > > > > > > Could > > > > > > > > we > > > > > > > > > > also extend it so that if a key doesn't exist, the metadatacolu= mn > > > > > > name > > > > > > > > is > > > > > > > > > > showed directly? > > > > > > > > > > > > regards, > > > > > > > > > > > > Peter > > > > -----------------------------------------------------------------------= =2D- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > Lmappletserver-developers mailing list > > Lma...@li... > > https://lists.sourceforge.net/lists/listinfo/lmappletserver-developers |
|
From: Roberto M. <rob...@gm...> - 2007-07-20 06:01:38
Attachments:
Search.xml
|
He Peter, I have committed the functionality to retrieve searches in XML. I modified the existing report servlet to handle this. So now if you navigate to: http://localhost:8080/lmas-addons-example/reportservlet?searchName=Search_1 you will get an XML representation of the search result (see attachment). I also removed the dynamic bean creation stuff an modified the pdf creation to use this XML as a data source. This makes authoring jasper templates in iReport even easier. You should use the actual XML file and setup a datasource. In the query window select XPath, and use "/searchResults/row" as the search expression. Form the XPath selection drag and drop to define your fields. I also updated the sample jasper templates in the full example project. The PDF functionality is still there and you can get a PDF of a report if you navigate to (this URL is also used form the meta data applet): http://localhost:8080/lmas-addons-example/reportservlet?reportName=Report_1 Please have a look and send me your comments. Regards, Roberto Peter Salomonsen wrote: > On Monday 16 July 2007 06:55:16 you wrote: > >> I have started working on implementing the feature. I have created a new >> servlet - XmlReportServelet. My idea is to be able to use the reporting >> template mechanism that we have, but load report templates in XSLT >> format. The results of a saved search would be represented in a fixed >> defined XML format, for e.g.: >> >> <searchResults latest="true"> >> <row> >> <column name="id" >1</column> >> <column name="airportName" >JFK</column> >> <column name="latitude" >- 44.98</column> >> <column name="longitude" >15.63</column> >> <column name="altitude" >128</column> >> <column name="windSpeed" >43</column> >> </row> >> <row> >> <column name="id" >2</column> >> <column name="airportName" >JFK</column> >> <column name="latitude" >- 44.98</column> >> <column name="longitude" >15.63</column> >> <column name="altitude" >128</column> >> <column name="windSpeed" >43</column> >> </row> >> </searchResults> >> > > This is a very good idea. Is this format compatible with the XML data source > that you have in iReport? Eventually could you change it so that it would be > compatible? > > >> The new servlet would apply the XSL transformation to this XML and >> return the result. It would receive the the template and search names >> (unique IDs) as URL params for e.g.: >> /xmlReport/Position.klm?template=Placemark&search=Vehicle1 >> > > XSL transformation is a good way of providing the kml. Actually I don't think > you should implement this part then. Providing the xml is enough, and let > external applications apply xsl templates for now. I think just providing the > stored search as xml is sufficient for now - and we'll make the decision > about also storing xml templates later. > > >> This would ultimately allow us to have URLs that generate HTML reports, >> RSS feeds etc. >> > > That is exactly what we want. > > Since we're now going for XMLDatasources would this eliminate the need for the > DynamicBean? I see a problem with this regarding datatypes. The DynamicBean > makes everything as strings, and this is e.g. a problem when sorting numbers > in the report. > > With the xml datasource we wouldn't any longer have to use the csv for > designing templates in iReport - right? > > Another thing - iReport has a possibility of viewing the report as Excel - > could we use the same mechanism to send an excel file rather than pdf? > > regards, > > Peter > > > |
|
From: Peter S. <co...@pe...> - 2007-07-20 09:25:01
|
Hi Roberto, The XML servlet is great, and it's much better to use in iReport. Did you manage to use the remote xml datasource? (I had some problems with it..) This would be even better. One downside with the xml datasource, is that the Report Wizard won't accept it. Is there a way around this? Suggestions? About this: http://localhost:8080/lmas-addons-example/reportservlet?reportName=Report_1 It does always delete my report - and I know it's because of the "Print current report" function - but could we make it possible get an on-demand pdf without deleting? Further - in addition to pdf - could we also get an Excel doc - just like when using the excel preview function in iReport? Maybe introduce some switches? : http://localhost:8080/lmas-addons-example/reportservlet?reportName=Report_1&type=excel&delete=false (other types pdf, and the print current report could use delete=true) And - regarding xsl transformation (to google kml's and other htmls) - any suggestions on how to solve this? Should we introduce xsl template uploading? We can use the reportservlet for also viewing xsl reports, the servlet will figure out if the template used is xsl? regards, Peter On Friday 20 July 2007 08:01:29 you wrote: > He Peter, > > I have committed the functionality to retrieve searches in XML. I > modified the existing report servlet to handle this. So now if you > navigate to: > > http://localhost:8080/lmas-addons-example/reportservlet?searchName=Search_1 > > you will get an XML representation of the search result (see > attachment). I also removed the dynamic bean creation stuff an modified > the pdf creation to use this XML as a data source. This makes authoring > jasper templates in iReport even easier. You should use the actual XML > file and setup a datasource. In the query window select XPath, and use > "/searchResults/row" as the search expression. Form the XPath selection > drag and drop to define your fields. I also updated the sample jasper > templates in the full example project. > > The PDF functionality is still there and you can get a PDF of a report > if you navigate to (this URL is also used form the meta data applet): > http://localhost:8080/lmas-addons-example/reportservlet?reportName=Report_1 > > Please have a look and send me your comments. > > Regards, > Roberto > > Peter Salomonsen wrote: > > On Monday 16 July 2007 06:55:16 you wrote: > >> I have started working on implementing the feature. I have created a new > >> servlet - XmlReportServelet. My idea is to be able to use the reporting > >> template mechanism that we have, but load report templates in XSLT > >> format. The results of a saved search would be represented in a fixed > >> defined XML format, for e.g.: > >> > >> <searchResults latest="true"> > >> <row> > >> <column name="id" >1</column> > >> <column name="airportName" >JFK</column> > >> <column name="latitude" >- 44.98</column> > >> <column name="longitude" >15.63</column> > >> <column name="altitude" >128</column> > >> <column name="windSpeed" >43</column> > >> </row> > >> <row> > >> <column name="id" >2</column> > >> <column name="airportName" >JFK</column> > >> <column name="latitude" >- 44.98</column> > >> <column name="longitude" >15.63</column> > >> <column name="altitude" >128</column> > >> <column name="windSpeed" >43</column> > >> </row> > >> </searchResults> > > > > This is a very good idea. Is this format compatible with the XML data > > source that you have in iReport? Eventually could you change it so that > > it would be compatible? > > > >> The new servlet would apply the XSL transformation to this XML and > >> return the result. It would receive the the template and search names > >> (unique IDs) as URL params for e.g.: > >> /xmlReport/Position.klm?template=Placemark&search=Vehicle1 > > > > XSL transformation is a good way of providing the kml. Actually I don't > > think you should implement this part then. Providing the xml is enough, > > and let external applications apply xsl templates for now. I think just > > providing the stored search as xml is sufficient for now - and we'll make > > the decision about also storing xml templates later. > > > >> This would ultimately allow us to have URLs that generate HTML reports, > >> RSS feeds etc. > > > > That is exactly what we want. > > > > Since we're now going for XMLDatasources would this eliminate the need > > for the DynamicBean? I see a problem with this regarding datatypes. The > > DynamicBean makes everything as strings, and this is e.g. a problem when > > sorting numbers in the report. > > > > With the xml datasource we wouldn't any longer have to use the csv for > > designing templates in iReport - right? > > > > Another thing - iReport has a possibility of viewing the report as Excel > > - could we use the same mechanism to send an excel file rather than pdf? > > > > regards, > > > > Peter |
|
From: Peter S. <co...@pe...> - 2007-07-23 07:25:44
|
Hi Roberto, Read inline comments. On 7/20/07, Roberto Milev <rob...@gm...> wrote: > > Hi Peter, > > Read comments inline. > > On 7/20/07, Peter Salomonsen <co...@pe...> wrote: > > > > Hi Roberto, > > > > The XML servlet is great, and it's much better to use in iReport. Did > > you > > manage to use the remote xml datasource? (I had some problems with it..) > > This > > would be even better. > > > I did not consider a remote xml datasource. Does this refer to loading > form URL? > Yes it's an iReport feature.. You can specify an xml datasource from a url. One downside with the xml datasource, is that the Report Wizard won't accept > > > > it. Is there a way around this? Suggestions? > > > Do you mean the report wizart inside the metalog applet? If yes, then this > is covered because xml datasources correspond to saved searches. > No, the report wizard in iReport. Somehow it doesn't seem to support xml datasources. No big deal though. About this: > > > > http://localhost:8080/lmas-addons-example/reportservlet?reportName=Report_1 > > > > > > It does always delete my report - and I know it's because of the "Print > > current report" function - but could we make it possible get an > > on-demand pdf > > without deleting? > > > > Further - in addition to pdf - could we also get an Excel doc - just > > like when > > using the excel preview function in iReport? > > > > Maybe introduce some switches? : > > > > http://localhost:8080/lmas-addons-example/reportservlet?reportName=Report_1&type=excel&delete=false > > > > (other types pdf, and the print current report could use delete=true) > > > yes the type and delete switches sound ok. > > And - regarding xsl transformation (to google kml's and other htmls) - any > > suggestions on how to solve this? Should we introduce xsl template > > uploading? > > We can use the reportservlet for also viewing xsl reports, the servlet > > will > > figure out if the template used is xsl? > > > I suggest we expand the report template table and add fields for content > type and file extension. For content type we would support: pdf, excel, xml > (xml would be used for xsl templates, and the file extension could be html, > klm, etc.). the xsl templates could be loaded in the same manner, > additionally the file extension should be specified on the upload page. I > see the foolwing possibilities for using the URL switches: > > -reportName > - type: pdf, excel, xml > - delete: true, false > > -searchName > - type: excel, xml > - template: (any saved template in the db) > - delete: true, false > > What do you think? > Sounds ok to me. cheers, Peter |
