Unable to progress RMA.

Hello, I am unable to progress Booked RMA, checked line workflow status, its showing an error, the error name is WFENG_NOTIFICATION_PERFORMER and error message is 3120: Activity 'OEOL/184184' has no performer. Tried to run request of retry activity in error, but error still remains.

Hello Tero,
Thanks for trying out the game panel and apologies for the problem you are having playing this mission! Yes, the problem with mission #13 is due to the fact the Photoshop version you are using is the Finnish one. We are working with the development team to get an update in the next weeks, along with a new level that will bring more things to play with.
Regards,
Petar

Similar Messages

  • Unable to progress - Photoshop CC LevelUp Game

    Hello everyone.
    So my problem is this. I'm unable to progress in the 13th mission of the LevelUp for Photoshop game. In this mission, I get stuck at the Step 2 of 4, in which I am supposed to use the Quick Selection Tool to select the flower in the sample photo given by the game. However, when I do this nothing happens and I am pretty sure I have the whole white flower selected with the tool. In the earlier missions, the steps have always moved forward automatically when I've completed the criteria for a step(for example cropping an image), and this is the first time it doesn't happen.
    So, I'm tad confused. Could it be because I'm using a Finnish version of the Photoshop CC, so the LevelUp game doesn't recognize the tool? I find this option unlikely though, as I haven't had this kind of issue with the earlier missions. The Photoshop CC I am using is also the 30-day free trial version I downloaded through the Adobe Creative Cloud. Any chances this might cause the issue?
    Any ideas and advice is appreciated!
    And in case it might be of any interested. I downloaded Adobe Creative Cloud from www.adobe.com and the LevelUp Game from http://success.adobe.com/microsites/levelup/index.html

    Hello Tero,
    Thanks for trying out the game panel and apologies for the problem you are having playing this mission! Yes, the problem with mission #13 is due to the fact the Photoshop version you are using is the Finnish one. We are working with the development team to get an update in the next weeks, along with a new level that will bring more things to play with.
    Regards,
    Petar

  • HT1766 I have installed the new software onto my iPhone4; I have backup my data; I am unable to progress any further from the 3 iPhone options - I selected from iTunes b/up which worked but has stalled since requested to connect to iTunes

    I have updated the new software onto my iPhone4; I have backup my data; I am unable to progress any further from the 3 iPhone options - I selected from iTunes b/up; then the iPhone requested that I connect to iTunes which I have done and it has now stalled - nothing has happened.

    Hey Miss Apple,
    Thanks for the question. I understand you are experiencing issues with restoring your backup from iTunes. The following resources may help to resolve your issue:
    iOS: Troubleshooting backup issues in iTunes
    http://support.apple.com/kb/TS2529
    iOS: Troubleshooting update and restore issues
    http://support.apple.com/kb/TS1275
    Thanks,
    Matt M.

  • Time Machine: New Hard Drive Unable to be "formatted"?

    Dear community,
    I apologize for this post, I searched a little but aside from the current TM bug, I had a hard time finding an answer to this question. I'm also re-installing on my other laptop so I am unable to reproduce this SNAFU.
    I recently ungraded my hard drive on my mid-2008 unibody Macbook, now running 10.8.4 (first of the unibodies!). I finally outgrew my 160 gig hard drive and bought a 500 gig WD Caviar Black. I created a TM restore on my old backup, and installed the new hard drive into my mac and restored from my back up (2 days ago). This isn't like the current bug that's going on at this time, I was able to see and restore from the most recent TM point.
    Today, I had to force a close secondary to a run away process (Sophos) that was overheating and taking up my processes. I was unable to force quit, so I did a hard reset. At this point, I got the gray screen of death and was unable to progress past the Apple Logo. Safe booting proved that there wasn't any problem mounting the disk and everything would point to some sort of corrupt process.
    When I got home from work, I used disk utility repaired permissions, but was unable to progress past the Apple Logo. I used a NEW back up disk last night to back up my TM to make a restore point, and I was going to just restore the whole computer from that. Unfortunately, I had an error when I attempted to restore from the TM backup.
    Essentially, it was able to initiate the back up, but within the first 15 seconds it would stop and say something similar to "...Unable to restore from Time Machine back up, the new hard drive is unable to mount/install restore software/image. Please restart to attempt again..." Apparently, it's rare to have this problem, my googling did not find many recent occurances.
    Thus my night has been this:
    -- Disk utility x2 on the newly installed hard drive
    -- Repaired permissions and verified disk (both checked out), the first time the permissions were changed (--r--x--w to something)
    -- Reformatted the disk w/ zoroes x1
    -- Reattempt to reinstall from TM (with the same error)
    I wish I grabbed screens, but I was a bit frustrated. Right now, I am re-installing ML from the web and then attempting to use the Migration Assistant to restore from these Time Machine back ups. I had around 15 gigs of pictures moved onto the new machine last night (hence the back up last night). So, I'm pretty good with terminal, so I'm not going to be shy about poking around.
    Any suggestions? Thoughts? I am much obliged for your input.

    So, right after I try to restore I get this message,
    "An error occurred while adding a recovery system to the destination disk. Restart your computer and then try restoring again."
    This is very vague.

  • Exchange Server 2013 SP1 Standard: Installation failing can't progress

    I'm trying to install Exchange Server 2013 and I keep getting this error and I am unable to progress, I can't find any support on the issue and frankly I don't want to/can't afford to spend $500 to ask Microsoft for technical support (what kind of racket
    do they think they're running?).
    The error message:
    Error:
    The following error was generated when "$error.Clear();
    New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    " was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
    Yet, I see no PushNotifications virtual directory or anything remotely related to that on IIS or in the inetpub folders and files. If I try to resume the set-up after this error I get:
    Error:
    The following error was generated when "$error.Clear();
    New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    " was run: "The AD configuration for virtual directory 'PushNotifications' already exists in 'CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local', please remove this AD configuration manually.
    Parameter name: VirtualDirectoryName".
    And I have to remove this config using ADSI Edit, which just returns me to the first error.

    1. Prodution
    2. Just 1 DC for 1 site.
    3. Setup.EXE
    4. Matches SP1 version numbers
    5. That's just what was made available to me via MSPP, the installer doesn't see any updates?
    6. Here is the log files:
    [03/23/2015 22:06:52.0940] [1] Setup failed previously while performing the action Install. Looking for the failed task with ID ClientAccessComponent___75f8c93d15314369983d33ec0742e189.
    [03/23/2015 22:06:52.0941] [1] 131 tasks were found to run.
    [03/23/2015 22:06:52.0941] [1] Processing component 'Client Access Configuration' (Configuring Mailbox role: Client Access service.).
    [03/23/2015 22:06:52.0941] [1] Executing:
    New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    [03/23/2015 22:06:52.0955] [2] Active Directory session settings for 'New-PushNotificationsVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'SVR01.OFFICE.local', Preferred Global Catalog: 'SVR01.OFFICE.local', Preferred Domain Controllers: '{ SVR01.OFFICE.local }'
    [03/23/2015 22:06:52.0956] [2] User specified parameters: -Role:'Mailbox' -DomainController:'SVR01.OFFICE.local'
    [03/23/2015 22:06:52.0956] [2] Beginning processing New-PushNotificationsVirtualDirectory
    [03/23/2015 22:06:52.0999] [2] Searching objects "SVR02.OFFICE.local" of type "Server" under the root "$null".
    [03/23/2015 22:06:53.0066] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
    [03/23/2015 22:06:53.0068] [2] Processing object "SVR02\PushNotifications".
    [03/23/2015 22:06:56.0763] [2] The properties changed on the object '' (CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local) are: "{ MetabasePath[msExchMetabasePath]='IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications', AuthenticationMethodFlags[msExchInternalAuthenticationMethods]='Ntlm, WindowsIntegrated', AuthenticationMethodFlags[msExchExternalAuthenticationMethods]='Ntlm, WindowsIntegrated', Id[distinguishedName]='SVR02\PushNotifications (Exchange Back End)', InternalAuthenticationMethods[msExchInternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, ExternalAuthenticationMethods[msExchExternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, OrganizationId[msExchOURoot, msExchCU]='' }".
    [03/23/2015 22:06:56.0764] [2] Saving object "SVR02\PushNotifications (Exchange Back End)" of type "ADPushNotificationsVirtualDirectory" and state "New".
    [03/23/2015 22:06:57.0073] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
    [03/23/2015 22:06:57.0587] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
    [03/23/2015 22:06:57.0591] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
    Line number: 630
    Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
    [03/23/2015 22:06:58.0378] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
    [03/23/2015 22:06:58.0378] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
    Line number: 630
    Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
    [03/23/2015 22:06:58.0386] [2] Ending processing New-PushNotificationsVirtualDirectory
    [03/23/2015 22:06:58.0388] [1] The following 1 error(s) occurred during task execution:
    [03/23/2015 22:06:58.0388] [1] 0. ErrorRecord: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
    [03/23/2015 22:06:58.0389] [1] 0. ErrorRecord: System.InvalidOperationException: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it. ---> System.Runtime.InteropServices.COMException: Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
    Line number: 630
    Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
    at Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath)
    at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, String moduleName, String moduleType, ExchangeVirtualDirectory advdir)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetLiveIdBasicAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, ADExchangeServiceVirtualDirectory advdir)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServiceVirtualDirectory`1.InternalProcessComplete()
    at Microsoft.Exchange.Management.SystemConfigurationTasks.NewPushNotificationsVirtualDirectory.InternalProcessComplete()
    at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
    --- End of inner exception stack trace ---
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
    [03/23/2015 22:06:58.0389] [1] [ERROR] The following error was generated when "$error.Clear();
    New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    " was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
    [03/23/2015 22:06:58.0389] [1] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
    [03/23/2015 22:06:58.0389] [1] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
    Line number: 630
    Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
    [03/23/2015 22:06:58.0390] [1] [ERROR-REFERENCE] Id=ClientAccessComponent___75f8c93d15314369983d33ec0742e189 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [03/23/2015 22:06:58.0390] [1] Setup is stopping now because of one or more critical errors.
    [03/23/2015 22:06:58.0390] [1] Finished executing component tasks.
    [03/23/2015 22:06:58.0406] [1] Ending processing Install-ClientAccessRole
    It says it can not log on with the supplied details, but the account is an Administrator account with full privileges so I can't see why this would be the case.

  • Unable to boot Powerbook after updating to 10.4.9

    Hi Folks,
    Really hope someone can help me. I have a 12 inch Powerbook , G4, 1.5 GHz. 1.25 Gb RAM, 100 Gb hard drive, Superdrive, running OS X 10.4 Tiger.
    I purchased the machine in mid 2005 and have had no problem reunning it. The computer came with OS X 10.4.0 installed. I have regularly updated it as Software Update recommends.
    Several days ago, the computer crashed while using Safari to browse the internet. When I attempted to reboot I prgresed through the grey screen with the spinning cog to the Mac OS X startup screen and ended up freezing at a blank blue screen with a mouse curser. After much fiddling around with Disk Utility and the install disk's I was able to re-install 10.4.0 from the disk and eventually got the machine restarted. It was slow and regularly crashed whenever I ran programs, especially sofware update. I manually downloaded the OS X 10.4.9 combo update for Power PC and installed it. Was very slow going and hung up at the end for a long time but eventually seemed to work and the computer reset but froze at the grey screen. Since then I have been unable to progress past the initial grey screen with the apple logo. No spinning cog, no blue screen. I am unable to start it in safe mode, single user mode, verbose mode or even pressing down C to get to the disk utility. When I restart it with the installation disk in the drive, I am able to get to the install menu and run disk utility from there but it has a disk management tool error when attempting to verify or repair definitions. Repair Disk says there are no errors. I have reinstalled 10.4.0 from the disk three times but no change. I have about 2Gb of space free and the rest is filled with stuff I really don't want to delete. Plus I can't get access to the hard drive to delete things anyway.
    Any suggestions? Safe mode doesn't work, Verbose or single user dont work, disk utilities don't help and I don't have another Mac I can do a Targeted restart from. Prefer not to do an erase and install as I'll lose 93 Gb worth of files.

    No backup, mate? Tsk, tsk. Now that I got that out of the way, on to the problem.
    First thing to try is zapping the PRAM: restart, holding down the CMDOPT+PR keys until you get at least three bongs, then let go.
    Boot the machine with the Apple Hardware Test disk that came with the machine and run the extended tests. If the machine passes those, boot the machine normally and see if that fixes things.
    If these don't work, I strongly suggest getting an external FireWire HD, boot with the install disks, use Disk Utility to format the HD, selecting Mac OS Extended, click on Options, select zero out data, and click on the erase button. When that's finished, install Tiger onto it, and see if it successfully boots the machine.
    Enough for now, that should keep you busy for awhile. Come back with what works or doesn't work. Time to hit the sack.

  • Unable to sign in with my apple ID

    I have been trying to sign in with my Apple ID and password.
    I am taken to review the account, which means clicking through a splash, agreeing to some T & C's, and then a screen to add info like year of birth.
    When I try to submit the final screen there, I see the message "An Error Occurred" and I am unable to progress. I have tried this a few times - and I'd really like to start buying films with it.
    Any ideas or help?

    Ah! I've got it - and this is a bit silly. I closed down iTunes completely. Restarted, and tried the sign in again. This time also taking it slowly between each one.
    I am now past that screen in the review process and have completed the setup.
    So - if you get stuck with this - close down iTunes completely, open it, and try it again. I thoroughly recommend leaving it for 10 minutes too.

  • ONLINE MODE일 경우 RMA RECEIPT시 RVTPT-020 ERROR 발생시 해결 방법

    제품 : MFG_PO     
    작성날짜 : 2005-02-03     
    ONLINE MODE일 경우 RMA RECEIPT시 RVTPT-020 ERROR 발생시 해결 방법
    ==================================================================
    PURPOSE
    RCV: Processing Mode = On-line 인 경우 종종 RMA receipt시 아래와 같은
    error가 발생하는데 이 note를 통해 그 해결안을 찾을 수 있다.
    RMA Receipts error: RVTPT-020 Subroutine rvtoe_RmaPushApi()
    - EONT_PRICING_ERROR
    Symptom: (ERR_TEXT=QP_PREQ_PUB.Initialize_Constants ORA-6508:
    PL/SQL could not find program unit being called) returned error
    Oracle Purchasing - Version: 11.5.3 to 11.5.8
    Problem Description
    RCV: Processing Mode가 'On-line'인 경우 RMA order receiving을 할때
    system은 아래와 같은 error message를 종종 display 한다.
    ============================================================
    RMA Receipts error: RVTPT-020 Subroutine rvtoe_RmaPushApi()
    - EONT_PRICING_ERROR
    Symptom: (ERR_TEXT=QP_PREQ_PUB.Initialize_Constants ORA-6508:
    PL/SQL could not find program unit being called) returned error
    ============================================================
    Receiving Transaction Manager를 bounce 하면 문제가 해결은 되고, 같은
    RMA line을 다시 receive 받을 수 있게 된다.
    이 문제는 Processing Mode가 'IMMEDIATE'이거나 'BATCH'인 경우에는 발생하
    지 않으며 오직 'ON-LINE'인 경우에만 종종 발생한다.
    "Build Sourcing Rules"(이후 version에선 "Build Attribute Mapping'으로
    이름 변경) program이 이 문제의 원인이다.
    QP의 concurrent program "Build Sourcing Rules"가 몇 개의 package를
    invalid 상태로 만들어, invalid/changed 상태의 QP objects를 OM이 call
    할 경우 error가 나타나게 된다.
    이러한 Invalids의 결과는 ON-Line mode시의 RMA receipts에서 나타나게
    된다. 가장 신속한 Workaround는 Receiving Transaction Manager를 bounce
    하는 것이다.
    Workaround
    Bounce Receiving Transaction Manager.
    Solution Description
    Patch 2875824와 관련 pre-requisites patch를 적용한다.
    이 patch는 다음과 files version을 upgrade 한다.
    QPXCTRLB.pls - 115.0 ()
    QPXPSRCB.pls - 115.69.1158.2 ()
    qptab.odf - 115.90 ()
    QPXCTRLS.pls - 115.8
    QPXPSRCS.pls - 115.28
    QPXVATTS.pls - 115.5
    QPXVBSTS.pls - 115.4
    qprunbld.sql - 115.7
    이 patch는 RCV: Processing Mode = On-Line 을 사용시 receiving
    transactions을 다시 실행하기 위해 Receiving Transaction Manager를 다시
    bounce할 필요가 없게 할 것이다.
    이 issue는 11i.OM_PF.I(11.5.9) 에서 해결이 되었다.
    or
    Bounce Receiving Transaction Manager:
    1. $ps -ef | grep RCVOLTM (Running 중인 processes의 수를 조회)
    2. Deactivate Receiving Transaction Manager
    (System Administrator > Concurrent > Manager > Administer)
    3. $ps -ef | grep RCVOLTM (Running 중인 processes가 없을때까지 반복)
    4. Restart Receiving Transaction Manager
    Reference Documents
    262052.1 : RVTPT-020 UNABLE TO DO RMA RECEIVING ONLINE

  • HT203527 Unable to purchase 20GB 60 INR per month Plan

    Hi,
    I want to purchase 20GB INR 60 per month plan on icloud and followed below steps :
    In Icloud - > Storage -> Buy More Storage - > I have selected 20GB -> and in next screen I have entered password and clicked on Buy -> But it is again redirecting to page
    Please let me know why am facing this issue, am still able to login into icloud from chrome browser
    Thanks,
    Sunil

    Hello inoothi,
    Welcome to the Apple Support Communities!
    I understand that you are attempting to purchase iCloud storage, but are essentially in a loop unable to progress. It appears that you are attempting this purchase on your Windows computer; have you tried to purchase this storage on your iPhone with the same result? If you cannot purchase from your iPhone as well, please let me know. 
    iCloud storage upgrades and downgrades - Apple Support
    Have a great day,
    Joe

  • Problem with Dynamically accessing EJB Class objects in WL 7.0 SP1

    I am trying to build a component which has the ability to instantiate and execute
    an known EJB method on the fly.
    I have managed to build the component but when I try and execute it I get a ClassNotFoundException.
    I know that the EJB I am trying to invoke is deployed and available on the server,
    as I can see it in the console, I also seen to have been able to get the remote
    interface of the object, my problem occurs when I try and access the class object
    so I can perform a create on the object and then execute my method
    The code I have written is below:
    private Object getRemoteObject(Context pCtx, String pJNDIName, String pHomeBean)
    throws Exception {
         String homeCreate = "create";
         Class []homeCreateParam = { };
         Object []homeCreateParamValues = {};           
    try {  
    //This call seems to work and doesn't throw an exception     
    Object home = pCtx.lookup(pJNDIName);
    //However this call throws a java.lang.ClassNotFoundException
    Class homeBean = Class.forName(pHomeBean);
    Method homeCreateMethod = homeBean.getMethod(homeCreate,homeCreateParam);
    return homeCreateMethod.invoke(home, homeCreateParamValues);
    } catch (NamingException ne) {             
    logStandardErrorMessage("The client was unable to lookup the EJBHome.
    Please make sure ");
    logStandardErrorMessage("that you have deployed the ejb with the JNDI
    name "+pJNDIName+" on the WebLogic server ");
    throw ne;
    } catch (Exception e) {
    logStandardErrorMessage(e.toString());
    throw e;     
    Any advice would be really appreciated, I'm fast running out of ideas, I suspect
    it has something to do with the class loader but I'm not sure how to resolve it
    Regards
    Jo Corless

    Hello Joanne,
    Congratulations! I'm very happy that you've managed to fix your problem. It's
    always essential to understand how to package applications when deploying on BEA
    WebLogic. Usually, by throwing everything into an EAR file solves just about all
    the class loader problems. :-) Let us know if you have any further problems that
    we can assist you with.
    Best regards,
    Ryan LeCompte
    [email protected]
    http://www.louisiana.edu/~rml7669
    "Joanne Corless" <[email protected]> wrote:
    >
    >
    I've fixed it!!!!!!!!
    Thanks to everyone who gave me help!!!!
    The class loader was the culprit which is what I suspected all along.
    As soon
    as I put the 2 jar files I was using into an EAR file the problem went
    away!!!!!
    Thanks again
    Jo Corless
    "Ryan LeCompte" <[email protected]> wrote:
    Hello Joanne,
    As Mr. Woollen mentioned, I also believe it's a problem with the class
    loader.
    You need to be careful how you arrange your EJBs, because WebLogic has
    a specific
    method in which it loads classes in an EAR, JAR, and WAR file(s). Please
    refer
    to http://dev2dev.bea.com/articles/musser.jsp for more information about
    BEA WebLogic
    class loading mechanisms and caveats. Also, try printing out the various
    methods
    that are available on the object that was returned to you via reflection.
    For
    example, use the getMethods() method, which returns an array of Method
    objects
    that you can subsequently cycle through and print out the various method
    names.
    This way you can discover if the class found/returned to you is indeed
    the one
    you intend to locate.
    Hope this helps,
    Ryan LeCompte
    [email protected]
    http://www.louisiana.edu/~rml7669
    Rob Woollen <[email protected]> wrote:
    I believe the issue is the home interface class for this EJB is not
    available in the class loader which is doing the reflection.
    If you do:
    getClass().getClassLoader().loadClass(homeInterfaceClassName)
    I suspect it will fail. Reflection still requires that the class be
    loadable.
    -- Rob
    Joanne Corless wrote:
    Hi Slava,
    If I make my code look like you describe below I get a compliationerror telling
    me that
    home.getMethod() is not recognised (no such method)
    If I change it slightly and use
    Method homeCreateMethod =
    home.getClass().getMethod(homeCreate,homeCreateParam);
    The code will compile OK but when executed it still throws a NoSuchMethodException
    Any ideas ?
    Thanks for your help so far
    Regards
    Jo Corless
    Your code should look like
    Object home = pCtx.lookup(pJNDIName);
    Method homeCreateMethod =
    home.getMethod(homeCreate,homeCreateParam);
    return homeCreateMethod.invoke(home, homeCreateParamValues);
    Regards,
    Slava Imeshev
    "Joanne Corless" <[email protected]> wrote in message
    news:[email protected]...
    Hi Ryan,
    I also wanted to mention that if you do a "header search" in this
    particular
    newsgroup
    with the search query as "reflection", you will see many previousmessages
    regarding
    reflection and EJBs. I believe you could learn a lot from thedifficulties
    that
    others have faced and solved.I tried that and although there was a number of similar cases noneof them
    actually
    seem to fix my issue. Thanks for the suggestion though
    Are the EJBs that you are trying to access accessible via your
    system
    classpath?
    Try to avoid having them accessible via the main system classpath,and
    only bundle
    them in your appropriate EJB jar files (contained in an EAR file,for
    example).Maybe I should have laid the problem out a little clearer.
    I have a number of EJB's bundled up in a JAR file which is hot deployedto
    the
    server. Within this first JAR file is an EJB (SSB) component that
    needs
    to
    be
    able to invoke a known method on another EJB. This second EJB may
    or
    may
    not be
    within the first JAR file but it also will be hot deployed.
    The component trying to invoke the method on the 2nd EJB has to
    be
    able to
    create
    an instance of the 2nd EJB without actually knowing anything bar
    a
    JNDI
    Name which
    is passed in at runtime.
    I can get as far as doing the
    Object home = pCtx.lookup(pJNDIName);
    This returned a class with the name
    "com.csc.edc.projects.allders.httppostoffice.postman.PostmanBean_mp8qy2_Home
    Impl_WLStub"
    My problem seems to occur when I try and invoke the create method
    Method homeCreate = home.getClass().getMethod("create", new Class[0]);
    My code throws a java.lang.NoSuchMethodException at this point so
    I
    am
    unable
    to progress to the next step of :
    Object bean = homeCreate.invoke(home, null);
    So I can return the instantiated bean back to the calling client.
    Why am I getting the NoSuchMethodException, is is because I am gettinga
    stub
    back rather than the home interface and if so how do I get the truehome
    interface
    from the bean
    Thanks in advance
    Jo Corless

  • Move Apple mail 2.07 account directory to another location/partition

    Hi all,
    Was bugged by few problems after the update to 10.4.6.
    As follows:
    All my emails disappear after it. Knowing that i previous did some customising of moving to different folder, i try to import it in and everything is there under the folder Import. Solved on my first problem.
    I have since drag all folders from Import to the main and deleted off the folder Import.
    While i starting to add accounts into the new Mail 2.07, i faced another problem. I am unable to set the account directory for the account i have created. This is bugging me as i have all my emails on the other partition and it contains 2GB of all my important emails i need. though i have successfully imported them into Mail 2.07, i wish to move the mail to the other partition so i can have a easier time not needing to housekeep now and then since most of my emails have large attachments with them.
    I tried accessing Andrew Pontious's helpfultiger tips after some searching within this discussion and found that his site is no longer functioning.
    Have also tried the other method of adding a new account without the assistance by pressing "Option" when clicking the "+" icons and the Mail preference panel just hang on me without anything shown. Forcing me to do a force quit on Mail and try again and again. And still, after last night of countless tries, i still unable to progress any further.
    Help needed :
    1. Any ways to push my mail to other partition other than setting the account directory within the account setting to the other partition?
    2. If able to customise the default folder from /Library/Mail to another partition, that will be nicer.
    3. If no way to set the default account directory, possible to customise a folder which is located at the other partition and create a rule to move the mails into that folder?
    Pardon me for this lengthy post as i have been bugged by few other problems other than this Mail and desperately needing help to get my Mail back in order to carry on working.
    N.B: I have tested my iMac hardware, did a disk verification and permission repair and everything is doing fine.

    I must be missing something here, because this is
    starting to make little sense to me. In my previous
    reply I did give you step-by-step instructions
    to accomplish what you want. Have you tried it? Is
    there something there you didn't understand? If
    replacing the HOME/Library/Mail folder with an
    alias doesn't work, I'm pretty sure it can be done
    using Unix symbolic links instead, but I believe
    Finder aliases are preferable here if they work (and
    I believe they do).
    Why on Earth would someone prefer to play with more
    involved hacks that only provide a partial solution
    and that are more likely to cause problems?
    Never doubted your suggestion and was gladful for it.
    However, i tried and my mail didn't show up with those personal folders which i created to categorize the chunk of emails i got. Ended up i reverse the process and everything is back in Mail again.
    One thought after last night of trying, com.apple.mail.plist.
    Will try to see if i can edit the default location ~/Library/Mail to my preferred location on the other partition by means of editing the plist.
    Will update if any result.
    And to all who have responded in this thread, sincerely thank all of you for the time and effort spent to help me out. Thank You!

  • BT Infinity Insufficient bandwidth to run iPlayer ...

    Having problems with BT Infinity.  Despite new modem,  speed is slower than ever.
    Support line link up took 30 minutes but operator unable to progress the matter and put us in a queue to the engineers - nearly 2 hours later I hung up in despair.
    Emailed a complaint to BT using their recommended procedure and 24 hours later I have not had a reply as promised in the blurb.
    I would like compensation for 2 weeks of slow Internet and for a ruined afternoon.  Most important of all I want someone on my case to fix the BT Infinity so that I receive the service I pay top dollar for.
    Why must such a prestigious company be so remote and insensitive.  I have never been so badly treated in my life.
    To add insult to injury we took part in a post phone-call survey with options for satisfaction of 1 through 7 with the latter being the worst.  We felt that 7 was appropriate in this case but the system would not accept this score.  ???????

    Hi again
    Ran the tests you suggested - results are listed below
    Download Speeds
    36 Mbps
    Upload Streaming
    8.35 Mbps
    Assured Rate Test
    34.2 Mbps
    Video Service Quality Test
    passed
    Why would we experience streaming problems with such, apparantly, good test results?
    Your help has been much appreciated.

  • Transferring files from Windows PC to MacBook Pro

    I've been trying to transfer files from my Windows PC to my MacBook Pro using the Migration Assistant. Both the computers are on the same Wi-Fi network. The MacBook however is unable to identify the WIndows PC and I am unable to progress further. What am I doing wrong?

    Does this help?
    http://support.apple.com/kb/PH13882?viewlocale=en_US
    Note: Wireless data transfer is slow compared to a hardwire connection.
    Ciao.

  • How to access my configs n customization in my project

    Hi Gurus,
    I am a learner...n i have done all my configs n customization by creating a new Project in my IDES system.
    However, when i am trying to use them through Easy Access Screen, i am unable to use those configs.
    For Ex. I have configured new Sales District, Legal Statuses, Customer Classification etc. but when i am creating a new Customer Master through XD01, all these customizations don't appear.
    Please tell what more i need to do to start using it in my project.
    Thanks,
    Khushal Agrawal

    Dear Laxmipathi Sir,
    Well Yes..actually....i have made all the fields as above madatory n have customized them.
    But while creating customer master, when i go for matchcode for say in Sales District...it does not displays any entries. Neither can i enter any text their n since i made it REQUIRED field, i am unable to progress further...so i need to eixt.
    Is it so beacuse i have created a Project for myself. Earlier it used to take.
    Please suggest a solution.
    Thanks
    Khushal Agrawal

  • Error Null Databinding context encountered -WSDL to Java webservice convert

    HI,
    I have been trying to generate service and client from WSDL using Jdeveloper11 and im unable to progress on this particular WSDL, i was succesfull in creating the client and service for a sample Apache WSDL using the Jdeveloper. If anyone can point out the issue in this WSDL or is there a bug in Jdeveloper when handling complex type? i attach the WSDL that i used, now note that the WSDL calls for another WSDL import witin it, if i comment out the import and its bindings im able to proceed,
    WSDL-1
    <!-- Tigerstripe : Operations relating to Alarm -->
    <wsdl:operation name="getAlarmsByKeys">
    <wsdl:input name="getAlarmsByKeysRequest" message="fmWS-v1-0:getAlarmsByKeysRequest" />
    <wsdl:output name="getAlarmsByKeysResponse" message="fmWS-v1-0:getAlarmsByKeysResponse" />
    <wsdl:fault name="getAlarmsByKeysException" message="fmWS-v1-0:getAlarmsByKeysException" />
    </wsdl:operation>
    <wsdl:operation name="getAlarmsByTemplate">
    <wsdl:input name="getAlarmsByTemplateRequest" message="fmWS-v1-0:getAlarmsByTemplateRequest" />
    <wsdl:output name="getAlarmsByTemplateResponse" message="fmWS-v1-0:getAlarmsByTemplateResponse" />
    <wsdl:fault name="getAlarmsByTemplateException" message="fmWS-v1-0:getAlarmsByTemplateException" />
    </wsdl:operation>
    <wsdl:operation name="queryAlarms">
    <wsdl:input name="queryAlarmsRequest" message="fmWS-v1-0:queryAlarmsRequest" />
    <wsdl:output name="queryAlarmsResponse" message="fmWS-v1-0:queryAlarmsResponse" />
    <wsdl:fault name="queryAlarmsException" message="fmWS-v1-0:queryAlarmsException" />
    </wsdl:operation>
    <!-- Tigerstripe : Operations for Interface artifact methods ( JVTAlarmCreationSession ) -->
    <wsdl:operation name="getAlarmSpecificInfoTypes">
    <wsdl:input
    name="getAlarmSpecificInfoTypesRequest"
    message="fmWS-v1-0:getAlarmSpecificInfoTypesRequest" />
    <wsdl:output
    name="getAlarmSpecificInfoTypesResponse"
    message="fmWS-v1-0:getAlarmSpecificInfoTypesResponse" />
    <wsdl:fault
    name="getAlarmSpecificInfoTypesException"
    message="fmWS-v1-0:getAlarmSpecificInfoTypesException" />
    </wsdl:operation>
    <wsdl:operation name="getVersion">
    <wsdl:input
    name="getVersionRequest"
    message="fmWS-v1-0:getVersionRequest" />
    <wsdl:output
    name="getVersionResponse"
    message="fmWS-v1-0:getVersionResponse" />
    <wsdl:fault
    name="getVersionException"
    message="fmWS-v1-0:getVersionException" />
    </wsdl:operation>
    <wsdl:operation name="createAlarms">
    <wsdl:input
    name="createAlarmsRequest"
    message="fmWS-v1-0:createAlarmsRequest" />
    <wsdl:output
    name="createAlarmsResponse"
    message="fmWS-v1-0:createAlarmsResponse" />
    <wsdl:fault
    name="createAlarmsException"
    message="fmWS-v1-0:createAlarmsException" />
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="JVTAlarmCreationSessionSoapBinding"
    type="fmWS-v1-0:JVTAlarmCreationSessionWSPort">
    <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http" />
    <!-- Tigerstripe : Bindings relating to Alarm -->
    <wsdl:operation name="getAlarmsByKeys">
    <soap:operation soapAction="getAlarmsByKeys" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name="getAlarmsByKeysException">
    <soap:fault name="getAlarmsByKeysException" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="getAlarmsByTemplate">
    <soap:operation soapAction="getAlarmsByTemplate" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name="getAlarmsByTemplateException">
    <soap:fault name="getAlarmsByTemplateException" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="queryAlarms">
    <soap:operation soapAction="queryAlarms" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name="queryAlarmsException">
    <soap:fault name="queryAlarmsException" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="getAlarmSpecificInfoTypes">
    <soap:operation soapAction="getAlarmSpecificInfoTypes" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name ="getAlarmSpecificInfoTypesException">
    <soap:fault name ="getAlarmSpecificInfoTypesException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="getVersion">
    <soap:operation soapAction="getVersion" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name ="getVersionException">
    <soap:fault name ="getVersionException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="createAlarms">
    <soap:operation soapAction="createAlarms" style="document" />
    <wsdl:input>
    <soap:body parts="parameters" use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body parts="parameters" use="literal" />
    </wsdl:output>
    <wsdl:fault name ="createAlarmsException">
    <soap:fault name ="createAlarmsException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>
    <!-- Binding for the Notification Producer -->
    <!-- <wsdl:binding name="NotificationProducerSoapBinding" type="wsnt:NotificationProducer">
    <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http" />-->
    <!-- =========== NotificationProducer Specific ============== -->
    <!-- <wsdl:operation name="Subscribe">
    <soap:operation soapAction="Subscribe" style="document"/>
    <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="SubscribeCreationFailedFault">
    <soap:fault name="SubscribeCreationFailedFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="TopicExpressionDialectUnknownFault">
    <soap:fault name="TopicExpressionDialectUnknownFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="InvalidFilterFault">
    <soap:fault name="InvalidFilterFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="InvalidTopicExpressionFault">
    <soap:fault name="InvalidTopicExpressionFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="TopicNotSupportedFault">
    <soap:fault name="TopicNotSupportedFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="InvalidProducerPropertiesExpressionFault">
    <soap:fault name="InvalidProducerPropertiesExpressionFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="InvalidMessageContentExpressionFault">
    <soap:fault name="InvalidMessageContentExpressionFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="UnacceptableInitialTerminationTimeFault">
    <soap:fault name="UnacceptableInitialTerminationTimeFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="UnrecognizedPolicyRequestFault">
    <soap:fault name="UnrecognizedPolicyRequestFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="UnsupportedPolicyRequestFault">
    <soap:fault name="UnsupportedPolicyRequestFault" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="NotifyMessageNotSupportedFault">
    <soap:fault name="NotifyMessageNotSupportedFault" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="GetCurrentMessage">
    <soap:operation soapAction="GetCurrentMessage" style="document" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="TopicExpressionDialectUnknownFault">
    <soap:fault name="TopicExpressionDialectUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="InvalidTopicExpressionFault">
    <soap:fault name="InvalidTopicExpressionFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="TopicNotSupportedFault">
    <soap:fault name="TopicNotSupportedFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="NoCurrentMessageOnTopicFault">
    <soap:fault name="NoCurrentMessageOnTopicFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="MultipleTopicsSpecifiedFault">
    <soap:fault name="MultipleTopicsSpecifiedFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>-->
    <!-- Binding for the SubscriptionManager -->
    <!-- <wsdl:binding name="SubscriptionManagerSoapBinding" type="wsnt:PausableSubscriptionManager">
    <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http" />-->
    <!-- ========= SubscriptionManager specific operations ====== -->
    <!-- <wsdl:operation name="PauseSubscription">
    <soap:operation soapAction="PauseSubscription" style="document" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="PauseFailedFault">
    <soap:fault name="PauseFailedFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="Renew">
    <soap:operation soapAction="Renew" style="document" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="UnacceptableTerminationTimeFault">
    <soap:fault name="UnacceptableTerminationTimeFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="Unsubscribe">
    <soap:operation soapAction="Unsubscribe" style="document" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="UnableToDestroySubscriptionFault">
    <soap:fault name="UnableToDestrySubscriptionFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="ResumeSubscription">
    <soap:operation soapAction="ResumeSubscription" style="document" />
    <wsdl:input>
    <soap:body use="literal" />
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" />
    </wsdl:output>
    <wsdl:fault name="ResourceUnknownFault">
    <soap:fault name="ResourceUnknownFault" use="literal" />
    </wsdl:fault>
    <wsdl:fault name="ResumeFailedFault">
    <soap:fault name="ResumeFailedFault" use="literal" />
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>-->
    <wsdl:service name="JVTAlarmCreationSessionWebService">
    <wsdl:port name="JVTAlarmCreationSessionWSPort"
    binding="fmWS-v1-0:JVTAlarmCreationSessionSoapBinding">
    <soap:address location="http://localhost/JVTAlarmCreationSessionWebService/JVTAlarmCreationSession" />
    </wsdl:port>
    <!--wsdl:port name="NotificationProducerPort" binding="wsnt:NotificationProducerSoapBinding">
    <soap:address location="http://localhost/JVTAlarmCreationSessionWebService/NotificationProducer"/>
    </wsdl:port>
    <wsdl:port name="SubscriptionManagerPort" binding="wsnt:SubscriptionManagerSoapBinding">
    <soap:address location="http://localhost/JVTAlarmCreationSessionWebService/SubscriptionManager"/>
    </wsdl:port-->
    </wsdl:service>
    </wsdl:definitions>
    WSDL-2 imported in the above WSDL
    <?xml version="1.0" encoding="utf-8"?>
    <!--
    OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.
    OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.
    Copyright (C) OASIS Open (2004-2006). All Rights Reserved.
    This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.
    The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
    This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
    -->
    <wsdl:definitions name="WS-BaseNotification"
    targetNamespace="http://docs.oasis-open.org/wsn/bw-2"
    xmlns:wsntw="http://docs.oasis-open.org/wsn/bw-2"
    xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"
    xmlns:wsa="http://www.w3.org/2005/08/addressing"
    xmlns:wsrf-rw="http://docs.oasis-open.org/wsrf/rw-2"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <!-- ========================== Imports =========================== -->
    <wsdl:import
    namespace="http://docs.oasis-open.org/wsrf/rw-2"
    location="rw-2.wsdl"/>
    <!-- ===================== Types Definitions ====================== -->
    <wsdl:types>
    <xsd:schema elementFormDefault="qualified">
    <xsd:import
    namespace="http://docs.oasis-open.org/wsn/b-2"
    schemaLocation="b-2.xsd"/>
    </xsd:schema>
    </wsdl:types>
    <!-- ================ NotificationConsumer::Notify ================
    Notify(
    NotificationMessage
    (SubscriptionReference, TopicExpression, ProducerReference,
    Message)*
    returns: n/a (one way)
    -->
    <wsdl:message name="Notify">
    <wsdl:part name="Notify" element="wsnt:Notify"/>
    </wsdl:message>
    <!-- ============== NotificationProducer::Subscribe ===============
    Subscribe(
    (ConsumerEndpointReference, [Filter], [SubscriptionPolicy],
    [InitialTerminationTime])
    returns: WS-Resource qualified EPR to a Subscription
    -->
    <wsdl:message name="SubscribeRequest" >
    <wsdl:part name="SubscribeRequest"
    element="wsnt:Subscribe"/>
    </wsdl:message>
    <wsdl:message name="SubscribeResponse">
    <wsdl:part name="SubscribeResponse"
    element="wsnt:SubscribeResponse"/>
    </wsdl:message>
    <wsdl:message name="SubscribeCreationFailedFault">
    <wsdl:part name="SubscribeCreationFailedFault"
    element="wsnt:SubscribeCreationFailedFault" />
    </wsdl:message>
    <wsdl:message name="TopicExpressionDialectUnknownFault">
    <wsdl:part name="TopicExpressionDialectUnknownFault"
    element="wsnt:TopicExpressionDialectUnknownFault" />
    </wsdl:message>
    <wsdl:message name="InvalidFilterFault">
    <wsdl:part name="InvalidFilterFault"
    element="wsnt:InvalidFilterFault" />
    </wsdl:message>
    <wsdl:message name="InvalidProducerPropertiesExpressionFault">
    <wsdl:part name="InvalidProducerPropertiesExpressionFault"
    element="wsnt:InvalidProducerPropertiesExpressionFault" />
    </wsdl:message>
    <wsdl:message name="InvalidMessageContentExpressionFault">
    <wsdl:part name="InvalidMessageContentExpressionFault"
    element="wsnt:InvalidMessageContentExpressionFault" />
    </wsdl:message>
    <wsdl:message name="UnrecognizedPolicyRequestFault">
    <wsdl:part name="UnrecognizedPolicyRequestFault"
    element="wsnt:UnrecognizedPolicyRequestFault" />
    </wsdl:message>
    <wsdl:message name="UnsupportedPolicyRequestFault">
    <wsdl:part name="UnsupportedPolicyRequestFault"
    element="wsnt:UnsupportedPolicyRequestFault" />
    </wsdl:message>
    <wsdl:message name="NotifyMessageNotSupportedFault">
    <wsdl:part name="NotifyMessageNotSupportedFault"
    element="wsnt:NotifyMessageNotSupportedFault" />
    </wsdl:message>
    <wsdl:message name="UnacceptableInitialTerminationTimeFault">
    <wsdl:part name="UnacceptableInitialTerminationTimeFault"
    element="wsnt:UnacceptableInitialTerminationTimeFault"/>
    </wsdl:message>
    <!-- ========== NotificationProducer::GetCurrentMessage ===========
    GetCurrentMessage(topicExpression)
    returns: a NotificationMessage (xsd:any)
    -->
    <wsdl:message name="GetCurrentMessageRequest">
    <wsdl:part name="GetCurrentMessageRequest"
    element="wsnt:GetCurrentMessage"/>
    </wsdl:message>
    <wsdl:message name="GetCurrentMessageResponse">
    <wsdl:part name="GetCurrentMessageResponse"
    element="wsnt:GetCurrentMessageResponse"/>
    </wsdl:message>
    <wsdl:message name="InvalidTopicExpressionFault">
    <wsdl:part name="InvalidTopicExpressionFault"
    element="wsnt:InvalidTopicExpressionFault" />
    </wsdl:message>
    <wsdl:message name="TopicNotSupportedFault">
    <wsdl:part name="TopicNotSupportedFault"
    element="wsnt:TopicNotSupportedFault" />
    </wsdl:message>
    <wsdl:message name="MultipleTopicsSpecifiedFault">
    <wsdl:part name="MultipleTopicsSpecifiedFault"
    element="wsnt:MultipleTopicsSpecifiedFault" />
    </wsdl:message>
    <wsdl:message name="NoCurrentMessageOnTopicFault">
    <wsdl:part name="NoCurrentMessageOnTopicFault"
    element="wsnt:NoCurrentMessageOnTopicFault" />
    </wsdl:message>
    <!-- ========== PullPoint::GetMessages ===========
    GetMessages(MaximumNumber)
    returns: NotificationMessage list
    -->
    <wsdl:message name="GetMessagesRequest">
    <wsdl:part name="GetMessagesRequest"
    element="wsnt:GetMessages"/>
    </wsdl:message>
    <wsdl:message name="GetMessagesResponse">
    <wsdl:part name="GetMessagesResponse"
    element="wsnt:GetMessagesResponse"/>
    </wsdl:message>
    <wsdl:message name="UnableToGetMessagesFault">
    <wsdl:part name="UnableToGetMessagesFault"
    element="wsnt:UnableToGetMessagesFault"/>
    </wsdl:message>
    <!-- ========== PullPoint::DestroyPullPoint ===========
    DestroyPullPoint()
    returns: void
    -->
    <wsdl:message name="DestroyPullPointRequest">
    <wsdl:part name="DestroyPullPointRequest"
    element="wsnt:DestroyPullPoint"/>
    </wsdl:message>
    <wsdl:message name="DestroyPullPointResponse">
    <wsdl:part name="DestroyPullPointResponse"
    element="wsnt:DestroyPullPointResponse"/>
    </wsdl:message>
    <wsdl:message name="UnableToDestroyPullPointFault">
    <wsdl:part name="UnableToDestroyPullPointFault"
    element="wsnt:UnableToDestroyPullPointFault"/>
    </wsdl:message>
    <!-- ========== PullPoint::CreatePullPoint ===========
    CreatePullPoint()
    returns: PullPoint (wsa:EndpointReference)
    -->
    <wsdl:message name="CreatePullPointRequest">
    <wsdl:part name="CreatePullPointRequest"
    element="wsnt:CreatePullPoint"/>
    </wsdl:message>
    <wsdl:message name="CreatePullPointResponse">
    <wsdl:part name="CreatePullPointResponse"
    element="wsnt:CreatePullPointResponse"/>
    </wsdl:message>
    <wsdl:message name="UnableToCreatePullPointFault">
    <wsdl:part name="UnableToCreatePullPointFault"
    element="wsnt:UnableToCreatePullPointFault"/>
    </wsdl:message>
    <!-- ================ SubscriptionManager::Renew ==================
    Renew( Duration | AbsoluteTime)
    returns: (New Termination Time [CurrentTime])
    -->
    <wsdl:message name="RenewRequest">
    <wsdl:part name="RenewRequest"
    element="wsnt:Renew"/>
    </wsdl:message>
    <wsdl:message name="RenewResponse">
    <wsdl:part name="RenewResponse"
    element="wsnt:RenewResponse"/>
    </wsdl:message>
    <wsdl:message name="UnacceptableTerminationTimeFault">
    <wsdl:part name="UnacceptableTerminationTimeFault"
    element="wsnt:UnacceptableTerminationTimeFault" />
    </wsdl:message>
    <!-- ============== SubscriptionManager::Unsubscribe ===============
    Unsubscribe()
    returns: empty
    -->
    <wsdl:message name="UnsubscribeRequest">
    <wsdl:part name="UnsubscribeRequest"
    element="wsnt:Unsubscribe"/>
    </wsdl:message>
    <wsdl:message name="UnsubscribeResponse">
    <wsdl:part name="UnsubscribeResponse"
    element="wsnt:UnsubscribeResponse"/>
    </wsdl:message>
    <wsdl:message name="UnableToDestroySubscriptionFault">
    <wsdl:part name="UnableToDestroySubscriptionFault"
    element="wsnt:UnableToDestroySubscriptionFault" />
    </wsdl:message>
    <!-- ========== SubscriptionManager::PauseSubscription ============
    PauseSubscription()
    returns: empty
    -->
    <wsdl:message name="PauseSubscriptionRequest">
    <wsdl:part name="PauseSubscriptionRequest"
    element="wsnt:PauseSubscription"/>
    </wsdl:message>
    <wsdl:message name="PauseSubscriptionResponse">
    <wsdl:part name="PauseSubscriptionResponse"
    element="wsnt:PauseSubscriptionResponse"/>
    </wsdl:message>
    <wsdl:message name="PauseFailedFault">
    <wsdl:part name="PauseFailedFault"
    element="wsnt:PauseFailedFault" />
    </wsdl:message>
    <!-- ========= SubscriptionManager::ResumeSubscription ============
    ResumeSubscription()
    returns: empty
    -->
    <wsdl:message name="ResumeSubscriptionRequest">
    <wsdl:part name="ResumeSubscriptionRequest"
    element="wsnt:ResumeSubscription"/>
    </wsdl:message>
    <wsdl:message name="ResumeSubscriptionResponse">
    <wsdl:part name="ResumeSubscriptionResponse"
    element="wsnt:ResumeSubscriptionResponse"/>
    </wsdl:message>
    <wsdl:message name="ResumeFailedFault">
    <wsdl:part name="ResumeFailedFault"
    element="wsnt:ResumeFailedFault" />
    </wsdl:message>
    <!-- =================== PortType Definitions ===================== -->
    <!-- ========= NotificationConsumer PortType Definition =========== -->
    <wsdl:portType name="NotificationConsumer">
    <wsdl:operation name="Notify">
    <wsdl:input message="wsntw:Notify" />
    </wsdl:operation>
    </wsdl:portType>
    <!-- ========= NotificationProducer PortType Definition =========== -->
    <wsdl:portType name="NotificationProducer">
    <wsdl:operation name="Subscribe">
    <wsdl:input message="wsntw:SubscribeRequest" />
    <wsdl:output message="wsntw:SubscribeResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="InvalidFilterFault"
    message="wsntw:InvalidFilterFault"/>
    <wsdl:fault name="TopicExpressionDialectUnknownFault"
    message="wsntw:TopicExpressionDialectUnknownFault"/>
    <wsdl:fault name="InvalidTopicExpressionFault"
    message="wsntw:InvalidTopicExpressionFault" />
    <wsdl:fault name="TopicNotSupportedFault"
    message="wsntw:TopicNotSupportedFault" />
    <wsdl:fault name="InvalidProducerPropertiesExpressionFault"
    message="wsntw:InvalidProducerPropertiesExpressionFault"/>
    <wsdl:fault name="InvalidMessageContentExpressionFault"
    message="wsntw:InvalidMessageContentExpressionFault"/>
    <wsdl:fault name="UnacceptableInitialTerminationTimeFault"
    message="wsntw:UnacceptableInitialTerminationTimeFault"/>
    <wsdl:fault name="UnrecognizedPolicyRequestFault"
    message="wsntw:UnrecognizedPolicyRequestFault"/>
    <wsdl:fault name="UnsupportedPolicyRequestFault"
    message="wsntw:UnsupportedPolicyRequestFault"/>
    <wsdl:fault name="NotifyMessageNotSupportedFault"
    message="wsntw:NotifyMessageNotSupportedFault"/>
    <wsdl:fault name="SubscribeCreationFailedFault"
    message="wsntw:SubscribeCreationFailedFault"/>
    </wsdl:operation>
    <wsdl:operation name="GetCurrentMessage">
    <wsdl:input message="wsntw:GetCurrentMessageRequest"/>
    <wsdl:output message="wsntw:GetCurrentMessageResponse"/>
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="TopicExpressionDialectUnknownFault"
    message="wsntw:TopicExpressionDialectUnknownFault"/>
    <wsdl:fault name="InvalidTopicExpressionFault"
    message="wsntw:InvalidTopicExpressionFault" />
    <wsdl:fault name="TopicNotSupportedFault"
    message="wsntw:TopicNotSupportedFault" />
    <wsdl:fault name="NoCurrentMessageOnTopicFault"
    message="wsntw:NoCurrentMessageOnTopicFault" />
    <wsdl:fault name="MultipleTopicsSpecifiedFault"
    message="wsntw:MultipleTopicsSpecifiedFault" />
    </wsdl:operation>
    </wsdl:portType>
    <!-- ========== PullPoint PortType Definition ===================== -->
    <wsdl:portType name="PullPoint">
    <wsdl:operation name="GetMessages">
    <wsdl:input name="GetMessagesRequest"
    message="wsntw:GetMessagesRequest" />
    <wsdl:output name="GetMessagesResponse"
    message="wsntw:GetMessagesResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="UnableToGetMessagesFault"
    message="wsntw:UnableToGetMessagesFault" />
    </wsdl:operation>
    <wsdl:operation name="DestroyPullPoint">
    <wsdl:input name="DestroyPullPointRequest"
    message="wsntw:DestroyPullPointRequest" />
    <wsdl:output name="DestroyPullPointResponse"
    message="wsntw:DestroyPullPointResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault"/>
    <wsdl:fault name="UnableToDestroyPullPointFault"
    message="wsntw:UnableToDestroyPullPointFault" />
    </wsdl:operation>
    <wsdl:operation name="Notify">
    <wsdl:input message="wsntw:Notify"/>
    </wsdl:operation>
    </wsdl:portType>
    <!-- ========== CreatePullPoint PortType Definition =============== -->
    <wsdl:portType name="CreatePullPoint">
    <wsdl:operation name="CreatePullPoint">
    <wsdl:input name="CreatePullPointRequest"
    message="wsntw:CreatePullPointRequest" />
    <wsdl:output name="CreatePullPointResponse"
    message="wsntw:CreatePullPointResponse" />
    <wsdl:fault name="UnableToCreatePullPointFault"
    message="wsntw:UnableToCreatePullPointFault" />
    </wsdl:operation>
    </wsdl:portType>
    <!-- ========== SubscriptionManager PortType Definition =========== -->
    <wsdl:portType name="SubscriptionManager">
    <wsdl:operation name="Renew">
    <wsdl:input name="RenewRequest"
    message="wsntw:RenewRequest" />
    <wsdl:output name="RenewResponse"
    message="wsntw:RenewResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="UnacceptableTerminationTimeFault"
    message=
    "wsntw:UnacceptableTerminationTimeFault" />
    </wsdl:operation>
    <wsdl:operation name="Unsubscribe">
    <wsdl:input name="UnsubscribeRequest"
    message="wsntw:UnsubscribeRequest" />
    <wsdl:output name="UnsubscribeResponse"
    message="wsntw:UnsubscribeResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="UnableToDestroySubscriptionFault"
    message=
    "wsntw:UnableToDestroySubscriptionFault" />
    </wsdl:operation>
    </wsdl:portType>
    <!-- ====== PausableSubscriptionManager PortType Definition ======= -->
    <wsdl:portType name="PausableSubscriptionManager">
    <!-- ============== Extends: SubscriptionManager ============ -->
    <wsdl:operation name="Renew">
    <wsdl:input name="RenewRequest"
    message="wsntw:RenewRequest" />
    <wsdl:output name="RenewResponse"
    message="wsntw:RenewResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="UnacceptableTerminationTimeFault"
    message=
    "wsntw:UnacceptableTerminationTimeFault" />
    </wsdl:operation>
    <wsdl:operation name="Unsubscribe">
    <wsdl:input name="UnsubscribeRequest"
    message="wsntw:UnsubscribeRequest" />
    <wsdl:output name="UnsubscribeResponse"
    message="wsntw:UnsubscribeResponse" />
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="UnableToDestroySubscriptionFault"
    message=
    "wsntw:UnableToDestroySubscriptionFault" />
    </wsdl:operation>
    <!-- === PausableSubscriptionManager specific operations === -->
    <wsdl:operation name="PauseSubscription">
    <wsdl:input message="wsntw:PauseSubscriptionRequest"/>
    <wsdl:output message="wsntw:PauseSubscriptionResponse"/>
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="PauseFailedFault"
    message="wsntw:PauseFailedFault" />
    </wsdl:operation>
    <wsdl:operation name="ResumeSubscription">
    <wsdl:input message="wsntw:ResumeSubscriptionRequest"/>
    <wsdl:output message="wsntw:ResumeSubscriptionResponse"/>
    <wsdl:fault name="ResourceUnknownFault"
    message="wsrf-rw:ResourceUnknownFault" />
    <wsdl:fault name="ResumeFailedFault"
    message="wsntw:ResumeFailedFault" />
    </wsdl:operation>
    </wsdl:portType>
    </wsdl:definitions>
    And the error i get is [fatal error] null databinding context encountered when creating service.
    Steps i followed:
    1. Created a new project in Jdev
    2. Right clicked on project to expand Business Tier - Web Services nodes. Selected the Java web Service from WSDL.
    3. Selected WSDL to convert
    ---Says it is Fetching WSDL
    ---then says building model
    --and pops error : [fatal error] null databinding context encountered.
    Any suggestions? I'm unable to get this issue fixed for a long time.

    Hey guys,
    I couldnt get this fixed in jdeveloper, i finally gave up on using Jdeveloper for Web service creation.
    I went back to my eclipse3.2.2 and used the Eclipse WTP 1.5.4 and guess what, it had no issues generating the service and client for my WSDL.
    I am not sure Jdeveloper can compete with Eclipse functionality and ease.

Maybe you are looking for