Using pim anf ile interface on motorola i760

There is a problem using pim and file interface on motorola i760 (maybe other devices olso). I wrote an application that shows the content of the phone, and it is works great on the emulator (shows the gallery). When I execute it on motorola i760, it doesn't show the gallery and the system file is empty (unless I create files). Anyone knows what is the problem?
Maybe is it motorola's problem?

this forum is sleeping..

Similar Messages

  • How can I use the color adjustments interface that shows up for camera RAW on jpeg files?

    How can I use the color adjustments interface that shows up for camera raw on other files types? The HLS controls had the secondary color adjustments (6 colors instead of the 3). Plus, it had same vibrancy and a better Curves interface. Yesterday was the first time I imported raw into Photoshop CS5 and I got that really cool interface. What is that? Can I use that on other file formats?

    Actually I am using the Tradional Chinese Version, when I try to edit the jpg file with camera raw, the system shows that there is no camera raw plug-in. The cmaera raw never work.

  • Using Report-to-Report Interface (RRI) in BEx Report Designer?

    Dear experts,
    I would like to know if it is possible to use Report-to-Report Interface in BEx Report Designer?
    From what I read from this article
    [(Creating Formatted reports using BEx Report Designer)|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00ae5173-6112-2d10-d78f-e7779d269f25?quicklink=index&overridelayout=true], the RRI capability of query is not supported in BEx report. So is it true? And are there any workarounds to enable/emulate RRI capability in BEx Report?
    Thanks in advance.
    Regards,
    Joon

    Hi Joon,
    It is possible to make RRI in BEX Report Designer by using Transaction Code - RSBBS .
    Here you need to give the Target Query and Source Query names and than you can easily connect two reports or two levels of same report.
    For further step wise description please check the below SDN document :
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/607e63d5-b56f-2c10-718f-8e33a08baa89?quicklink=index&overridelayout=true
    I hope this document helps to sort out the queries.
    Regards,
    Akanksha

  • Why do I get -18001 Errors using Customised TestStand User Interface

    Hi all
    I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
    The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
    I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
    If anyone
    has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
    Thanks
    Dave

    David,
    I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
    1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
    An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
    LabVIEW : VI is not executable.
    An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
    2) The same error will occur when
    a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
    b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
    I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
    For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
    Building The Operator Interface
    The following are steps if you are using a LabVIEW operator interface.
    1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
    Creating a LabVIEW Run-time Server
    If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
    1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
    Assembling the Test VIs for Run-Time Distribution
    This distribution process uses one of the shipping TS examples that calls LV VIs.
    1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
    2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
    3) Confirm that the sequence runs without problem.
    4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
    5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
    6) Set the target directory to be something distinct like C:\temp\AssblVIs.
    7) If you are using TestStand 2.0 skip adding Dynamic VIs
    8) Save with or without diagrams. Its your choice.
    Change Search Directories
    Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
    1) In the sequence editor select Configure>>Search Directories.
    2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
    3) Close the Edit Search Directories dialog box.
    4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
    5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
    6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
    Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
    1) In the sequence editor select Configure>>Adpaters.
    2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
    3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
    3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
    4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
    5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
    You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
    Distributing Components
    -To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
    -To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
    -You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
    Hope this helps.
    Regards,
    Kitt
    =========================================
    Title:
    Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
    The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
    Components that need to be distributed:
    TS engine
    Operator interface
    LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
    LabVIEW run-time engine
    LabVIEW test VIs
    Test sequence files
    Actions before distributing:
    It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
    Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
    Assemble the test VIs for distribution.
    Update the TestStand search directories so that the sequences reference the assembled VIs.
    Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
    Test the distribution components on the development machine.
    Enter section headings, separating each section with a line break:
    TS Engine Component
    Operator Interface Component
    LabVIEW ActiveX Server
    Configuring the LabVIEW Standard Prototype Adapter
    LabVIEW Run-time Engine Component
    Assembling your Test VIs for Distribution
    Note
    TS Engine Component
    With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
    These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
    You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
    Operator Interface Component
    You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
    LabVIEW ActiveX Server
    You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
    If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
    If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
    Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
    Configuring the LabVIEW Standard Prototype Adapter
    When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
    To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
    As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
    LabVIEW Run-time Engine Component
    If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
    You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
    Assembling your Test VIs for Distribution
    After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
    One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
    TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
    Links: See Distributing LabVIEW Test VIs below
    Note
    Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
    Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
    Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
    ==============================================

  • Is it possible to use External Defiantion in Interface Mapping?

    Hi Experts,
    Is it possible to use External defination in Interface mapping? I used this ED in Message Mapping but I am unable to use the same ED for Interface Mapping?
    In order to create Interface Mapping I need to create Message Interface and use it in Interface Mappiong?
    Thanks
    Rajeev

    Hi Rajeev,
         External definitions is for importing avaliable external DTD,XSD or WSDLs instead of creating them in XI environment maually by creating elements under datatypes,assigning them too Message types and Message Interfaces etc.Where as you fo for Imported Archives to import externally done Mapping programs like JAVA,ABAP and  XSLT mappings but not define Mesage interfaces.
    So you can create message interface import appropriate External definition into it.Later use it during interface mapping.Hope you understand it.
    Thanks,
    Ram.

  • Help! with creating a J2ME program using the http connectivity interface

    So this is what I have to do using the http connectivity interface:
    1.Creating two threads – one for communication (receiving and sending) and the other (main) thread will be for interaction with the user.
    2.The main thread will make use of three midlet forms. The first form will ask for web page address (URL) and separately for a delimiter which will separate the words in the URL document, the third form will display the ratio of all symbols on the page and the number of occurrences of the delimiter specified
    3.The second thread should perform http connectivity to the WWW, utilise the web page address supplied and connect to the appropriate web page and read its content, count all symbols on the chosen page, count the number of occurrences of the delimiter given as user input on the same form as the web page address, calculate the ratio between the two and pass this information to the first thread to display.
    I have many questions but my main concerns are:
    *1. How to communicate using HTTP interface within a thread*
    *2. What is a delimiter in the context above and how should it be implemented*
    I've been thrown in at the deep end with little programming experience with this assignment. If anyone can share a similar example or answer my concerns I'd be more than happy.
    Thanks in advance.

    thelane wrote:
    hi thanks for the response.
    As I said I have coded in other languages before, but this is a new for me in java. I needed to get it working quickley. Now I can clean up.
    I will have a look at method and see how I get on.
    ANy similiar examples would be great.
    Thanks.I can certainly give you a similar example.
    Say you have code such as this:
      int a = 10, b = 11;
      int temp = 1;
      for(int i = 2; i < a; ++i) {
       temp *= i;
      System.out.println(a + " factorial is " + temp);
      temp = 1;
      for(int i = 2; i < b; ++i) {
       temp *= i;
      System.out.println(b + " factorial is " + temp);Each section of code takes the factorial of the current variable an outputs it. The factorial code can be placed within a method to be called more easily, as such:
    public void factorial(int num) {
    int temp = 1;
    for(int i = 2; i < num; ++i) {
      temp *= i
    System.out.println(num + " factorial is " + temp);
    }Then, whenever you need to call it, you can just do so:
    int a=10,b=11,c=12;
    factorial(a);
    factorial(b);
    factorial(c);

  • Can extends keyword be used with respect to interfaces?

    can extends keyword be used with respect to interfaces?

    srinu269 wrote:
    can extends keyword be used with respect to interfaces?Yes. An interface can extend another interface:
    interface A {
        public void a();
    interface B extends A {
        public void b();
    class X implements B {
        public void b() {    
        public void a() {
    }

  • Using a specific network interface

    Hello, I would like to know how I can force Mac OS X to use a specific network interface while connecting to my mac mini (from the iMac):
    I'm connected to the internet (I mean the local network) using the airport, and I connected my iMac with the mac mini using an ethernet cable (because I want to transfer files faster, and I don't want to reboot my mini in target disk mode), but when I connect to the mini (using the "share" feature) it seems to use the airport connection. Of course I could disable the airport interface to force it to use the ethernet one (and it works) but I don't want to...
    So, how can I force a specific interface? I don't mind using a command line command to mount it initially btw.
    Thanks

    Hello, 
    Try using a different IP address range to put each interface in a different subnet. For example use 10.0.0.x and 255.255.255.0 for the Ethernet connection and 192.18.2.x and 255.255.255.0 for the Airport.
    mrtotes

  • HELP!!!  Message - (One or more applications are using the iTunes scripting interface. Are you sure you want to quit?)  How do I get this to stop?

    I bought a new Sony Vaio Laptop running Windows 8, 64bit, i7 processor.  Everytime I open iTunes and then close out, the following message occurs: (i-tunes message - One or more applications are using the iTunes scripting interface. Are you sure you want to quit?) Then it starts counting down from 20 seconds unless I just click on the (Quit) button.  How do I get this to stop?  Please be specific, I am challenged when it comes down to computers.
    Thank You

    This was extremely annoying for me, also.  I started uninstalling unneeded Sony applications to try to narrow down the problem.  It turned out not to be a Sony application... it is some functionality built into the bluetooth driver software package by Broadcom.  Uninstalling the bluetooth package (via the control panel) takes care of the problem.  Itunes also boots up way quicker.  But uninstalling it will remove features related to bluetooth and nfc.   For me, that isn't an issue, since I don't use them.  Since you said you're "computer challenged" I would probably just send an email to sony complaining about the problem.  They'll get in touch with Broadcom eventually (the manufacture of the drivers) and get the problem fixed.
    Side note: the Broadcom package is huge...  nearly 1GB in size.  Which is crazy.  I can't imagine what it does considering the size of it.  Entire operating systems can take up less storage.  Also, I have no idea how it starts an itunes plugin without placing it into the standard plugin directories.

  • Can I use the Command Line Interface on Unix?

    Hi,
    We use 9iAS on Unix. We want to use Discoverer Command Line Interface on unix to export the worksheet query result. Can anyone know how to do this? I couldn't find out the command similar to dis5usr.exe for windows version.
    Thanks.
    Richard Qiu

    Hello Richard
    You can use the Discoverer EUL Command Line for Java utility. This was released with Discoverer 10g (9.0.4).
    Please refer to the documentation for more information on how to use this command line interface: 'Oracle Discoverer EUL Command Line for Java User's Guide 10g (9.0.4), Part No. B10274_01 (PDF)' The document is available from OTN at http://otn.oracle.com/documentation/discoverer.html
    Regards
    Discoverer Product Management

  • How to use minus in a interface ?

    Hi,
    we use ODI in an application ,and want use minus in a interface.
    Can anyone please help me with this.
    viking
    Thanks in advance for your feedback.

    I find it.
    The simplest way of setting up an SQL request using the MINUS operator is to create a view containing the MINUS operator.
    The created view may then be reverse-engineered as an ODI Model Datastore and may be used in Integration Interfaces as a Source.
    If the goal is to generate the difference between a Source table and a Target table, then, the IKM Incremental Updates Knowledge Modules implement this already. That is to say :
    1. determine the differences between Source and Target Datastores
    2. apply the changes to the Target
    Note that the 11g release of ODI will allow the use of UNION/MINUS/etc. operators natively in Integration Interfaces.
    Infact, I am very disappoint to ODI.

  • Use of abstract and interface?

    when i use Abstract class or Interface.Which one is better?

    Depends on what you want to do. An interface is more general (in that it doesn't define any actual behavior) and allows you to mimic multiple inheritance (a class can implement any number of interfaces whereas it can only extend one class (abstract or otherwise)). Abstract is good if you have a common base of functionality that all of the implementers will be using.
    It's also fairly common to use both (i.e. the interface TableModel and the abstract class AbstractTableModel), so that someone who wants to completely write their own implementation is free to, while someone who wants to just extend or change the standard functionality could do that as well.

  • Use of the second interface

    Hi,
    I just configured the first interface of my C150 ESA with ip address, default gateway,listener, RAT and SMTP routes. I want my IronPort to handle mail for another domain with a totally independant netwotk (subnet and mail servers...). Can I configure the second interface the same way I configured the first one (obviously with all the good settings...;-)) ? Does it work? Is there no problem of IP or SMTP routing ?
    To be short, I want to do two "one interface configuration" scheme with my ESA (which has two physical interfaces) and not a "two interfaces configuration" scheme
    Thanks,
    Vincent

    Vincent - should be ok to do this. You have two options to do this:
    1. Use the 2nd NIC port and assign IP.
    2. Use the virtual gateway feature to get this 2nd IP address onto the network and then create a new listener on the virtual interface..this is much simpler and less work.
    Use the interfaceconfig CLI command or in the GUI to do this. Bind the new interface with it's unique DMZ ip onto the same network card as used for the previous interface (data 1 i assume).
    Option 2 is much easier
    :wink:

  • Use of declaring an interface inside an interface

    Hi
    Whats the use of declaring an interface inside an interface? I can make some guesses by my own but want to come up with some
    solid reasoning.
    So any view points are welcome
    public interface ParentInterface{
    interface ChildInterface{
    public void inside();
    thanks
    Harshit

    CeciNEstPasUnProgrammeur wrote:
    kajbj wrote:
    One reason could be that the outer interface has a method that takes a callback implementation as argument. The nested interface is in that case the contract that the callback method must implement. I don't see a reason to declare that callback interface at top level.That's what I meant. Although I see very few reasons (namely one - limited usage, which might change) not to declare it at top level, because you can't make it less visible, like one might do with an inner class implementing a public interface.
    There is no technical reason for it and no technical reason against it, and whether or not seems just to be a matter of personal taste.I agree. But it can also make it easier to navigate the code. Now people can see that the NotificationListener interface only is important if you are going to use or implement a processor (but that could kind of be done with packages as well)
    I just don't like the looks of "class Myclass implements SomeInterface.InnerInterface".Neither do I, and I would probably create an anonymous implementation that just delegates.

  • Doubts while doing  example on WDJ-Using Web Dynpro Component Interface

    Hi
    I am doing the example mentioned in the PDF file WDJ - Using Web Dynpro Component Interface Definition.
    In the PDF file its mentioned the following code inside onActionCreateDC1:
    g_Usage.createComponent("com.sap.wd.childdc1comp.ChldDC1Comp");
    wdThis.wdGetWDCompInterfInstInterface().passInfo(
    "Created Child DC 1");
    I have one query that what is com.sap.wd.childdc1comp.ChldDC1Comp?Is it the component name of DC or the package name of DC?
    I have deployed the application.When i click on button Create Child DC1 i am getting follwing exception:
    com.sap.tc.webdynpro.services.sal.deployment.api.WDDeploymentException: Failed to load deployable object part 'com.wartsila.test.ChileDC1Comp', type 'Component' of deployable object 'wartsila.com/DP_TutWDInterfaces'.
    When i click on Create Child DC2 i am getting follwing exception:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException:Failed to create delegate for custom controller com.wartsila.test1.ChildDC2CompInterfaceCfg. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
    Can anybody tell how can i solve it?
    Is it required to deploy the two child component also that is ChildDC1Comp and ChildDC2Comp?If yes then how to deploy these two child DC as when i am tryng to create application for these two component then default plug is showing blank thats why i am unable to deploy these child Dcs.
    Thanks
    Susmita

    Hi Susmita,
                      Is it required to deploy the two child component also that is ChildDC1Comp and ChildDC2Comp?
    Yes , u have to deploy both the components.
    when i am tryng to create application for these two component then default plug is showing blank thats why i am unable to deploy these child Dcs.
    U need not create an Application for deploying the component .Right Click on ur project --> Deploy.
    The problem is with ur Component, while creating a Component u should have created a Interface view and default StartUp plug.
    Just check whether u have Created the startup plug for ur interface view.
    Open the controller editor of ur interface view --> Select Plugs Tab .
    and in the plug tab , check whether u have Default Start plug (in Inbound Plugs Table).
    if there is no Default Start Plug , then click the Button New to create a Default Plug .
    in the pop up window -- select Stsrt Up and Give the name of the plug as "Default".
    After doing this , select the default plug and Right click on the plug -->copy  and Open the window Controller editor -- > select Plugs Tab --> check whether u have default plug (in Inbound plugs) in the Window controller .
    if the plug is not there , then paste the plug in the Window's Inbound Plug Table .
    Hope it helps
    Thanks and Regards

Maybe you are looking for