Re: [Dspace-tech] DSpace/Maven help request - update dependency version
Thanks, Tim. That helped me to understand. I put the version numbers of the
dependency in the parent pom.xml ('dspace-src/pom.xml') and left the version
numbers out of 'dspace-src/dspace-api/pom.xml'.
So then I found another thing I didn't look at closely enough. The WordFilter
doesn't use poi directly, but the org.textmining project that it uses depends
on that old version of POI. To confuse things more, the old versions of poi
had groupId 'poi', and the new versions have groupId 'org.apache.poi'.
I can convince Maven to forget about the old version of the POIi library by
making this exclusion change in the parent pom:
dependency
groupIdorg.textmining/groupId
artifactIdtm-extractors/artifactId
version0.4/version
exclusions
exclusion
groupIdpoi/groupId
artifactIdpoi/artifactId
/exclusion
/exclusions
/dependency
dependency
Then only the new version, org.apache.poi/poi/3.6 is included in the project.
Unfortunately, the org.textmining extractors really do need that version of
POI. The PowerPointFilter works, but I've broken the WordFilter:
Exception:
org.apache.poi.poifs.filesystem.POIFSFileSystem.getRoot()Lorg/apache/poi/poifs/filesystem/DirectoryEntry;
java.lang.NoSuchMethodError:
org.apache.poi.poifs.filesystem.POIFSFileSystem.getRoot()Lorg/apache/poi/poifs/filesystem/DirectoryEntry;
at
org.textmining.text.extraction.WordExtractor.extractText(WordExtractor.java:51)
at
org.dspace.app.mediafilter.WordFilter.getDestinationStream(WordFilter.java:95)
I have two programs that share the same classpath, but need different versions
of the same library.
I could rewrite the WordFilter so that it no longer uses the org.textmining
package which needs the old library, but I keep thinking that the more I try to
fix stuff, the more I'm likely to break:
http://www.nypost.com/p/news/local/brooklyn/rat_bastards_f5onjzgcqxm0fu3RFz3ySL
On Oct 5, 2010, at 4:09 PM, Tim Donohue wrote:
Hi Keith,
Simply put, it's because you were accidentally looking in the wrong pom.xml
:) There's many of them sprinkled through the DSpace codebase, and they all
inherit many of their settings from one main pom.xml.
So, you noticed that the 'dspace-api/pom.xml' file included a dependency for
poi. But, if you look closely, that dependency doesn't list a version.
This is because, for DSpace, we manage all the versions of dependencies in
one parent pom.xml (which is loaded via the parent tag within the
dspace-aip/pom.xml).
Now, take a look at the [dspace-src]/pom.xml. This is the main Parent pom.xml
for dspace (with an artifactid of 'dspace-parent')
http://scm.dspace.org/svn/repo/dspace/trunk/pom.xml
This is the pom.xml which actually lists the versions of every dependency
used by the various APIs of DSpace. If you search in this pom.xml, you'll
find this entry:
dependency
groupIdpoi/groupId
artifactIdpoi/artifactId
version2.5.1-final-20040804/version
/dependency
That's where the 2.5.1 version is sneaking in. If you make your necessary
changes to this pom.xml, everything should act as you expect it to. So, just
undo your changes in 'dspace-src/dspace-api/pom.xml', and instead make those
changes to 'dspace-src/pom.xml'
I hope that helps!
- Tim
On 10/5/2010 2:36 PM, Keith Gilbertson wrote:
Hi,
I've been experimenting with a Media Filter for text extraction from
PowerPoint files. It's based on the Apache POI libraries, as was suggested
by others in a previous thread.
It uses the poi, poi-scratchpad, and poi-ooxml artifacts, in version 3.6,
the latest release version from Apache. I haven't done much with Maven, and
am not sure how to tell it which libraries I need.
This bit was already in the dspace-api/pom.xml file:
dependency
-groupIdpoi/groupId
-artifactIdpoi/artifactId
-/dependency
I removed it, because I wanted the latest version of the libraries. Then, I
added these dependencies to the bottom of the file:
+dependency
+groupIdorg.apache.poi/groupId
+artifactIdpoi/artifactId
+version3.6/version
+/dependency
+dependency
+groupIdorg.apache.poi/groupId
+artifactIdpoi-scratchpad/artifactId
+version3.6/version
+/dependency
+dependency
+groupIdorg.apache.poi/groupId
+artifactIdpoi-ooxml/artifactId
+version3.6/version
+/dependency
Somehow Maven magically found the correct versions of the dependencies, and
everything built fine. When I deployed DSpace and looked in the lib
directory, there were two versions of the main poi library there:
poi-2.5.1-final-20040804.jar
poi-3.6.jar
poi-ooxml-3.6.jar
poi-ooxml-schemas-3.6.jar
poi-scratchpad-3.6.jar
I couldn't figure out why the poi-2.5.1 version was still there, or find
anything that actually used it. So, in the interest of doing some quick
testing, I just deleted
[Dspace-tech] [Fwd: Dspace Technical Workshop Tanzania]
Original Message Subject: Dspace Technical Workshop Tanzania From:Paul Samwel Muneja pmun...@udsm.ac.tz Date:Wed, October 6, 2010 1:43 pm To: dspace-tech@lists.sourceforge.net -- Dear all, I am looking for a facilitor for Dspace Technical Workshop in Tanzania which will be held at the end of December or early January. The objective of this workshop is to empower our IT guys to understand on how to install and to configure Dspace Software.If you feel you can assist please reply this e-mail for further communication. Regards, Paul Paul S. Muneja Assist.Lecturer and Librarian University of Dar es salaam pmun...@libis.udsm.ac.tz or pmun...@yahoo.com Tel: +255 713798947 Paul S. Muneja Assist.Lecturer and Librarian University of Dar es salaam pmun...@libis.udsm.ac.tz or pmun...@yahoo.com Tel: +255 713798947 _ University Computing Centre - 'Professionalism, Customer Care and Technological foresight' -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] tomcat reporting memory leak?
On 5 October 2010 16:33, Simon Brown st...@cam.ac.uk wrote: Which nobody has requested, making this a massive red herring. I fail to see how cutting back on unnecessary and redundant database access constitutes overhead to cover up the problems of larger repositories. One person's unnecessary and redundant database access is another's very necessary database access - well, at least it can be. I remember the patch for reducing the updating of browse / search indexes, and I can see why it would be useful to not do those updates during a batch import if you have an appropriate workflow. That won't be the case for all of the repositories - quite a few will welcome the ability to see those items as and when they are added. There is also the issue of how long it takes to do the one very big update at the end of the batch run vs. incremental changes as you go - it may be less work overall, but having one big change can be more disruptive in some cases. Any repository, regardless of size, will see improvements with this kind of optimisation, at least one example of which I have already highlighted (and had my arguments shouted down - this is also, incidentally, why I haven't bothered to open any other JIRA tickets on other performance issues we've seen. What would be the point?) No, you didn't get shouted down for raising a performance issue. Where the argument came was because you assumed that this would clearly be of benefit to any repository, when you did nothing to address the underlying performance issues (which could have been helped quite dramatically with some small SQL tweaks and some configuration work in Postgres), and instead just bypassed them for one very specific use case. It doesn't matter how large or small a repository is, if they don't perform batch uploads using the ItemImporter, your change will do *nothing* for them. But an alteration to the underlying SQL, and guidelines for getting the best out of Postgres would benefit everyone - regardless of how large or small the repository is, or the means by which they populate it. The pertinent question for me is why, whenever the issue of performance comes up, is one of these theoretical future of repositories screeds pulled out and slammed down in front of the conversation? People are reporting problems with the systems they have *right now*. It's not meant to be a barrier to conversation, but a question as to what you want to resolve. Do you want to address the *scalability* of DSpace, or do you just want to avoid an immediate performance bottleneck? If we conflate these, conversations are going to stall, and we're not going to make any progress. Or rather, they were. And yes, it is true that there is a finite limit to what the hardware is capable of, but the quality of the software plays a significant role in how quickly that limit is reached. But we've had this conversation before. I don't really expect it to end any better this time than it did then. I completely agree - but a solution that breaks the encapsulation of the components in the system, and leaves important indexes in an inconsistent state for an extended period of time is not an automatic win for the majority of the community. I offered a lot of suggestions as to how that code could be better structured, improvements both to the SQL and the configuration of Postgres to handle the load more efficiently, and suggestions for further tweaks that would reduce the amount of updates that the code would have needed to do still further. All of which would have be more beneficial to the community (not just improving batch uploads, but interactive / singular deposits and edits) - and not only that, would have improved the performance of your systems further than you had so far achieved. Any method of increasing the processing capabilities of a system, either through more powerful hardware or improvements in the software, is postponing the inevitable for any repository with continued growth. The difference is in how much cost there is to any individual repository in each of those methods. Our system, with the changes we've made to it, struggles at around 300,000 items. People are reporting problems (presumably running stock 1.6.2) at around 50,000, from what I can gather. This is where we need to be careful about what we are reporting. Quite a few of the issues around 1.6.x appear to be around rampant memory usage, rather than a clear function of how many records there are in the database. There are also different issues involved if we are talking about adding / editing lots of records, or simply highly accessed. Even so, regardless of what we do to the code to make it efficient, it does not and can not absolve the system administrator of correctly maintaining both DSpace itself, and it's dependencies. I wouldn't want to get drawn on where that point is without any evidence, but there is a lot of scope for altering and improving Postgres
Re: [Dspace-tech] A simplified version of dspace-services and Tomcat unloading
On 5 October 2010 19:17, Sands Alden Fish sa...@mit.edu wrote: What resources were leaking here exactly? Leaking resources across requests can have some serious consequences depending on the resources, and I'm curious to know exactly what type of errant behavior we could expect from a 1.6.x version running the flawed services framework. I would say that the ability to leak resource across requests is more theoretical than demonstrated in a real world scenario. By which I mean that it's clearly demonstrated that the Caching service has the ability to store data either at the wrong scope, or to have request scope caches that actually get bound / re-bound to a later, different, request - however, I haven't exercised a full DSpace application in such a way to observe this happening. But even if the application wouldn't normally run into an issue, that doesn't mean we shouldn't tighten up it's behaviour to prevent it from becoming an issue later. G -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Dspace workflow problem
Good Day we have a problem with the work flow this is how we have created it Accept/Reject/Edit Metadata Step --COLLECTION_21_WORKFLOW_STEP_2 Edit Metadata Step -- COLLECTION_21_WORKFLOW_STEP_3 Submitters --- COLLECTION_21_SUBMIT now the problem is that from the submitter step the document goes straight to the Accept/Reject/Edit Metadata Step but we want it to go through the Edit Metadata Step before the Accept/Reject/Edit Metadata Step. how can we change the work to work accordingly. regards Tumie -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace/Maven help request - update dependency version
Ugh -- sounds like you've entered dependency hell.
Though, I think the one shred of good news here is that it seems to only
have a dependency conflict in one place in our codebase.
It looks like (at a glance) if our WordFilter can be re-written to no
longer need the org.textmining project, you *might* be OK (i.e.
hopefully it wouldn't snowball on you). But, that would require finding
a Word document text extractor that is as good as (or better than) that
'org.textmining' one, and then hoping it doesn't cause another
dependency conflict. Not sure of any alternative Word text extractors,
off the top of my head, but maybe others know of one?
- Tim
On 10/6/2010 5:51 AM, Keith Gilbertson wrote:
Thanks, Tim. That helped me to understand. I put the version numbers of the
dependency in the parent pom.xml ('dspace-src/pom.xml') and left the version
numbers out of 'dspace-src/dspace-api/pom.xml'.
So then I found another thing I didn't look at closely enough. The
WordFilter doesn't use poi directly, but the org.textmining project that it
uses depends on that old version of POI. To confuse things more, the old
versions of poi had groupId 'poi', and the new versions have groupId
'org.apache.poi'.
I can convince Maven to forget about the old version of the POIi library by
making this exclusion change in the parent pom:
dependency
groupIdorg.textmining/groupId
artifactIdtm-extractors/artifactId
version0.4/version
exclusions
exclusion
groupIdpoi/groupId
artifactIdpoi/artifactId
/exclusion
/exclusions
/dependency
dependency
Then only the new version, org.apache.poi/poi/3.6 is included in the project.
Unfortunately, the org.textmining extractors really do need that version of
POI. The PowerPointFilter works, but I've broken the WordFilter:
Exception:
org.apache.poi.poifs.filesystem.POIFSFileSystem.getRoot()Lorg/apache/poi/poifs/filesystem/DirectoryEntry;
java.lang.NoSuchMethodError:
org.apache.poi.poifs.filesystem.POIFSFileSystem.getRoot()Lorg/apache/poi/poifs/filesystem/DirectoryEntry;
at
org.textmining.text.extraction.WordExtractor.extractText(WordExtractor.java:51)
at
org.dspace.app.mediafilter.WordFilter.getDestinationStream(WordFilter.java:95)
I have two programs that share the same classpath, but need different
versions of the same library.
I could rewrite the WordFilter so that it no longer uses the org.textmining
package which needs the old library, but I keep thinking that the more I try
to fix stuff, the more I'm likely to break:
http://www.nypost.com/p/news/local/brooklyn/rat_bastards_f5onjzgcqxm0fu3RFz3ySL
On Oct 5, 2010, at 4:09 PM, Tim Donohue wrote:
Hi Keith,
Simply put, it's because you were accidentally looking in the wrong pom.xml
:) There's many of them sprinkled through the DSpace codebase, and they all
inherit many of their settings from one main pom.xml.
So, you noticed that the 'dspace-api/pom.xml' file included a dependency for
poi. But, if you look closely, that dependency doesn't list aversion.
This is because, for DSpace, we manage all the versions of dependencies in
one parent pom.xml (which is loaded via theparent tag within the
dspace-aip/pom.xml).
Now, take a look at the [dspace-src]/pom.xml. This is the main Parent
pom.xml for dspace (with an artifactid of 'dspace-parent')
http://scm.dspace.org/svn/repo/dspace/trunk/pom.xml
This is the pom.xml which actually lists the versions of every dependency
used by the various APIs of DSpace. If you search in this pom.xml, you'll
find this entry:
dependency
groupIdpoi/groupId
artifactIdpoi/artifactId
version2.5.1-final-20040804/version
/dependency
That's where the 2.5.1 version is sneaking in. If you make your necessary
changes to this pom.xml, everything should act as you expect it to. So, just
undo your changes in 'dspace-src/dspace-api/pom.xml', and instead make those
changes to 'dspace-src/pom.xml'
I hope that helps!
- Tim
On 10/5/2010 2:36 PM, Keith Gilbertson wrote:
Hi,
I've been experimenting with a Media Filter for text extraction from
PowerPoint files. It's based on the Apache POI libraries, as was suggested
by others in a previous thread.
It uses the poi, poi-scratchpad, and poi-ooxml artifacts, in version 3.6,
the latest release version from Apache. I haven't done much with Maven,
and am not sure how to tell it which libraries I need.
This bit was already in the dspace-api/pom.xml file:
dependency
-groupIdpoi/groupId
-artifactIdpoi/artifactId
-/dependency
I removed it, because I wanted the latest version of the libraries. Then,
I added these dependencies to the bottom of the file:
+dependency
+groupIdorg.apache.poi/groupId
+artifactIdpoi/artifactId
+version3.6/version
Re: [Dspace-tech] DSpace/Maven help request - update dependency version
That version of tm-extractors is quite old.
There is a newer version on the Google site -
http://code.google.com/p/text-mining/ - but it will take a bit of work
wrapping things up for general use.
It has dependencies on newer versions of POI than 0.4, and some distinct
improvements to it's robustness.
G
On 6 October 2010 16:39, Tim Donohue tdono...@duraspace.org wrote:
Ugh -- sounds like you've entered dependency hell.
Though, I think the one shred of good news here is that it seems to only
have a dependency conflict in one place in our codebase.
It looks like (at a glance) if our WordFilter can be re-written to no
longer need the org.textmining project, you *might* be OK (i.e.
hopefully it wouldn't snowball on you). But, that would require finding
a Word document text extractor that is as good as (or better than) that
'org.textmining' one, and then hoping it doesn't cause another
dependency conflict. Not sure of any alternative Word text extractors,
off the top of my head, but maybe others know of one?
- Tim
On 10/6/2010 5:51 AM, Keith Gilbertson wrote:
Thanks, Tim. That helped me to understand. I put the version numbers of
the dependency in the parent pom.xml ('dspace-src/pom.xml') and left the
version numbers out of 'dspace-src/dspace-api/pom.xml'.
So then I found another thing I didn't look at closely enough. The
WordFilter doesn't use poi directly, but the org.textmining project that it
uses depends on that old version of POI. To confuse things more, the old
versions of poi had groupId 'poi', and the new versions have groupId
'org.apache.poi'.
I can convince Maven to forget about the old version of the POIi library
by making this exclusion change in the parent pom:
dependency
groupIdorg.textmining/groupId
artifactIdtm-extractors/artifactId
version0.4/version
exclusions
exclusion
groupIdpoi/groupId
artifactIdpoi/artifactId
/exclusion
/exclusions
/dependency
dependency
Then only the new version, org.apache.poi/poi/3.6 is included in the
project. Unfortunately, the org.textmining extractors really do need that
version of POI. The PowerPointFilter works, but I've broken the WordFilter:
Exception:
org.apache.poi.poifs.filesystem.POIFSFileSystem.getRoot()Lorg/apache/poi/poifs/filesystem/DirectoryEntry;
java.lang.NoSuchMethodError:
org.apache.poi.poifs.filesystem.POIFSFileSystem.getRoot()Lorg/apache/poi/poifs/filesystem/DirectoryEntry;
at
org.textmining.text.extraction.WordExtractor.extractText(WordExtractor.java:51)
at
org.dspace.app.mediafilter.WordFilter.getDestinationStream(WordFilter.java:95)
I have two programs that share the same classpath, but need different
versions of the same library.
I could rewrite the WordFilter so that it no longer uses the
org.textmining package which needs the old library, but I keep thinking that
the more I try to fix stuff, the more I'm likely to break:
http://www.nypost.com/p/news/local/brooklyn/rat_bastards_f5onjzgcqxm0fu3RFz3ySL
On Oct 5, 2010, at 4:09 PM, Tim Donohue wrote:
Hi Keith,
Simply put, it's because you were accidentally looking in the wrong
pom.xml :) There's many of them sprinkled through the DSpace codebase, and
they all inherit many of their settings from one main pom.xml.
So, you noticed that the 'dspace-api/pom.xml' file included a dependency
for poi. But, if you look closely, that dependency doesn't list
aversion. This is because, for DSpace, we manage all the versions of
dependencies in one parent pom.xml (which is loaded via theparent tag
within the dspace-aip/pom.xml).
Now, take a look at the [dspace-src]/pom.xml. This is the main Parent
pom.xml for dspace (with an artifactid of 'dspace-parent')
http://scm.dspace.org/svn/repo/dspace/trunk/pom.xml
This is the pom.xml which actually lists the versions of every
dependency used by the various APIs of DSpace. If you search in this
pom.xml, you'll find this entry:
dependency
groupIdpoi/groupId
artifactIdpoi/artifactId
version2.5.1-final-20040804/version
/dependency
That's where the 2.5.1 version is sneaking in. If you make your
necessary changes to this pom.xml, everything should act as you expect it
to. So, just undo your changes in 'dspace-src/dspace-api/pom.xml', and
instead make those changes to 'dspace-src/pom.xml'
I hope that helps!
- Tim
On 10/5/2010 2:36 PM, Keith Gilbertson wrote:
Hi,
I've been experimenting with a Media Filter for text extraction from
PowerPoint files. It's based on the Apache POI libraries, as was suggested
by others in a previous thread.
It uses the poi, poi-scratchpad, and poi-ooxml artifacts, in version
3.6, the latest release version from Apache. I haven't done much with
Maven, and am not sure
Re: [Dspace-tech] tomcat reporting memory leak?
On 6 Oct 2010, at 15:15, Graham Triggs wrote: [snip] This is exactly the kind of pointless pontification that we got last time. Any point that is raised is deflected or ignored, and you even manage to contradict yourself between paragraphs. What's it to be, should patches benefit ALL repositories, or is it fine if it's just some? Or the other way round, maybe? I will be very happy to offer our experiences regarding large-scale DSpace instances with the community, if that can be of any help. But not if it involves having to deal with Graham Triggs. I really do not have time for this. -- Tom De Mulder td...@cam.ac.uk - Cambridge University Computing Service +44 1223 3 31843 - New Museums Site, Pembroke Street, Cambridge CB2 3QH -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] tomcat reporting memory leak?
All, I would really appreciate it if we could stop the negativity in this discussion thread. I'm sorry to have to post a message of this sort publicly, but I feel I'm unfortunately being forced to do so. Insults and negativity on a public listserv do not help anyone. I also personally take offense to the insulting of anyone in our DSpace Committers group, as they are volunteering their own time (sometimes even outside of their workplace) to make DSpace software better. Open source software does not build and maintain itself, and our group of Committers have made it their passion to improve DSpace for the benefit of us all. Despite any arguments or differences we all may have, it is in our best interest to work together to resolve these issues in a friendly and timely manner. There is a place for arguments and disagreements on these DSpace mailing lists and I welcome them, provided they are kept constructive. I'm in touch with Cambridge around their performance issues off-list, and hope that we can work towards a solution to these issues for everyone involved. Thanks, Tim Donohue Technical Lead for DSpace Project DuraSpace.org -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace/Maven help request - update dependency version
Thanks Graham and Tim. I hadn't seen that. On Oct 6, 2010, at 11:52 AM, Graham Triggs wrote: That version of tm-extractors is quite old. There is a newer version on the Google site - http://code.google.com/p/text-mining/ - but it will take a bit of work wrapping things up for general use. It has dependencies on newer versions of POI than 0.4, and some distinct improvements to it's robustness. G On 6 October 2010 16:39, Tim Donohue tdono...@duraspace.org wrote: Ugh -- sounds like you've entered dependency hell. Though, I think the one shred of good news here is that it seems to only have a dependency conflict in one place in our codebase. It looks like (at a glance) if our WordFilter can be re-written to no longer need the org.textmining project, you *might* be OK (i.e. hopefully it wouldn't snowball on you). But, that would require finding a Word document text extractor that is as good as (or better than) that 'org.textmining' one, and then hoping it doesn't cause another dependency conflict. Not sure of any alternative Word text extractors, off the top of my head, but maybe others know of one? - Tim -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Send item to Facebook and CSS loading inconsistently problem
Hi, all,
I added the share menu posted by Stuart yesterday afternoon, and it seemed
work ok.
However this morning, I started to notice weird things: the stylesheet doesn't
apply to all pages consistently. For example, the homepage and many other pages
in ie7 display ok (load both style.css and style-ie7.css), but the communities
pages don't load style-ie7.css. I never noticed this kind of problem before,
the pages in the same browser display the same before (all bad, or all good).
I tried to reverse to an earlier version of sitemap.xmap, tried to comment out
the share section code in my local.xsl, and tried to use compatibility mode
or not, however, some pages in ie7/ie8 still will load both style.css and
style-ie7.css, some only load style.css. Also, some of my Safari pages will put
out ie7 as well, which makes the pages really messed up. How can I fix this?
I attached my sitemap.xmap below (we use modified Kubrick theme).
Thank you for your help!
Sophie
...
map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0;
map:pipelines
!--
Define global theme variables that are used later in
this
sitemap. Two variables are typically defined here, the
theme's
path and name. The path is the directory name where
this theme
is located, such as Reference for the reference
theme. The
theme's name is used only for descriptive purposes to
describe
the theme.
--
map:component-configurations
global-variables
theme-pathwsu/theme-path
theme-namewsu/theme-name
/global-variables
/map:component-configurations
map:pipeline
!-- Allow the browser to cache static content for an
hour --
map:parameter name=expires value=access plus 1
hours/
!-- Static content --
map:match pattern=themes/*/**
map:read src={2}/
/map:match
map:match pattern=*.htm
map:read src=static/{1}.htm
mime-type=text/html /
/map:match
map:match pattern=*.htm
map:read src=static/policies/{1}.htm
mime-type=text/html /
/map:match
/map:pipeline
!--
The theme's pipeline is used to process all requests
handled
by the theme. It is broken up into two parts, the first
part
handles all static theme content while the second part
handle
all dynamic aspect generated content. The static
content is
such things as stylesheets, images, or static pages.
Typically
these are just stored on disk and passed directly to the
browser without any processing.
--
map:pipeline
!-- Never allow the browser to cache dynamic content
--
map:parameter name=expires value=now/
!-- Aspect content
There are five steps to processing aspect content:
1: Generate the DRI page
The first step is to generate a DRI page for
the request;
this is handled by the aspect chain. Once it is
generated
it is the beginning of a theme's pipeline, the
DRI page is
ultimately transformed in the resulting XHTML
that is
given to the user's browser.
2: Add page metadata
The next step is to add theme specific metadata
to the
DRI page. This is metadata about where the
theme is
located and its name. Typically this metadata
is different
depending on the users browser, this allows us
to give
different stylesheets to Internet Explorer than
for other
browsers.
3: Transform to XHTML
The third step is the main component of a theme
the XSL
transformations will turn the DRI page from the
aspects
into an XHTML page useable by browsers.
4: Localize the page
The second to last step is to localize the
content for the
[Dspace-tech] MVN error: Plugin's descriptor
Dear Sir, I am trying to assemble DSpace 1.6.2 with Maven 2.2.1. I am getting following build error [INFO] Internal error in the plugin manager getting plugin 'org.apache.maven.plugins:maven-release-plugin': Plugin 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-8' has an invalid descriptor: 1) Plugin's descriptor contains the wrong artifact ID: maven-site-plugin 2) Plugin's descriptor contains the wrong version: 2.0-beta-7 Please let me know how to solve this problem With Regards Indu Bhushan RRCAT, Indore -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] How to customize advance search in JSPUI
Hello All, I am working on Dspace 1.6 JSPUI. I face 2 problems *1- How can i customize advance seach in JSPUI (Dspace 1.6)? 2-How can i customize the result of browse links(like title, author, etc)? I want when i click om title instead of 3 column i want 4 or 5 column (more details) will come.* Please any one suggest me how will i achieve these task. Thanks in Advace.. plz help.. Thanks and Regards Shashidhar Chaturvedi Programmer NIC Trivandrum 9037695850 shashidharchaturve...@gmail.com -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] handle problem
Hello All, I am working on Dspace 1.6.2 JSPUI. the handle is working , but if for example we use this URL: http://hdl.handle.net/10556/115 http://hdl.handle.net/10556/115, we have this result: http://elea.unisa.it:8080/xmlui/handle/10556/115 http://elea.unisa.it:8080/xmlui/handle/10556/115, unfortunately we do not use XMLUI, but use jspui. So we should return such http://elea.unisa.it:8080/jspui/handle/10556/115 http://elea.unisa.it:8080/jspui/handle/10556/115. How can we do? Thanks, Gaetano __ C.S.I. Universita' degli Studi di Salerno Gaetano Rufino Ufficio Sistemi Tecnologici E-Mail: mailto:gruf...@unisa.it gruf...@unisa.it Tel: +39 089 966 350 Fax: +39 089 966 368/346 Tel. HelpDesk: +39 089 966 400 __ Sic parvis magna -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
