whitemarlin

Thank you. And now, can the JasperJPivot source for CE 4.5.0 be made available as well?

That seems to be the JasperServer source, not the JasperJPivot source. Post Edited by whitemarlin at 05/10/2012 16:36

Oh, we'll be moving to 4.1. Just not right now! :-) BTW, in your copious free time, check out a couple of patches I've submitted. You can get to them by starting at these URLs: http://jasperforge.org/projects/jasperserver/tracker/view.php?id=5445 http://jasperforge.org/projects/jasperserver/tracker/view.php?id=5446

I've resolved that issue too. The solution was to go into maven-settings.xml and copy/paste the jasperserver-repo repository as a pluginRepository. I can now build with Maven 3.0.3 again. You might like to try these changes at some convenient time, so you're not limited to Maven 2.2.1 anymore. I don't fully understand why my Maven 3.0.3 builds used to work. My hypothesis is that I DID at one time build with Maven 2.2.1, and perhaps that put my local repository in a state that Maven 3.0.3 could use. I know of one other project in which that was the case. I am a little embarrassed. I found notes I wrote back on September 14 in which I said, "The Jasper folks say to use 2.2.1; I use 3.0.3 and it seems to work." So perhaps I should just go back to using 2.2.1. Thanks for all your help.

Belay that. I've resolved that issue. The key was in the error message "'parent.relativePath' points at wrong local POM". Apparently this was only a warning in Maven 2 but is an error in Maven 3. I believe the parent is specified incorrectly in two files: jasperserver-api-impl/common/pom.xml jasperserver-api-impl/engine/pom.xml On line 10 of these files, the parent artifactId is specified as 'jasperserver-api'. I believe it should be 'jasperserver-api-impl'. Now I am on to the next error: [exec] [iNFO] Jasper Server API Implementations - Metadata ...... FAILURE [11.142s] ... [exec] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run (Instrument domain classes) on project jasperserver-api-metadata-impl: Execution Instrument domain classes of goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run failed: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies could not be resolved: Could not find artifact org.hibernate:hibernate-core:jar:3.3.2.GA-HHH-2763 in codehaus-plugins (http://dist.codehaus.org/)

Thanks so much, Tony. That's good information. I do use Maven 3.0.3, and I've heard reports of projects that can build from an empty repository with Maven 2 but not Maven 3. I don't suppose you'd like to repeat the experiment with 3.0.3... FYI, when I comment out the ref to the old repository, I get error messages that are similar but different--messages like [exec] [ERROR] Non-resolvable parent POM: Could not find artifact com.jaspersoft.jasperserver:jasperserver-api:pom:3.7.0 in js-repo-svn (file://<local path omitted>/jasperserver-ce-3.7.0-src/jasperserver-repo) and 'parent.relativePath' points at wrong local POM @ line 8, column 11 -> [Help 2] In the meantime, yes, I'd appreciate it if you could upload your zipped repository. Also your maven_settings.xml. Thanks, Wes

Sorry, I just now got time to get back to this. I truly appreciate your taking the time to work with me. Two things: First, I was not complete in my description of my build process. In between unzipping the file and running the ant build-ce command, I apply a patch that has the effect of doing all the preparatory steps you mention. This is so I can have a fully scriptable, "turn-key" build process. Second, and most important, THIS PROCESS WORKED UNTIL A FEW WEEKS AGO, when it began failing with the error messages about being unable to contact the deprecated repository. So I conclude that the build process requires some resources that were located on the deprecated repository and that are now inaccessible. What is necessary, it seems to me, is to identify those resources, make them available on some other repository, and change the build process to refer to the new repository instead. I am fairly confident that I can do the last part (change the build process to refer to the new repository). What I can't do is the first part (identify the resources and make them available elsewhere). That is what I need you to do. I am also fairly confident that if YOU try the 3.7 build from the distributed zip file (preferably starting with a fresh local repository), then you will encounter the same problem. Does that make sense? Thanks again.

Thanks for the response. Well, I don't -think- there is confusion, and no, I can't use the current source. We are using 3.7. But the 3.7 distribution has been unbuildable for weeks, as far as I can tell. Do you agree or disagree? If you agree, do you think the 3.7 distribution will ever be buildable again, or is that version essentially dead? If I unzip the jasperserver-ce-3.7.0-src.zip file, cd into jasperserver-ce-3.7.0-src/jasperserver/buildomatic, and run 'ant -lib install_resources/extra-jars build-ce', I get these errors in the build-ce target: The project com.jaspersoft.jasperserver.api.common.impl:jasperserver-api-common-impl:3.7.0 (.../jasperserver-ce-3.7.0-src/jasperserver/jasperserver-api-impl/common/pom.xml) has 1 error Non-resolvable parent POM: Could not transfer artifact com.jaspersoft.jasperserver:jasperserver-api:pom:3.7.0 from/to JBoss (http://repository.jboss.org/maven2): Access denied to: http://repository.jboss.org/maven2/com/jaspersoft/jasperserver/jasperserver-api/3.7.0/jasperserver-api-3.7.0.pom and 'parent.relativePath' points at wrong local POM @ line 8, column 11 The project com.jaspersoft.jasperserver.api.engine.impl:jasperserver-api-engine-impl:3.7.0 (.../jasperserver-ce-3.7.0-src/jasperserver/jasperserver-api-impl/engine/pom.xml) has 1 error Non-resolvable parent POM: Could not transfer artifact com.jaspersoft.jasperserver:jasperserver-api:pom:3.7.0 from/to JBoss (http://repository.jboss.org/maven2): Access denied to: http://repository.jboss.org/maven2/com/jaspersoft/jasperserver/jasperserver-api/3.7.0/jasperserver-api-3.7.0.pom and 'parent.relativePath' points at wrong local POM @ line 8, column 11 Should I be building some other way? I just got your latest post while I was composing this one. I have not tried the "-o" option. But since I blew away the Jasper portion of my local repository when the error began happening a couple of weeks ago, I doubt very much that that will work. Regardless, I can't base a general build process for the company on what happens to be in the local repository on one machine. If you can do anything to make jasperserver-ce-3.7.0-src.zip be buildable again, or tell me if I'm doing anything wrong, I would much appreciate it! Again, this used to work, and now it doesn't. Thanks!

Any more news on this, tkavanagh? Thanks in advance.

Thanks, tkavanagh. Should this be working now? I have not located your modified maven_settings.xml. In mine, I made this change: 56c56 < <url>http://repository.jboss.org/maven2</url> --- > <url>https://repository.jboss.org/nexus/content/groups/public</url> and it still doesn't work. (I didn't think it would, since as you say the new repository has been reorganized--it doesn't look like Jasper is even there.)

A couple of weeks ago I could build 3.7 from source. Now I can't. I'm getting error messages like Access denied to: http://repository.jboss.org/maven2/com/jaspersoft/jasperserver/jasperserver-api/3.7.0/jasperserver-api-3.7.0.pom and 'parent.relativePath' points at wrong local POM @ line 8, column 11 I suspect this is due to a recent change in access to the deprecated repository at http://repository.jboss.org/maven2. I've posted a request for help at http://community.jboss.org/wiki/JBossDeprecatedRepository#comment-7761 but received no reply. Can you help? Please? This is a showstopper.

Is it possible to create an analysis view via a web service?

I created http://jasperforge.org/projects/jasperserver/tracker/view.php?id=5446 to track this issue.

I created http://jasperforge.org/projects/jasperserver/tracker/view.php?id=5445 to track this issue.

tkavanagh Wrote: Shoot, I downloaded and looked. And I see the same issue that the apache-ant folder is not there. It should be there so I'll have to fix this. In the meantime, you *can* use your own copy of apache-ant. Make sure it is version 1.7.1 or better. Then you will also need to copy the ant-contrib-<ver>.jar into your apache-ant/lib folder. The buildomatic scripts rely on the ant-contrib conditional logic capability. You can grab the ant-contrib.jar from the 3.5.0 src package. Hi! Do you still intend to add apache-ant to jasperserver-ce-3.7.0-src.zip? Thanks!

It does appear to work, assuming the patch in my post http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=91764 is applied. The child ResourceDescriptors must be defined as references, by for example rd.setWsType(wsType); // needed? rd.setReferenceUri(uri); rd.setIsReference(true); Attached is the patch that makes the MondrianConnectionHandler changes mentioned above.

I believe there is a bug in 3.7.0 and 4.1.0 (at least) preventing successful creation of a Mondrian schema through a web service call. The file applicationContext-web-services.xml appears to list the file types for which FileResourceHandler will be used (along with other handlers). The last entry (a late addition?) is 'olapMondrianSchema', also known as ResourceDescriptor.TYPE_MONDRIAN_SCHEMA. But FileResourceHandler does not deal with this file type; it deals with all the others listed in applicationContext-web-services.xml, but not this one. (It also deals with 'xml', which is not listed--that may be another bug.) The result of this omission appears to be that if a Mondrian schema is created through a web service call, the corresponding row in the JIFileResource table has its file_type column set to null, which causes problems downstream. I believe the attached patch fixes this bug.

I concluded that the 'right' way to do this was to set the ResourceDescriptors for the OLAP schema and the data source as children of the ResourceDescriptor for the client connection. But this was unsuccessful: the client connection was created, but its OLAP schema (at least) was null. I believe this is because MondrianConnectionHandler.updateResource, unlike for example QueryHandler.updateResource and ReportUnitHandler.updateResource, does not look for children of the ResourceDescriptor. (In fact, it does absolutely nothing.) This appears to be still true in 4.1.0. Do I have any recourse other than patching MondrianConnectionHandler.updateResource (and MondrianConnectionHandler.doDescribe) to be cognizant of child ResourceDescriptors? And would that even work? I would appreciate any help. Post Edited by whitemarlin at 09/12/2011 06:59

I'm trying to replace a manual process by a programmatic process. The process is creating an "analysis client connection". Manually, it is done by steps similar to the following (copied from an internal doc):. a. Add Resource/Other/Analysis Client Connection b. Select “Mondrian Connection” c. Enter the connection Name and Label. Use the same value for Name and Label. Do not enter a description. Next. d. Locate the OLAP schema from the repository. Select the schema that you created above. e. Next. Next. (no changes required on the next screen). f. Locate the data source “From the Repository.” Select the data source that you created above. g. Next. Save. I am trying to use the putResource(ResourceDescriptor, RequestAttachment[]) method in com.jaspersoft.jasperserver.irplugin.wsclient.WSClient. But I don't know how to specify the OLAP schema and the data source in the ResourceDescriptor. I've looked for examples, docs, forum posts, etc., and have not found anything helpful. Can you help? Thank you.