Thanks again for the quick reply. I did ad an issue for the missix
mix:referencable supertype, but before adding one for the activation
problem I thought I should run a simple test first:
- I copied the author instance and renamed it to "magnolia36test"
- I changed the activation settings so that my author instance would
publish to magnolia36test
- Then I deleted all data content from magnolia36test
- Finally I tried publishing again: Worked fine!
So there must be something wrong in my the magnoliaPublic instance.
Before I restart from scratch with a war, is there anything you could
think of that I might have been missing?
-will
On 24.06.2008, at 10:52, Jan Haderka wrote:
Hmmm, that seems like a problem. There should be an error stack
trace in
log file on public instance from when you got this message. Could you
please create an issue and attach the full stacktrace to it?
Thanks,
Jan
On Tue, 2008-06-24 at 10:43 +0200, Will Scheidegger wrote:
I'm facing one (hopefully) last problem now: When I try to activate a
data node (or even an empty folder in the data JCR Browser) I get the
following error message:
"Can't activate: : 1 error detected:
Message received from subscriber: Activation failed | /sbkv:
mandatory
property {http://www.jcp.org/jcr/1.0}uuid does not exist on web8081"
I again thought that this would be due to a missing
"mix:referencable"
on the web8081 instance, but that's not the case. The two instances
now have the exact same customnodes.xml file and I'm still getting
the
error message. Then I thought that the data nodes on the author
instance might be missing the uuids, so I deleted them all and
created
new test nodes using the gui: still no success in activating them.
Any help is warmly appreciated since I wanted to have this running
yesterday evening... Thanks!
-will
On 23.06.2008, at 18:04, Jan Haderka wrote:
I see, you found the solution yourself. I wanted to test few
different
scenarios before responding to you, but seem you managed to figure
it
out yourself in the mean time :)
By adding mix:referencable you do not loose performance. The reason
why
you have to do it is the fact that this mixin is no longer implied
since
we do not add mix:versionable to all nodes by default.
Cheers,
Jan
On Mon, 2008-06-23 at 17:55 +0200, Will Scheidegger wrote:
I added "mix:referenceable" as supertype to "dataBase". This solved
the problem. Of course I don't know if I'm loosing performance
benefits again this way...
Regards,
Will
On 23.06.2008, at 17:43, Will Scheidegger wrote:
O.k., after some digging around I had a closer look at the
custom_nodetypes.xml file and compared the two from Mag 3.5.4 and
3.6 M1. The only remarkable difference I could find is in the
definition of mgnl:contentNode. The Mag 3.6 file lists
mix:referencable as supertype for this type together with
nt:hierarchyNode. The old one only lists nt:hierarchyNode as
supertype. Now I vaguely remember something about a change in
nodetype definitions in Mag 3.6 to improve performance. Could it
be
that nt:hierarchyNode used to have mix:referencable as supertype
and
now doesn't anymore?
If so I guess this would mean that I have to add
mix:referencable as
supertype to my data nodes. Should I add it to each one? Or
should I
add it to one of their common supertypes? Which one: dataItem,
dataItemBase, dataBase?
Cheers,
Will
On 23.06.2008, at 17:21, Will Scheidegger wrote:
Hm... I thought about this too, because I imported the config
from
the old installation instead of creating it with the UI. So as
last
test before I posted this question I removed the config (/
modules/
data/config/types/mynode, /modules/data/trees/mynode), all data
and
recreated it using the GUI... but also the same name. Do you
think
that this might be the problem? Where are the node type
definitions
being stored? And how would I add mix:referencable to it?
Thanks for the help!
-will
On 23.06.2008, at 17:10, Jan Haderka wrote:
Hi Will,
is that from a data type you defined yourself manually or via
DataModule
UI? If it is the former, then you need to make sure that you add
mix:referencable to it, if the latter it is most likely a bug.
Cheers,
Jan
On Mon, 2008-06-23 at 17:03 +0200, Will Scheidegger wrote:
I'm testing Magnolia 3.6 M1 with a site which uses the data
module.
I'm pretty happy with the speed, but I'm facing a show stopper
now.
The following code works fine on Magnolia 3.5.4 but throws an
exception in 3.6m1
The code:
Content itemValues = (Content) matching.next();
String itemValuesUUID = itemValues.getUUID();
The exception:
javax.jcr.UnsupportedRepositoryOperationException
at org.apache.jackrabbit.core.NodeImpl.getUUID(NodeImpl.java:
2830)
at
info
.magnolia.cms.core.DefaultContent.getUUID(DefaultContent.java:
897)
Additional info: The "itemValues" node which is causing the
above
is a
data module node so it has its own nodetype.
Any ideas anyone? Thanks!
Regards,
Will
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
