Cannot add WebViewer of ActiveReports to an ASP.NET page - activereports

I installed ActiveReports from their site. The version was labeled as .NET 2.0 build 5.2.1013.2 (for Visual Studio 2005 and 2008). I have an ASP.NET project in VS 2008 which has 2.0 as target framework. I added all the tools in the DataDynamics namespace to the toolbox, created a new project, added a new report.
When I drag and drop the WebViewer control to a page in the design view, nothing happens. No mark up is added, no report viewer is displayed on the page. Also I noticed that there are no tags related to DataDynamics components in my web.config file. Am I missing some configuration?

I think I found the reason. While trying to get this work, I think I installed another version of the package that removed or deactivated my current version. The control I was dropping on the form belonged to the older version that had no assemblies referenced. I removed all installations of ActiveReports, installed the last version and cleaned up the toolbox. I added the latest version of the WebViewer to toolbox and dropped it on the form. It worked.

Related

Where can I get Zest 2.0 eclipse plugin

I was trying to get Zest 2.0 for Eclipse marketplace but found nothing.
Then I tried to download it manually through GEF4, however it seems that there are only 1.x versions of Zest.
How can I install Zest 2.0 properly?
The version history of Zest is not entirely clear, but I try to tell what happened there:
The original versions (Zest 1.x) were developed by Ian Bull, that was included in the GEF project, but was developed mostly separately.
GEF 2.0 started as a Google Summer of Code project in 2009 (IIRC), and a lot of new features and bugfixes were implemented over the 1.x branch, but they were never ported back to the release train.
Then GEF4 started as a new approach where the entire inner behaviour of GEF was changed, and in 2014 the Zest 2.0 components were migrated to use the new GEF4 codebase, using a 0.1.0 version number.
In June 2016 this was released as GEF4 Zest 1.0.
In other words, components called Zest 2.0 are not available in any standalone release. If you want to rely on them, you can do one of the following:
Use Zest 1.x components available from the GEF legacy release update site: http://download.eclipse.org/tools/gef/updates/legacy/releases/ If you have an existing Zest-based tool, these versions should be easy to migrate to.
Migrate to GEF4 Zest available from current release site http://download.eclipse.org/tools/gef/updates/releases/ If you plan to start a new project, most likely this is the most promising candidate; similarly, this is the version that is planned to be maintained long-term, so this migration might become necessary sooner or later.
Click on help menu / install new software, click on add button to add new update site. The update site can be found here. In your case that might be this: http://download.eclipse.org/tools/gef/gef4/updates/releases. You should see this:
Install it. Or you may be able to install it using local update site (not tried) found here: https://www.eclipse.org/gef/downloads/index.php.

how to upload jrxml file in jaspersoft studio? sftp

After editing a jaspersoft template in Studio version 6.0.3 is it possible to export or upload the jrxml file to my server via sftp directly from JasperSoft Studio?
Currently after edits are made and saved I have to go to the ftp client to upload files.
you could try to use Eclipse RSE installing the dedicated feature. It's possible from Jaspersoft Studio. You simply need to add the update site for it.
I would suggest you use Indigo one, because the Juno (dedicated to 4.2.x) may screw up UI and other JSS capabilities.
Even if the Eclipse 3.8.2 version, the platform used by JSS product, is referred as Juno, it can be more like a bug-fix version of Indigo 3.7.x.
So you could add the Indigo update site: http://download.eclipse.org/releases/indigo/
Later you can select the feature "Remote System Explorer End-User Runtime", install it and you are free to try if it suits your needs.
See screenshot below:
Personally I simply installed, but I didn't play with it.
Anyhow I suggest you to also give a look to the following blog post: http://rays-blog.de/2012/05/05/94/use-winscp-to-upload-files-using-eclipses-autobuild-feature/
Maybe it's better to set-up a custom script, like this user did because not completely satisfied of the Eclipse-like solutions.
It's worth mentioning also this one: http://www.jcraft.com/eclipse-sftp/
In my case it didn't work even if installation appeared to have completed successfully. Maybe it's too old for the latest Eclipse versions.
Regards,
Massimo.

How do I get my new BIRT 4.3.1 to use the use the same project and workspace for everything I built in 4.2.1?

All of the following is done in a cloned development (VM) server, so there is no risk to my production environments (prd04 for completed reports, tst04 for creation and problem solving, working on clone of tst04 now).
I have been using BIRT 4.2.1 for a about a year, I have several reports and most importantly a library that were created with 4.2.1. While the production reports actually run via Apache, I have downloaded and updated the "runtime" files so any new reports will run ok, but this made 95% of the old reports stop working. It does not make sense to try and “fix” them with 4.2.1 if I am going to be running 4.3.1 now. I expect the problem to be fixed with a library correction related to jar or war file.
I want to use my fresh download of 4.3.1 in the same workspace and with the same project as I used for 4.2.1. But I am days into trying to make it work and no luck.
Failures
Tried to upgrade the existing 4.2.1 to 4.3.1 but never got it to work correctly
Ended up downloading a fresh copy, so now I have two instances of BIRT (one of each)
Used the existing 4.2.1 workspace for 4.3.1 C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\Birt
Brought in the Navigator View, but am unable to make it “see” the existing reports and projects
Project > Open Project will not work, “Open Project” is greyed out. If I create a new project “open project” and “close project” works but still can’t “see” my existing project
Open an existing report and try to “save as” in the workspace, but it can’t see …Tomcat 7.0\webapps\Birt
Try to drag (project, library, report) and drop from Resources to Navigator Does not work
Try to drag (project, library, report) and drop from the Window file to Navigator Does not work
Looked into “CVS Repositories” but at first glance it does not seem to be the correct path.
Tried a bunch of other things, but they did not work and were not as promising as the above.
It is starting to feel like I only have two options left;
Create a separate Apache instance for running any new 4.3.1 reports, leaving all the existing reports running on Apache with the 4.2.1 “runtime" files
Create a new project for 4.3.1 and one by one rebuild existing reports, once I have everything working upgrade my production Apache and redeploy all the updated reports.
Screen shot of invisible workspace
Your wrote: I have downloaded and updated the "runtime" files so any new reports will run ok, but this made 95% of the old reports stop working.
What exactly do you mean? Error messages? Hangs? Crashes? OutOfMemoryError?
If it's OOM you probably hit a "feature" introduced in 4.2.2 regarding Default Row Fetch Size (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=407299).
Apart from that, I don't see a reason why any report created with 4.2.1 should not run with 4.3.
And just to clarify: Are you using an Eclipse IDE as a kind of "BIRT Reports Server" somehow? To be honest, that sounds crazy.
We are also using a custom plugin. This was developed with BIRT 3.7.1 and runs on 3.7.1, 4.2.1 and 4.3 without any problems.
The same is true for the BIRT runtime Environment (bunch of JARs, no OSGI). We are not using Apache Tomcat (instead we developed a "BIRT Reports Server").
It should be possible to update the Tomcat Server by just replacing the 4.2.1 JARs with 4.3 JARs and setting the classpath accordingly.

upgrade gwt 1.7 to gwt 2.5

Our project uses gwt 1.7 and jdk 1.5.0_13.
We need to add support for IE9 and above.
For that, we need to upgrade gwt to latest version (2.5) and, therefore, upgrade jdk as well.
While doing so, we are getting errors related to missing source codes in gwt jars (e.g. TimeOutException source code not found).
We have simply replaced the gwt 1.7 jars with latest ones. What else do we need to change?
Is there any guide explaining the migration procedure for gwt?
AFAIK there isn't any detailed guide explaining the migration. In the documentation project you have only a brief list of features and breaking changes for each version, it is very useful though.
You have many posts with the experience of users migrating from 1.7 to 2.0, but almost very old since 2.0 was released some years ago. There is very little info for migrations from 1.7 to the the last 2.5.
Said that, the main problem you will deal with is the change in the tools for dev and debug, so I recommend first to get used with these tools. Then you have to fix each single 'red' mark in your IDE project. Then you should look for 'yellow' marks in order to avoid using deprecated classes/methods. Finally you could consider replacing some code of your project with new features in 2.x like cell-widgets, layout-panels, etc, see the showcase.
The process will be tedious, but it is worth to have your project using last releases if you plan to maintain the application in the future.
BTW, there are plans to remove support for IE6, IE8 and even IE9 in future versions of GWT, in order to improve and modernize gwt and to support new html5 features. It will be gradual though: Solutions for people needing IE7/IE8 support in future GWT releases
I updated from 2.2 -2.5 yesterday and had 2 errors I had to overcome.
Jar file was for 2.2- I deleted it, switched to non GWT toolkit, and switched back. This updated(created) to correct jar.
source code problem- for some reason the run config was not transferred correctly. Since i had used a new workspace when updating i copied over the old path to the new workspace. (this was located under: Debug config--> Arguments--> Program arguments
Hope this helps :)

Eclipse EGit and GWT/GAE

I have a central GIT repository, so that i can work on the project from different computers.
However when i pull the project on the other computer i get the error "Unbound classpath container: 'GWT SDK [missing]' in project 'Test Project'" (I also get a similar error for GAE).
So my question is: How do i setup my project so the same version of GAE/GWT is used on all computers.
I suspect the problem could be caused by the different versions of GAE and GWT on the machines. For example: GWT (1) is not the same version on the machines as it depends on when you updated GWT.
I ran into this problem too, and solved it by installing the GAE and GWT sdks under specific names, manually. That is, instead of relying on eclipse's software update tools, I downloaded the specific SDK version I wanted from the googlecode sites, and then added them manually to eclipse. This way their names include the numbers, and your git repository can store information about which versions it's using.
I do have to install the sdks manually on each developer machine, which is a drag.
To install an sdk manually:
Download it
Right-click on the sdk container in eclipse (in project explorer, it probably says GWT SDK [missing])
Choose properties
Click configure SDKs
follow the path to install a new sdk
You don't have to set the new sdk as default or anything - your project will pick it up immediately after you install it.
Note to any GPE developers: it'd be nice if the sdks were installed automatically with a version-specific name for the benefit of source control!
You can Change the project's SDK target.
In eclipse go to Marker [it is a tab next on the extreme left of the tabs including Console and Development] --> Left Click problem indication --> Click Quick fixes and choose the option which re-configures the project. This should fix the problem. Note that if your code uses features that changed between SDK versions you will have to make changes.
Combined with Rilev Lark's answer This is a chance to Update your projects or your environments whenever the problem occurs.