9
You can turn it back on in your Spring dispatcher servlet XML:
<!-- DD4T Provider beans -->
<bean id="binaryProvider" class="org.dd4t.providers.impl.BrokerBinaryProvider">
<property name="contentIsCompressed" value="true"/>
<property name="cacheProvider" ref="cacheProvider" />
</bean>
<bean id="...
6
That EHCache uses a lot of memory makes sense, since when caching is turned on, it will use the configured amount of memory to store items.
If you disable cache, be prepared to take a big performance hit. All models and items generated and fetched from the Tridion Broker database will always happen. Turning on the Tridion Object Cache will essentially move ...
3
To answer my own question; SDL delivered a hotfix and it resolved the issue.
3
Whenever component is in a workflow, it gets checked-out, so v0 version (minor version) is created. And yes, this is a standard behavior. When component leaves workflow, minor version is no longer there.
Besides, I see that you publish binary with TCM id in file name. If this gives you problem, you can remove TCM id from filename during publishing.
3
First of all, you will need to setup JMS as your cache invalidation mechanism, as DD4T's caching mechanism does not support listening to RMI. You can read all about that in Quirijn's blog post and the follow-up post.
To enable JMS cache invalidation in a dd4t-2.0 webapp, you need to do the following:
Ensure the following dependencies are present:
<...
3
When using the DD4T 2.0 Templates (latest version 2.1.2), to enable compression I believe you have to add the CompressOutput TBB as last item in your Page Template. Not sure if you can also use it on a Component Template.
The benefits of using compression are that the size you push over the line (between the CM and Deployer) is less, and thus the transport ...
2
You can change schema name anytime but remember don't change Root element name if not required, if you still want to change the Root Element Name too then you have to update the same in your Java DD4T application Modeling.
2
You probably can use Spring's JMS listener combined with OSB. Configuration looks this this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
"http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
<bean id="cacheMessageListener" class="org.dd4t.core.caching.jms.impl....
2
Apparently it needs to be the tcm uri of the folder Example: tcm:7-2056-2
2
As Velu said, this is most probably an orphan item. It means that it was published with page, but when page was unpublished, it stayed in broker, most probably because references to this binary stayed in broker. So Creating unpublish package for binaries will most probably not work.
For this you need to contact customer support. They will give you queries ...
1
Seems to look like your case orphan records in content broker database, or could be a chance those binaries to be used in other pages not sure.
If the item does not exist in the CM, then you cannot send the publish transaction from the CM.
If the binaries are orphaned as in, they were published together with a page, but somehow the page got unpublished, ...
1
As far as I'm aware of you can use JNDI names for data sources in the Content Delivery configuration files.
If you search the 2013 documentation for jndi you will see the locations of where it is mentioned, for example in cd_storage_conf.xml:
https://docs.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20full%20documentation-v1/GUID-27C4B58F-A922-4CFD-8F9A-...
1
Configuration mentioned by Raimond above works and the spring webapp is now able to make connection to the JMS topic defined in OSB. Just couple of minor corrections thats why pasting the conf again here:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
"http://www.springframework.org/dtd/spring-beans.dtd">
...
1
There's no generic Transport Listener specification in the JMS Api / specification, so hence it's not possible to keep this part generic.
You should be able simply remove the transportListener and the references to it and then invalidation will still work.
1
I guess the conclusion maybe is that the name of the class JMSTransportListener should possibly have been ActiveMQTransportListener instead, and if you are not intenting to use ActiveMQ, you should implement your own jmsTransportListener.
However I'm not completely sure because you fail to mention what changes you are making to support your other JMS server....
1
When a Multimedia Component with an external URL is published, Tridion tries to download the external resource and include it in the transport package for deployment to the content delivery system as configured. In your case, the error message clearly shows that the remote server returned a 503 error code when Tridion attempted to download the resource.
If ...
1
We ran into a similar issue and unfortunately there isn't anything available OOB to get this information. I don't recall of the exact version of the DD4T that we used.
We ended up injecting a value using TBB in xpath on the fields and then on the RESTful api side used dd4t to serialize the objects, read the value from XPath that we injected and generated an ...
1
Looks a bit vague question to me - If I do rename the schema and publish the components again; will the application break ? - You really need to look into your code - in case you have written custom broker queries based on Schema Name or if there is any code using Schema Name for the functionality like Event System code or may be some custom page - This may ...
1
This isn't intended as a specific answer but the comment size/format was is too restrictive - and I feel could still be useful if anyone stumbles across this specific question.
The answer - as noted by Robert is that the TCM URI (the fully qualified Tridion ID tcm : publication_id - internal_id - type_id) is usually expected in the scripts.
The use of the ...
1
looking at the ViewModelBase, is it possible to set setRawData to true and call the inherited getRawDataAsString() to grab the RAW component data?
@ViewModel (
rootElementNames = {"joshsContent"},
viewModelNames = {"JoshsStuff"},
setComponentObject = true,
setRawData = true)
public class JoshsStuff extends ...
Only top voted, non community-wiki answers of a minimum length are eligible
