? on hi8 - composite or component

I find myself having to transfer a old hi8 tape.
I'll be using SVIDEO out of the deck into my editing system.
Trying to decide if I need SVIDEO to composite cable or SVIDEO to component cable.
Problem is I don't have a svideo in on my system.
I can do composite or component in (with rca cables)
Since I'm coming SVIDEO out with hi8 - do I really get any more quality going with component (3 rca cables) rather than just staying with composite (2 rca cables)?

All versions of Premiere (Pro and Elements) work with Firewire, so you need an external device to accept your deck's output and convert to digital to then connect to your computer via Firewire
http://www.grassvalley.com/products/converters - http://www.grassvalley.com/products/advc55

Similar Messages

Best practices for adding components in a composite custom component

Hello,
I am developing a custom, composite JSF component need to dynamically add child components in my renderer class. I've noticed that people add components to a custom component in many different ways. I'd like to follow JSF best practices when developing this component - of the following approaches, which would you recommend? Or is there yet another approach I should be using?
1) in the encodeBegin method of my renderer class, create a new component, add it to the component tree, and let the page life cycle take care of the rendering:
HtmlDataList dimensionStateGroupDataList = (HtmlDataList) app.createComponent( HtmlDataList.COMPONENT_TYPE );
//set properties on dimensionStateGroupDataList
component.getChildren().add(dimensionStateGroupDataList);
2) in either the encodeBegin or encodeEnd method, create a component and encode it:
HtmlDataList dimensionStateGroupDataList = (HtmlDataList) app.createComponent( HtmlDataList.COMPONENT_TYPE );
//set properties on dimensionStateGroupDataList
dimensionStateGroupDataList.encodeBegin();
dimensionStateGroupDataList.encodeEnd();
Both of these methods are functional, and I prefer the first (why encode children if you don't have to?), but I am interested in other people's take on how this should be done.
Thanks for your help.
-Christopher

My bad, sorry, wasnt concentrating, Im afraid I have no experience with portlets, but I would have thought that you can mimic the outputLinkEx in you renderer by encoding your own links?
If you were to bind a backing bean variable to an outputLinkEx what would it be? Not understanding portlets, or knowing what an outputLinkEx is may be hindering me, but you should be able to create an instance of it in code like (this example uses HtmlOutputLink, you would need to know which component to use):
HtmlOutputLink hol = new HtmlOutputLink();
hol.set....Then set any attributes on it, and explicitly call its encodeStart, encodeEnd functions. Is that way off the mark.

Composite or Component AV Cable

Which AV Cable is better for the iphone. The composite or component. I would like to watch it on the TV and charge at the same time and jujst didn't know what the main differences were between the two.
THX

I have both cables (although on separate TVs) and they will both give you an excellent image.
As the other poster says, component is better, at least via the specs, but your own television and eyesight may make the difference hard to see. In some cases I actually prefer the composite input, as it tends to be more "movielike" (less video looking). It also depends on what else you have hooked to that set -- if you have a certain input free I wouldn't hesitate to choose either one for it, but if you have multiple inputs available you'd probably be better off going component.

Composite vs Component

I am debating on buying either the Composite or Component AV cable for my iPhone to play movies on friends TVs.
I want to buy the one that is gonna work on the bulk of TVs out there. The trend seems like most even new TVs will have RCA inputs but I know lots of old TVs wont have component.
So based on the idea of which one I am going to be able to use on most TVs, which one should I go with? As much as quality is nice with the component, if you can't plug the cable into the TV, quality is a waste since you cant watch anything.
Thoughts? Thanks!

I want to buy the one that is gonna work on the bulk of TVs out there. The trend seems like most even new TVs will have RCA inputs but I know lots of old TVs wont have component.
Accessing my vast experience with televisions I would estimate that 99.9% have a composite input, and about 95% also have component input.
Bear in mind though, the Hollywood cartel is pushing hard to make component video illegal. In fact, beginning this year DVD players can no longer output HD video on component cables. HD can only output on the less reliable HDMI connector.
About the only time I see a television without component inputs are on the cheap televisions that hotels buy.

URGENT: How to build composite custom component with a valuechangelistener?

Hi there!
I already posted regarding this issue before but unfortunately there wasn't any answer. But I don't think what I am trying to achieve is something unusual.
I am trying to build a composite custom component, that consists of some UISelectOne components and some UIInputText fields. Now I need to fill the combo boxes depending on the selected values of the other boxes. Therefore I added a value change listener. But when it fires I get an index out of bounds exception on the page.
The problem seems to be that the child components are being added twice to the component: Once in the constructor (which I am doing and which is called everytime the component is built) and once as part of the Restore View Phase (which JSF is doing).
So my question is: How and where do I correctly initialize my component's children?
A full code example can be found under http://forum.java.sun.com/thread.jspa?threadID=586301&tstart=150
Thanks a lot in advance!

#2 sounds utterly strange to me. How would I utilize the phase id?The code below shows my idea whereas I never validate it in any real projects:
public class MyPhaseListener implements PhaseListener {
     private static final String IDKEY = "PHASEID";
     public static PhaseId getCurrentPhaseId() {
          return (PhaseId) FacesContext.getCurrentInstance().getExternalContext().getRequestMap().get(IDKEY);
     public void beforePhase(PhaseEvent event) {
event.getFacesContext().getExternalContext().getRequestMap().put(IDKEY,event.getPhaseId());
     public PhaseId getPhaseId() {
          return PhaseId.ANY_PHASE;
}You can write your constructor like as:
if (MyPhaseListener.getCurrentPhaseId().equals(PhaseId.RENDER_RESPONSE ) {
     /* create children because this is the first time to create the component */
}

Can't reference methods in a Bean from a Composite JSF Component.

I have the following composite component TestCC.xhtml:
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html"
xmlns:cc="http://java.sun.com/jsf/composite" xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<cc:interface>
<cc:attribute name="manager" method-signature="java.lang.String helloTest()" required="true"/>
</cc:interface>
<cc:implementation>
Hello #{cc.attrs.manager} !!!!!!!!!!!!!!!!!!!!!
</cc:implementation>
</html>
When I try to call it in a JSFF file:
<?xml version='1.0' encoding='UTF-8'?>
<ui:composition xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:icc="http://java.sun.com/jsf/composite/IchipComponent">
<icc:TestCC manager="#{viewScope.PatientClinicalBean.helloTest}"/>
The page crashes at my composite tag with the following message in the console:
javax.el.ELException: //C:/Documents and Settings/tlam/Application Data/JDeveloper/system11.1.2.3.39.62.76.1/o.j2ee/drs/iCHIP/ViewControllerWebApp.war/WEB-INF/classes/META-INF/resources/IchipComponent/TestCC.xhtml: javax.el.PropertyNotFoundException: //C:/Documents and Settings/tlam/Application Data/JDeveloper/system11.1.2.3.39.62.76.1/o.j2ee/drs/iCHIP/ViewControllerWebApp.war/Patient/Profile/Clinical.jsff @13,86 manager="#{viewScope.PatientClinicalBean.helloTest}": The class 'patient.profile.PatientClinicalBean' does not have the property 'helloTest'.
But my managed bean does have a public String helloTest() method, as well as other methods that work fine elsewhere in my JSFF page:
public class PatientClinicalBean{
String test = "TESTING";
public String helloTest() {
return test;
I have tried this many times with different methods, all with the same result. Yet if my composite component outputs just a string and I enter the expression <icc:TestCC manager="#{viewScope.PatientClinicalBean.test}"/> to access the String test field directly it executes properly. I can't seem to reference any of the methods in PatientClinicalBean from only my composite component, when other method calls work fine in the same JSFF page. All other examples I've seen on the web have no problems doing this the same way I have, am I missing something?!
Edited by: tnology on 24-Oct-2012 14:13
Edited by: tnology on 24-Oct-2012 14:14
Edited by: tnology on 24-Oct-2012 14:16

What if you change the method in the class like this?
public String getHelloTest() {
return test;
}If you attempt to read a property call abc from a bean, you need to have a method called getAbc(). If you attempt to set a property called abc, you need to have a method called setAbc(...). This is JavaBeans convention.

What av cable is the best : composite or component

Hi is there a difference between the image quality when I used component av cable (MB128LL/A) or composite av cable (MB129LL/A) with my ipod classic and my plasma flat screen tv (Panasonic 50")?
Do you know some alternative product (the Apple one are a bit expensive)?
Thanks!

First off, the Apple products are the only ones that have the Video-ID chip in them, so they're the ONLY ones that work with the 6th Gen Classics.
Secondly, component cable is always better, especially since it can show your iPod videos in LOW-res HD.

AV Cables Composite or Component?

What's the difference? How do I know which I want / need to connect my Nano to a TV?

Welcome to the discussions, ejmoment.
The difference is really going to be what kind of television you have. If you have a newer TV with Component connections (red green blue, then red and white), then get the component cable. If you don't, then your only other option is the Composite cable (yellow red and white).

Adding a Web Dynpro Model on a Composite Apllication Component in CE 7.1

Hi experts,
I am trying to add a web dynpro model to a Composite Application DC.
I am using SAP NW CE 7.1.
In CE 7.0, this was done by simple right click on the CA DC.
but i am not able to do it in CE 7.1.
Can somebody tell me how do i add a web dynpro model to a composite application DC???
basically i need to add a UI corresponding to a composite application?????
Cheers
Gaurav Raghav

Hi Srinivasan Subbiah,
The option you just mentioned is disabled.
how can i enable it???
Also let me explain what i need.
I have a 3 step process where in a user fills a form and sends it to his manager, who appoves/reject it based on some criterias. then the approval/rejection alert is send back to the user.
Now i need to develop the UI as well as Business Logic for this process.
How do i go about it?????
I can develop the UI in a Web Dynpro DC and the Business Logic in a Composite Application DC. How do i associte one with the other????
In CE 7.0, this was achieved by addind a Web Dynpro Model in the Composite Application Project. How do i acheive the same in CE 7.1 ?????
Thanks and cheers
Gaurav Raghav

Using the Composite/Component AV cable for slideshows

iPad 32G WiFi
Hi,
I plan to use the Composite or Component AV cable for slideshows in the Photo app. There is a setting (TV Out) for Videos in Settings, I will set it to PAL when I run the slideshows in Asia later this week.
Question: Once set, will this setting under Videos apply to the Photo app for slideshows as well, or this setting is only good for videos?
Any suggestion will be greatly appreciated! /Kenny

No problem
enjoy your magic machine

How can I connect my 2009 Mac Mini to a TV that only has the Component inputs available? My Mac Mini has a Mini DisplayPort and Mini-DVI port. Thanks.

How can I connect my 2009 Mac Mini to a TV that only has the Component inputs available? My Mac Mini has a Mini DisplayPort and Mini-DVI port. Thanks.

Composite is analogue with one connector. That is why it is called composite
Component is analogue with three connections. I think one for each color
Here is the one for component. I misread composite for component
http://www.amazon.com/DVI-I-Component-DisplayPort-Female-Adapter/dp/B003OBOJC2

Iphone setting for video composite out

How can I set my Iphone in order to see composite video out; for beamer or for LCD TV

composite and component don't support mirror so they will only display output when the app being used support it
got both a composite and component cable for my ios6 iphone4 and they work great

BPEL Composite compilation issues in SOA Suite 11.1.2

I imported a SOA Composite BPEL project developed on SOA Suite 11.1.1 in SOA Suite 11.1.2. When compiling the project through ant using the "ant-sca-compile.xml" generated through JDev in 11.1.1 I am getting the following exception
java.lang.NoClassDefFoundError: oracle/fabric/common/FabricException
Caused by: java.lang.ClassNotFoundException: oracle.fabric.common.FabricException
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
Could not find the main class: oracle.soa.scac.ValidateComposite. Program will exit.
Exception in thread "main"
Have checked all my classpaths and jar's which are found to be in order. What can be the problem?

I changed some of the paths in the build file but now I am having compilation issues. It says the classpath is not set correctly. But I have included all the jar's properly in the build.xml.
Any pointers to where I might be going wrong?
D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\build\ant-sca-compile.xml
detokeniser:
scac:
[scac] Validating composite : 'D:/CommonTechServices/INT_ARCH/Construction/src/soa/CommonServices/NotificationServiceBpel/composite.xml'
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:14: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:15: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:16: package com.collaxa.cube.engine.core.map does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:21: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:100: package com.collaxa.cube.engine.core.ICubeProcess does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:107: package com.collaxa.cube.engine.core.ICubeProcess does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:148: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:148: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:148: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:390: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:390: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:401: package com.collaxa.cube.engine.core.map does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:401: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:401: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.util does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:841: package com.collaxa.cube.util does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:857: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:872: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:900: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:900: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:930: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:941: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:941: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:990: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1044: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1044: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1089: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1089: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1105: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1122: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1122: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1122: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1300: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1348: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1404: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1404: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1449: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1449: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1465: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1509: package com.collaxa.cube.engine.types.bpel does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1526: package com.collaxa.cube.engine.types.bpel does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1553: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1607: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1607: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1652: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1652: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1668: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1685: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1685: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1685: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1780: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1797: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1797: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1797: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1964: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1981: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1981: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:1981: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2154: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2208: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2208: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2253: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2253: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2269: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2286: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2286: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2286: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2381: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2398: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2398: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2398: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2565: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2582: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2582: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2582: package com.collaxa.cube does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2755: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2803: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2859: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2859: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2904: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2904: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2920: package com.collaxa.cube.engine.ext.bpel.v1.nodes does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2964: package com.collaxa.cube.engine.types.bpel does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:2981: package com.collaxa.cube.engine.types.bpel does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:3008: package com.collaxa.cube.engine.ext.bpel.v1.blocks does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine.core does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine does not exist
[scac] D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\orabpe
l\notificationservicebpel\BPEL_BIN.java:3062: package com.collaxa.cube.engine.core does not exist
[scac] Note: D:\CommonTechServices\INT_ARCH\Construction\src\soa\CommonServices\NotificationServiceBpel\SCA-INF\bpel\NotificationServiceBpel\src\
orabpel\notificationservicebpel\BPEL_BIN.java uses unchecked or unsafe operations.
[scac] Note: Recompile with -Xlint:unchecked for details.
[scac] FATAL_ERROR: location {ns:composite/ns:component[@name='NotificationServiceBpel']}(30,45): Failed to compile bpel generated classes.
[scac] failure to compile the generated BPEL classes for BPEL process "NotificationServiceBpel" of composite "default/NotificationServiceBpel!1.0
[scac] The class path setting is incorrect.
[scac] Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL pr
ocess is depending on are deployed correctly. Also verify that the run time is using the same release/version.
[scac]
BUILD FAILED

Displaying video using "Apple Composite AV Cable" to an in car DVD player

Has anyone had any success or knows of any in car dvds/screens that will enable you to display video from an iPhone/Touch. Im assuming we would need to use something similar to Apples "Apple Composite AV Cable". To be honest I really only want to show videos from my iPhone/touch... if the screens didn't have dvds I really would care..
Thx

Your best bet would be to find a car head unit with either a composite or component input. From there you would just use the appropriate cable from the Apple Store.

Iphone4 video output via composite av cable

Hi, this questions probably been asked loads of times but I haven't found an answer , hence , can someone please tell me how to switch on video out on iPhone 4 on 5.1 , I bought composite cable but no video just audio . Can any1 out there help. Thank you

iphone4 and composite and component cable don't support mirror so they
only display images when an supported app is being used like youtube or the video app and the likes
use both the composite and the component cable with my iphone4 on 5.1 and both works fine
so do my ipod touch with 5.1 and ipad2 with 5.1

? on hi8 - composite or component

Similar Messages

Maybe you are looking for