[MAGNOLIA-1082] Activation fails depending on the repository data to be activated Created: 26/Sep/06 Updated: 26/Feb/08 Resolved: 28/Sep/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 3.0 RC3 |
| Fix Version/s: | 3.0 RC3 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Ralf Hirning | Assignee: | Boris Kraft |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
After uploading content using Packager the content could not be activated. So it seems that activation does not support all possible data stored in a repository. The logfile says: |
| Comments |
| Comment by Sameer Charles [ 26/Sep/06 ] |
|
John, I had the same issue when I was working on versioning. I was storing one serialized class without encoding it. |
| Comment by Ralf Hirning [ 26/Sep/06 ] |
|
Hi Sameer, I don't think that this is a good idea to solve the problem. The repository and activation must support binaries without encoding. |
| Comment by Sameer Charles [ 26/Sep/06 ] |
|
in jackrabbit binaries are always encoded otherwise xml export/import does not work, in magnolia version implementation we also serialize objects in to version store with Base64 so it does not break any XML parsing on this data. |
| Comment by Ralf Hirning [ 26/Sep/06 ] |
|
Now the transfer part works, but the creation/update on the subscriber fails. I add the activation-log of the subscriber. This is all very strange, Packager does not use any JCR-API, but uses the Magnolia-API to write to a repository. For example to write a binary, the following code snippet is used NodeData nodeData = node.createNodeData(getName(), getType()); if (getType() == PropertyType.BINARY) { nodeData.setValue(getStream()); }node.save(); So it should be stored just as binary and activation should be able to deal with it. |
| Comment by Ralf Hirning [ 26/Sep/06 ] |
|
It seems that this bug is related to jackrabbit's import/export problems with binaries (see http://jira.magnolia.info/browse/MAGNOLIA-603 and http://jira.magnolia.info/browse/MAGNOLIA-1000). |
| Comment by Sameer Charles [ 27/Sep/06 ] |
|
Its not related to binary in any way,. Activation does not care how repository takes care of encoding, this part is outside the scope of activation. |
| Comment by Sameer Charles [ 27/Sep/06 ] |
|
after looking at the activation log you attached it looks like some page is missing where you are activating ERROR info.magnolia.cms.exchange.simple.SimpleExchangeServlet 26.09.2006 10:56:55 – Exception caught |
| Comment by Ralf Hirning [ 27/Sep/06 ] |
|
The problem is connected to import / export. Se the author's activation.log... |
| Comment by Sameer Charles [ 28/Sep/06 ] |
|
closing this issue since its not related to activation, please create another issue for content migrator or for JCR impl if needed |
| Comment by Boris Kraft [ 28/Sep/06 ] |
|
wrong resolution |
| Comment by Ralf Hirning [ 28/Sep/06 ] |
|
I found the error. An Attribute with Type Date has been saved as String. |
| Comment by Boris Kraft [ 28/Sep/06 ] |
|
not our bug |
| Comment by Sameer Charles [ 28/Sep/06 ] |
|
And this is intended to be like this, You must specify if the node has to be Binary type because of the nt:resource handling in JCR |