Re: Multi-value references
hi aleksandar, how do you remove the mv properties? with Property.remove() or by setting individual values of the mv array to NULL ? regards, toby On 12/6/06, Aleksandar Pecanov [EMAIL PROTECTED] wrote: Hi, I seem to have run into a bit of a problem ... I wrote a method for removing (braking) node's references in order to sucessefully remove a referenced node. What it actually does is remove all properties that refer to a node or if it is a multi-value property, it removes just the value pointing to the node. Now, my problem is with the second case (multi-value properties). Although values are removed (within a session), the node is still being referred by this properties (or so the getReferences() method claims). This wouldn't be much of a problem (I'll just ignore it), but upon saving the session containing the changes, a ReferentialIntegrityException is thrown thus preventing the full removal of the node. Has this been tested already somewhere? Thank you. -- - [EMAIL PROTECTED] --- Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 --- http://www.day.com ---
[jira] Commented: (JCR-97) Improve Checkstyle conformance
[ http://issues.apache.org/jira/browse/JCR-97?page=comments#action_12456006 ] Stefan Guggisberg commented on JCR-97: -- i committed jan's patches (svn r483071) jan, good job, thanks! Improve Checkstyle conformance -- Key: JCR-97 URL: http://issues.apache.org/jira/browse/JCR-97 Project: Jackrabbit Issue Type: Improvement Reporter: Jukka Zitting Priority: Minor Attachments: jackrabbitAPICheckstylePatch.patch, jackrabbitCoreUnnecessaryCodeCleanup.patch This is an ongoing meta-issue for improving the Checkstyle conformance of the Jackrabbit codebase. Checkstyle (http://checkstyle.sourceforge.net/) is an automated tool for checking conformance with coding standard and good coding style. A Checkstyle report for Jackrabbit can be generated by running maven checkstyle. Currently the Jackrabbit Checkstyle report contains thousands of trivial problems like unused imports and minor formatting issues. While it would be possible to just remove those checks from the Jackrabbit Checkstyle configuration, it would certainly be better to fix the real issues. After fixing the trivial problems, the Checkstyle reports become much more valuable tools in locating troublesome code and identifying chances for improvement. While this issue remains open, you have an open mandate to improve the standards conformance and coding style of the Jackrabbit sources. This mandate applies only to changes that fix problems reported by Checkstyle while making no changes to the external interface or behaviour of the changed code. The commit messages of such Checkstyle improvements should be labeled with the Jira key of this issue (JCR-97) to mark the changes as style-only. This way other committers will have easier time reviewing your changes for bugs or other unexpected side-effects. If you are not a Jackrabbit committer, but want to help improve the Checkstyle conformance, you can make your changes using sources from anonymous subversion and send your changes as an attachment to this issue. Please see the Javadoc improvement issue JCR-73 for details. PS. Blind conformance to style guides is seldom beneficial. Please remember that the goal of this issue is to improve Jackrabbit code, not just the Checkstyle output! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (JCR-661) RMIC not working in subprojects when compiling parent using maven2
[ http://issues.apache.org/jira/browse/JCR-661?page=all ] Stefan Guggisberg reopened JCR-661: --- reopening as the applied batch breaks the build on mac osx. the m2 build on mac osx (10.4) did work before the patch had been applied. the hard-coded dependency on tools.jar causes the build to fail complaining about the missing dependency. note that there's no tools.jar in the mac jdk. the classes contained in tools.jar are on a mac included in classes.jar on the boot classpath. temporary workaround for building jackrabit on a mac: remove the tools.jar dependency in the top-level pom. RMIC not working in subprojects when compiling parent using maven2 -- Key: JCR-661 URL: http://issues.apache.org/jira/browse/JCR-661 Project: Jackrabbit Issue Type: Bug Components: maven Reporter: Jan Kuzniak Assigned To: Jukka Zitting Priority: Minor Fix For: 1.2 Attachments: pom-rmi-patch.patch This is because there is a bug such that if you have a child build which uses the ant plugin it inherits the plugin dependencies of the first time the plugin is declared. The workaround is to put the antrun plugin in the toplevel, and add the java jar to its plugin dependencies. (reference: http://mail-archives.apache.org/mod_mbox/maven-users/200602.mbox/[EMAIL PROTECTED]) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: jcr taglib
Hi, On 12/6/06, Torgeir Veimo [EMAIL PROTECTED] wrote: I'm looking to use the jcr taglib, but the examples doesn't seem to work out of the box, ie. the InitServlet doesn't compile, since JNDI_DEFAULT_REPOSITORY is not defined in CRTagConstants.java. I haven't tried the examples lately :(. I'll see it asap. It's easy to fix locally, but I'm wondering if this taglib is still maintained? I make changes as I need them, not much lately. However, if you find something that should be fixed please feel free to submit a patch. Also, the tld should probably be automatically put into META-INF in the resulting jar file, but I'm not sure how to configure maven how to do this.. you are right, I'll take a look to it asap. br, edgar -- Torgeir Veimo [EMAIL PROTECTED]
jcr taglib: setting node attribute with object doesn't work
If I use the properties tag and et a node attribue with a java object, it doesn't work, since the setNode() method in PropertyTag.java takes a string as an argument. There's no category for the jcr taglib in jira? -- Torgeir Veimo [EMAIL PROTECTED]
Re: jcr taglib: setting node attribute with object doesn't work
On 12/6/06, Torgeir Veimo [EMAIL PROTECTED] wrote:
On Wed, 2006-12-06 at 18:30 +, Torgeir Veimo wrote:
If I use the properties tag and et a node attribue with a java object,
it doesn't work, since the setNode() method in PropertyTag.java takes a
string as an argument.
Hmm, it seems it's because the way I call the tag,
jcr:properties node=${currentnode} var=property ..
where currentnode is an object, then the servlet compiler has already
interpreted it and thus the propertyTag can't use JCRTagUtils to
interpret the expression itself.
I wrote the jcr taglib for a project which used a servlet version
previous to 2.4. AFAIK you can disable JSP EL with any of the
following options.
* in a webapp - if you use a 2.3 web.xml file, it is disabled
* in web.xml, you can turn it off for a set of JSPs using the
jsp-property-group element
* in a page - use the isELEnabled attribute of the page directive
* in a page - replace $ with #36; , or use \${ instead of ${
Maybe we should update the taglib to work with jsp 2.0.
br,
edgar
--
Torgeir Veimo [EMAIL PROTECTED]
Re: jcr taglib: setting node attribute with object doesn't work
On Wed, 2006-12-06 at 16:31 -0300, Edgar Poce wrote: Maybe we should update the taglib to work with jsp 2.0. That would be easier, since I use EL extensively in my pages. I'm not sure how to instruct the page compiler that the tag wants to evaluate the attribute value itself. -- Torgeir Veimo [EMAIL PROTECTED]
Re: jcr taglib: setting node attribute with object doesn't work
On 12/6/06, Torgeir Veimo [EMAIL PROTECTED] wrote:
On Wed, 2006-12-06 at 16:31 -0300, Edgar Poce wrote:
Maybe we should update the taglib to work with jsp 2.0.
That would be easier, since I use EL extensively in my pages. I'm not
sure how to instruct the page compiler that the tag wants to evaluate
the attribute value itself.
sorry if I'm missing something but in my previous post I commented
that AFAIK you can disable the EL by using any of the following
options. Any of those options should do the trick.
* in a webapp - if you use a 2.3 web.xml file, it is disabled
* in web.xml, you can turn it off for a set of JSPs using the
jsp-property-group element
* in a page - use the isELEnabled attribute of the page directive
* in a page - replace $ with #36; , or use \${ instead of ${
probably the fourth will be the best option if you use EL in the same
page than jcr taglib.
br,
edgar
--
Torgeir Veimo [EMAIL PROTECTED]
[jira] Resolved: (JCR-661) RMIC not working in subprojects when compiling parent using maven2
[ http://issues.apache.org/jira/browse/JCR-661?page=all ] Jukka Zitting resolved JCR-661. --- Resolution: Fixed Fixed (I think so) the Mac issue in revision 483230 by adding a Mac-specific build profile. I don't have a Mac available for testing this, so please reopen if the issue remains. RMIC not working in subprojects when compiling parent using maven2 -- Key: JCR-661 URL: http://issues.apache.org/jira/browse/JCR-661 Project: Jackrabbit Issue Type: Bug Components: maven Reporter: Jan Kuzniak Assigned To: Jukka Zitting Priority: Minor Fix For: 1.2 Attachments: pom-rmi-patch.patch This is because there is a bug such that if you have a child build which uses the ant plugin it inherits the plugin dependencies of the first time the plugin is declared. The workaround is to put the antrun plugin in the toplevel, and add the java jar to its plugin dependencies. (reference: http://mail-archives.apache.org/mod_mbox/maven-users/200602.mbox/[EMAIL PROTECTED]) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Jackrabbit and Maven
Are we going to move the site generation from core to the parent? [EMAIL PROTECTED] egrep jackrabbit-site jackrabbit-core/* jackrabbit-core/project.properties:# Site Deploy (into ../jackrabbit- site for checkout on jackrabbit.apache.org) jackrabbit-core/project.xml:siteDirectory../jackrabbit-site/ siteDirectory It would be nice to start documenting those projects that have moved up out of the contrib section. Roy
unsubscribe
unsubscribe
