The key is to have the Tridion java wrapper fire up the JVM in debug mode:
java -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044 -Djava.compiler=NONE -Xnoagent
The rest is business-as-usual remote debugging with Java.
Tridion appears to set jvmLoader.Debug = true; by default. So you should just be able to attach to the java process ...
All Java 6 versions are officially supported.
Note: Java versions 6 update 26 to 6 update 30 may create problems with the publishing process and some other operations due to known issues in incompatibility between Oracle's jdk and Microsoft's sqljdbc4.jar
For more detail on this issue you can see THIS thread.
From my personal experience, I noticed the ...
You really have to think of SDL Tridion in two parts (well two main parts - there's a lot more to it than that :))
The 'CMS' side - this could be content that is published or unpublished that lives inside the CMS - this is where you would use the 'Core Service' (a .Net web service) to put / pull content in the CMS, or perform other CMS related tasks.
I would suggest following the official Tridion Training Curriculum. It is created for this purpose of introducing new developers to Tridion and also walking them through how to build a website using the CMS. It is a minimum of 3 full days and available from SDL here.
The next best thing is to find a simple website and try to re-create this site in Tridion ...
Take a look at my blog post http://yatb.mitza.net/2013/07/a-java-service-oriented-architecture.html.
It explains a Service Oriented approach to consuming OData content from a web-application using Java (namely OData4J). There is an example of the actual OData call.
Your code is creating a Multimedia Type (which you need when creating a Multimedia Schema).
To create a Multimedia Component you will first need to upload the binary data to the Content Manager, and then you create the Component and set its Multimedia Properties. Here is some sample code in C#, but it should give you a rough idea:
string myFilename = "...
I'm not sure you have the right level of expectations there, as it seems that you would want Java/Eclipse to provide you the same benefits that Microsoft / .NET / LINQ provide when working with OData services.
The webservice and its capabilities are exactly the same independently of the client you use - .NET, Odata4j, JayData - but the client itself will ...
Check out the sample code below. You will of course have to change all the references to TCM URIs to meaningful values on your system. Also, I'm uploading a file called Beagle.jpg which initially exists in the C:\ folder of my client machine.
ICoreService client = CoreServiceFactory.getBasicHttpClient();
ReadOptions readOptions = new ReadOptions();
only Java 6 is supported for Tridion 2011 SP1 HR1, it does not work on Java 7(i hadtried) & i do not think its support for Java 7 is going to happen because there would be good amount of change and 2013 is already launched. so very less chance.
Latest Version of Java 6 can be download from here
Tridion CMS is a completely proprietary software and no code will be provided.
Also their is no concept of trial version or free developer download etc. and you have to get the licenses to get your hands down on it - See HERE
Also, this essentially a hosted solution which can be hosted in Cloud or on your local servers provided you have valid licenses ...
I think the servlet-name in your filter mapping might be the problem here:
<filter-name>Ambient Data Framework</filter-name>
<servlet-name>Content Delivery Web service</servlet-name>
So your ADF Filter doesn't come into play for your Java app, since it seems to be mapped to the ...
To answer the more black and white questions first:
Is there a Java version available?
Yes, but its not yet publically available, you may be able to get a sneak preview if you contact SDL.
Can it work with Grails?
I don't really have any experience with Grails, but it may be possible to integrate it as they both use Spring MVC. How much additional work ...
Since DXA 1.1, Component Links to Multimedia Components are resolved as Binary Links (so a direct link to the MM Component's binary content).
I see you have tagged dxa java, which means that you will need DXA 1.2 (the first official DXA Java release).
I implemented something similar using Tridion and JSP. In my use-case, a user had to verify they'd read some terms and conditions before they could see the content of the page, but that's easily enough adapted to your use case where a stock username/password is set.
From memory, the process worked something like:
We assigned a protected component a ...
I would strongly advise against connecting to the Content Manager (to retrieve content) from your client web application.
As John says, there are two distinct parts and it is better to work with these than against them!
Quite often Tridion is installed within the company network and publishes content out to a separate 'demilitarised zone' (DMZ). If ...
Instead of using the ComponentPresentationAssembler, you could use the ComponentPresentationFactory to determine this. It's getComponentPresentation method will return a ComponentPresentation object that is null in the case of no CP existing
bool hasPres = false;
// add a method to get the CPF to your tagVals class
The temp location is configurable via cd_storage_conf.xml.
The Storages element takes an attribute called TempFileSystemTransactionLocation. For example:
<Storage Type="persistence" Id="sqlserver" dialect="MSSQL" Class="com.tridion.storage.persistence....
You have a few options:
Start the Deployer JVM with system property java.io.tmpdir set to whatever you want;
Example: java -Djava.io.tmpdir=C:\MyTemp com.tridion.deployer.Deployer
On Windows, set the environment variable TMP to a custom value. The Java JVM uses this value as default (when you don't specify the system property java.io.tmpdir). If you are ...
There is a known defect with WAI and 2011 SP1. Multiple cookies are set per session for each page requested that has PnP enabled on it. It should be one cookie per session. This defect has a Hotfix for it on top of 2011 SP1 + HR1, CD_2011.1.1.79834. It is at Tridion World here:
This was a bug in the dd4t-2 beta stack. Since you are using (probably?) a mixed set of DXA-Java and a dd4t-2 stack, I'm not sure where it should be fixed.
In any case, the actual fix is in org.dd4t.contentmodel.PageImpl:
// change this line:
private List categories;
// Into this line:
I've done solutions for this in the past... and as usual, there's many ways to peel this cat. While I still believe that component linking, functionally, is really what you need (even if people think it's not what they want), I agree that for certain pages you could use page linking.
Solution that works
So what I've done quite successfully in the past is ...
These dependencies aren't available from maven central. You need to host those yourself. To find out which items are hosted on Maven central:
So they can't be resolved without hosting them yourself.
Use Artifactory or Sonatype Nexus to make this happen.
The instructions for hosting the ...
This type of architecture is perfectly possible, with files stored on some kind of shared resource across the web servers. Usually I see a NAS or SAN type device used for this purpose. Steer clear of syncing technologies - in my experience they are prone to issues.
However, these architectures are less common in Tridion deployments today. I would urge to ...
I think the issue is only with the slash special character. Rest of the special characters are fine.
For instance, if I call the getLinkAsString method (getLink method in your Java code snippet will be calling getLinkAsString I suppose) like the below code snippet, I am able to get the page URL. Note the link text property has no backslash before the span ...
It seems to be a requirement for SCD (Secure Content Delivery), with SCD you indeed can manage the user roles in Tridion as metadata in folders/components/pages.
SCD will follow the same Java Security specification but it made tridion friendly.
Additionally you can use JAAS and a Tom Cat JAAS Realm, it will allow you to stop using the tom cat users file. ...
SDL owned packages always start with com.tridion.* or com.sdl.*, not with com.sdltridion.* (and especially not com.sdltridion.contentmanager.*).
It seems like you're using custom jars (maybe from here?) and you should keep track - or contact the author - of those.
Update I just found the chapter in the documentation you mention and it also states