Cannot deploy/transfer to the simulator of Tablet

Similar Questions

• Can deploy app in the Simulator, but not to the device

  Sorry about this newbie question, but how is it that a simple HelloWorld application compiled in Eclipse runs just fine on the Simulator, but cannot be installed on a 8320 Curve by the Blackberry Desktop Software?

  I use the latest version at all.  The message returned by the desktop software is:

  ! There was an error importing files.
  No additional applications can be found. Your file can
  contain applications that already exist in the list of applications,
  are not compatible for your device, or errors.

  However, I am able to deploy the application on the handset using the command line tool:

  C:\Eclipse\plugins\net.rim.ejde\vmTools\JavaLoader.exe -usb load \workspace\HelloTest\deliverables\Standard\5.0.0\HelloTest.jad
  

  This installs the application, which then runs correctly on the device.  I can then reload the list of app on the Blackberry Desktop Software tool and it shows HelloTest, but under the properties of the Application-> dependencies it says:

  "Application not available (net_rim_cldc).

  It seems that some dependence crept in the generation of the application and that confuses the desktop tool.  The curve is running 4.5 OS.

  Should I just throw this office tool, or how can I clean the application so that it installs correctly?  Obviously, this is just foreplay before building a much broader application, and I wish I had these little glitches will hamper ASASP.

  Thanks for any help!

  You should be able to download a plugin 4.5 on the site to update. Go to "help > install new software" to open the screen of software available. If you have not yet done so, add the updated BlackBerry site to your Eclipse configuration:

  1. Click on "available software Sites.
  2. Click on the button 'Add '.
  3. Enter a name such as 'BlackBerry update location' and set the location http://www.blackberry.com/go/eclipseUpdate/3.5/java
  4. Click OK, then OK again to return to the screen of the software available

  The 'working with' menu drop-down, select the location of BlackBerry Update (or whatever you named it). Expand the BlackBerry Java plug-in category and you should be able to select an appropriate plug-in version.

• How to play mp3 in the simulator of Tablet

  I want to integrate its App, the snippet of code as follows:

  Sound/speakers in the Simulator do not currently work.  We hope that in the next version of the SDK.  If it works as an AIR application, you are safe to assume that it will work on the device end probbly.

• transfer to the Simulator without the IDE requests

  
  

  Each BlackBerry Tablet OS SDK (AIR, WebWorks, Android and native) come with a command-line tool called blackberry - deploy that allows to install applications.  BlackBerry Tablet OS graphical help provides a GUI wrapper for these batch files.

  If you do not necessarily have the native SDK installed, but you will need one of the SDK.

• the simulator of tablet users, what af version Java VM is running?

  I'm having trouble installing my Simulator.

  During my installation of other software, I had to download and install a jdk and change the environment varables.

  they are defined as:

  user:

  JAVA_HOME C:\Program Files (x86)\Java\jdk1.6.0_29\bin

  ACCESS C:\Program Files path (x86)\Java\jdk1.6.0_29\bin

  system:

  C:\Program Files (x86)\Java\jdk1.6.0_29\bin path

  JAVA_HOME C:\Program Files (x86)\Java\jdk1.6.0_29\bin

  I tried track similar cases of problems with instalation.  The error message I get is: Windows error 2 occurred during the loading of the java virtual machine.  I googled the error message.  And have found that other people have had this problem when installing software using install anywhere.   Some of the possible solutions to this problem are to make shure the directory that is currently being installed in is empty.  I can't find what could be this directory.  This could be the problem since I tried to install several times.  Is there anyway to find out what this directory?

  And also, another possible solution is to run the instation of the comand using the LX_VM, to use a special installation of the java VM.

  ->

  Symptoms: The user is using Windows. An error during the installation of software voices, for example, audium.exe or another installer, which indicates a problem with the Java. One such error is the following:

  Windows 3 error occurred during the loading of the Java virtual machine
  Resolution: An installer of voice may be forced to use a particular installation of Java rather than the default. With this, you can be sure that it uses a supported Java version. Follow these steps:

  Open a console, for example, Start-> Run...--> cmd.

  Navigate to the location of the installation file.

  Run the installer with the option of LAX_VM followed by the full path to the desired java.exe, for example,

  Audium.exe LAX_VM "C:\Program Files\Java\j2re1.4.2_08\bin\java.exe".

  =======================================================================================================================
  All programs Windows Setup

  If you use the Windows Installer package, you may encounter the following error message when you run the Setup program:

  Windows error 2 occurred during the loading of the Java virtual machine.

  The workaround is to run Setup from the command line using a different syntax. In the following example, e:\Java\jdk1.5.0_11\bin\java.exe is the path to the JDK installed on the host computer:

  GCI.exe LAX_VM 'e:\Java\jdk1.5.0_11\bin\java.exe '.

  ==========================================================

  What is the problem? My java virtual machine version is the problem?

  That was indeed the problem.  I learned a lot.  But it has not been easy. Why nobody gave me a helping hand? I went into the command window.  Tried to run the Setup at the root of c:\ and received a message "unrecognized command".  This me puzzled for a while. But I remembered that the installer has been in office.  I tried again.  And he ran.  But I had the same machine vm does not no error.  I just barly noticed that I forgot to put \bin\ points to the jdk.

  And then when I ran, it went through.  Well, you have to understand there is not something wrong internally with the virtual machine.  Unless you have the wrong version.  So, its got to be the way that the whole package is installed.

  So if you can get by modifying the installation process, you stand a good chance to fix the problem.  Now it's just a matter of folling the usual VMware player loading instructions.

• Help me! Cannot delete app in the Simulator.

  I want to remove my application from Simulator to test some things. I go to Option-> advanced-> Application-> Module Option and remove my app, but after simulator restarts. My application still remain. Help me! Thank you.

  Go to the directory of Simulator and manually deleting the file DOC.

• Cannot run app in the Simulator!

  Hello

  So I did the project using Flash Builder and since the SDK is buggy and can't be packaged and signed using Flash Builder, I have updated the content property of the XML to "App.as" and packed using the command line. I also did the 2 step of signing process.

  Now I have installed the signed bar file using the command line, and when I open the app, I see a gray screen!

  I think that 'App.as' is an action script file which I use in the tag content. On the other hand, Flash Builder creates a SWF file using this and which uses as content. My question would be, how can I do?

  In addition, no one knows about the next SDK release? This SDK is really buggy!

  Hey Foundation.

  you mix two steps into one. Please do the following:

  1. Change your content of the tags in the - app.xml back to the original value. so, something like this:

                             [This value will be overwritten by Flash Builder in the output app.xml]
     

  2. Then, you need to compile your application. After resetting the - app.xml under your src directory, you can do this part in flash builder. to do this and after measurements, please carefully follow the instructions in this thread:

     http://supportforums.BlackBerry.com/T5/Tablet-OS-SDK-for-Adobe-Air/useful-tip-package-images-via-com...

  After that, you should be able to package and sign your App. Good luck!

• Cannot deploy due to the Unmarshaller exception has no

  Hello
  
  I am using WebLogic on Solaris 9.2.2. I hope someone can tell me what to do when my deployment fails due to an exception "Unmarshaller failed. This is the track of the long-life battery. Anything to push me in the right direction is appreciated,-Dave
  
  
  # < 28 October 2008 11:50:40 AM MDT > < error > < hats > < rhonti > < nps-supp-gui-ms-1 > < [pending] ExecuteThread: '3' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1225216240248 > < BEA-149265 > < error has occurred in the execution of the request of deployment with the ID ' 1225216234581 'for task 311'. Error is: "weblogic.application.ModuleException: [HTTP:101064] [WebAppModule(nps_history_gui:nps_history_gui.war)] in Web application descriptor parsing error" / export/third-party/etsbea/product/wls_9.2.2/user_projects/domains/nps_pt_92/servers/nps-supp-gui-ms-1/stage/nps_history_gui/nps_history_gui.war ' "
  weblogic.application.ModuleException: Unmarshaller failed
  at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:781)
  at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:272)
  at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
  at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
  to weblogic.application.internal.flow.DeploymentCallbackFlow$ 1.next(DeploymentCallbackFlow.java:360)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
  to weblogic.application.internal.BaseDeployment$ 1.next(BaseDeployment.java:615)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
  at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
  at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
  at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
  at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
  at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
  at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
  at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
  at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
  at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
  at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
  at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
  to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 000 (DeploymentReceiverCallbackDeliverer.java:12)
  to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 1.run(DeploymentReceiverCallbackDeliverer.java:45)
  to weblogic.work.ServerWorkManagerImpl$ WorkAdapterImpl.run (ServerWorkManagerImpl.java:518)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
  Caused by: weblogic.descriptor.BeanAlreadyExistsException: bean already exists: ' weblogic.j2ee.descriptor.FilterMappingBeanImpl@12a064e3(/FilterMappings[weblogic.descriptor.internal.CompoundKey@13f28ec1]).
  at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:207)
  at weblogic.j2ee.descriptor.WebAppBeanImpl.setFilterMappings(WebAppBeanImpl.java:834)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:585)
  at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
  to com.bea.staxb.runtime.internal.RuntimeBindingType$ BeanRuntimeProperty.setValue (RuntimeBindingType.java:483)
  to com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$ QNameRuntimeProperty.fillCollection (AttributeRuntimeBindingType.java:385)
  at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
  at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:145)
  at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:185)
  at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:154)
  at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
  to weblogic.descriptor.internal.MarshallerFactory$ 1.createDescriptor(MarshallerFactory.java:136)
  at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)
  at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:749)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:378)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:720)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:729)
  at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:134)
  at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:775)
  ... 25 more
  
  "weblogic.application.ModuleException: Unmarshaller failed.
  weblogic.application.ModuleException: [HTTP:101064] [WebAppModule(nps_history_gui:nps_history_gui.war)] in Web application descriptor parsing error "/ export/third-party/etsbea/product/wls_9.2.2/user_projects/domains/nps_pt_92/servers/nps-supp-gui-ms-1/stage/nps_history_gui/nps_history_gui.war".
  weblogic.application.ModuleException: Unmarshaller failed
  at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:781)
  at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:272)
  at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
  at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
  to weblogic.application.internal.flow.DeploymentCallbackFlow$ 1.next(DeploymentCallbackFlow.java:360)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
  to weblogic.application.internal.BaseDeployment$ 1.next(BaseDeployment.java:615)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
  at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
  at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
  at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
  at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
  at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
  at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
  at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
  at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
  at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
  at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
  at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
  to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 000 (DeploymentReceiverCallbackDeliverer.java:12)
  to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 1.run(DeploymentReceiverCallbackDeliverer.java:45)
  to weblogic.work.ServerWorkManagerImpl$ WorkAdapterImpl.run (ServerWorkManagerImpl.java:518)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
  Caused by: weblogic.descriptor.BeanAlreadyExistsException: bean already exists: ' weblogic.j2ee.descriptor.FilterMappingBeanImpl@12a064e3(/FilterMappings[weblogic.descriptor.internal.CompoundKey@13f28ec1]).
  at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:207)
  at weblogic.j2ee.descriptor.WebAppBeanImpl.setFilterMappings(WebAppBeanImpl.java:834)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:585)
  at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
  to com.bea.staxb.runtime.internal.RuntimeBindingType$ BeanRuntimeProperty.setValue (RuntimeBindingType.java:483)
  to com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$ QNameRuntimeProperty.fillCollection (AttributeRuntimeBindingType.java:385)
  at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
  at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:145)
  at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:185)
  at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:154)
  at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
  to weblogic.descriptor.internal.MarshallerFactory$ 1.createDescriptor(MarshallerFactory.java:136)
  at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)
  at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:749)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:378)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:720)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:729)
  at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:134)
  at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:775)
  ... 25 more
  
  weblogic.application.ModuleException: Unmarshaller failed
  at weblogic.servlet.internal.WebAppModule.createModuleException(WebAppModule.java:980)
  at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:799)
  at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:272)
  at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
  at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
  to weblogic.application.internal.flow.DeploymentCallbackFlow$ 1.next(DeploymentCallbackFlow.java:360)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
  to weblogic.application.internal.BaseDeployment$ 1.next(BaseDeployment.java:615)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
  at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
  at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
  at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
  at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
  at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
  at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
  at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
  at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
  at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
  at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
  at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
  to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 000 (DeploymentReceiverCallbackDeliverer.java:12)
  to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 1.run(DeploymentReceiverCallbackDeliverer.java:45)
  to weblogic.work.ServerWorkManagerImpl$ WorkAdapterImpl.run (ServerWorkManagerImpl.java:518)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
  weblogic.descriptor.BeanAlreadyExistsException: bean already exists: ' weblogic.j2ee.descriptor.FilterMappingBeanImpl@12a064e3(/FilterMappings[weblogic.descriptor.internal.CompoundKey@13f28ec1]).
  at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:207)
  at weblogic.j2ee.descriptor.WebAppBeanImpl.setFilterMappings(WebAppBeanImpl.java:834)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:585)
  at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
  to com.bea.staxb.runtime.internal.RuntimeBindingType$ BeanRuntimeProperty.setValue (RuntimeBindingType.java:483)
  to com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$ QNameRuntimeProperty.fillCollection (AttributeRuntimeBindingType.java:385)
  at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
  at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:145)
  at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:185)
  at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:154)
  at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
  to weblogic.descriptor.internal.MarshallerFactory$ 1.createDescriptor(MarshallerFactory.java:136)
  at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)
  at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:749)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:378)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:720)
  at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:729)
  at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:134)
  at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:775)
  at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:272)
  at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
  at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
  to weblogic.application.internal.flow.DeploymentCallbackFlow$ 1.next(DeploymentCallbackFlow.java:360)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
  to weblogic.application.internal.BaseDeployment$ 1.next(BaseDeployment.java:615)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
  at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
  at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
  at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
  at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
  at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
  at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
  at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
  at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
  at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
  at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
  at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
  to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 000 (DeploymentReceiverCallbackDeliverer.java:12)
  to weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$ 1.run(DeploymentReceiverCallbackDeliverer.java:45)
  to weblogic.work.ServerWorkManagerImpl$ WorkAdapterImpl.run (ServerWorkManagerImpl.java:518)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

  You can post your web.xml?

  Maybe the problem is that you have a duplicate servlet mapping.

  --
  Wiest

• Unable to load the file on Tablet Simulator bar

  Hello

  I have the latest JDK and JRE and the simulator of tablet running on the VM player. The development mode is on and I have the IP address. I managed to compile the example sketch program, and it generated a file bar. But when I get home

  BlackBerry-deploy - password xx - installApp-device 192.168.52.128 - package bin\sketchPadStandard.bar

  It says install...

  then,

  result::faliure.

  don't give all the details. Any ideas as to why this is happening?

  Hello

  It was with the release of Simulator.downloaded the new version (beta 2), and it worked.

  Oh and another thing, I tried to create a virtual machine with a 2 GB hard drive and it wouldn't boot (the old version did somehow). When I increased the size of the HD fine tho.

• Cannot deploy the bar file BB10 Simulator.

  As the title,

  I have try all the possible method to deploy my bar of file Simulator BB10 running on VMware player without a bit of luck.

  The IP address that I use is the one indicated in the developer section of the simulated device:
  169.254.0.1

  no luck, I can't even ping the device to the windows console.

  Any idea?

  If you are connected to a VPN, it can cause connection problems to the Simulator.

  Could you try reboot the Simulator in bridged mode?  You can change this under the network option in the settings of your virtual machine.  If you do not have to go through NAT, which could cause you problems, this will put the Simulator on your physical network card.

  Also are you able to telnet/ftp to the Simulator?  You can identify yourself as devuser/devuser.

• Ripple error deployment to the simulator fails

  Hi, I'm taking my first steps in development of BB. My company asked me to do a BB - app with IBM work lamp. I installed the SDK Webworks, waving and a BB Simulator (model 9900). I also added the necessary environment variables on Windows 7. I did a hybrid application that contains the html, css and javascript. After the creation and deployment of the local console of the work light, I can open the app with ripple. After the start of the services, I can pack and start the work of packing App., but the deployment on the simulator fails. I get the following error:

  Spawning Simulator 9900 - 7.0.0.384...

  stderr: CreateProcessW: the system cannot find the specified file.

  Exit take flight for 9900 - 7.0.0.384

  I have seen this error on the forum, but others had when packing. I get it through to the Simulator. Can someone help me with this?

  I solved my problem by choosing another Simulator, 9860-model. Ripple now starts the Simulator, which is extremely slow. The hotswap function crashes immediately, but the Simulator works with my application. However I am concerned that blackberry development tools is so buggy. But as long as I don'tn use the simulator that's good enough.

• Flash Builder does not appear to be deployed to the Simulator:

  Hey guys!

  So here's the deal. I am running Win7 with the IDE Flash Builder Burrito. I followed the guide on the BB step by step to create my first Hello World project. When I try to debug, FB seems to show that it has installed the successful application on the Simulator, but still waiting to connect to the application until it finally expires with the message "the Flash BUilder debugger cannot connect to the running application".

  Host machine, I ping IP of the Simulator, and the mode of development.

  I inserted the target IP address in the Debug menu (it's 192.168.88.128) and the debug host is the IP address of the host too (10.0.3.136). I entered the correct device as password.

  Scratching my head here now, what Miss me?

  Alright! It is very very annoying. I discovered that I was in fact trying to deploy on the previous version of the Simulator... Sorry to lose all time on it. Consider this a rookie mistake

• IDE cannot find the Simulator

  First off, the IDE can find my Playbook very well, but he can't find the Simulator. I tried different combinations to start the Simulator and the IDE (in order) but also to restart my computer.

  In debugging, the automatic discovery of target configurations can't find the Simulator. I tried to manually enter the IP address and IP development of the Simulator as well but FDI still can not find it.

  Hi, I don't have any VPN Firewall (or antivirus) software installed. The Windows Firewall is disabled. It's because I reinstalled recently in fact Windows on this machine.

  Anyway, I solved my problem. I executed the script blackberry-deploy from the command line and discovered that Java was not in the PATH variable, so I added it. Now, I was able to get the blackberry - deploy to install the application from the command line with success in the Simulator. The IDE has always not able to automatically detect the device, but by creating the debug configuration with the IP of the target, the IP address in the Simulator, I clicked by error messages indicating that it could not connect, hit apply and OK buttons, and then in the project view and this is the error next to the Simulator icon has disappeared and I was able to debug in the IDE from here with happiness!

  Thanks for your post, "blocking communication" made me wonder if the IDE was the difficulty to communicate with blackberry-deploy.

  LESSON LEARNED: Make sure that Java is in your PATH variable!

  Edit:

  You know that it is confusing to me how he managed to deploy on the device very well, because I imagine that uses the same blackberry-deploy. Maybe she called a path/to/java instead of just "java" when deploying to the device, or I'm going crazy, or maybe the IDE just need a gentle touch and randomly want to work (and then maybe have Java in the PATH variable was not really the solution to this problem; I can't say for sure)

• BB-Ant-tools and deployment to the Simulator

  Hello world:

  I have a library intern that I developed called Ichabod required by one of our applications, Spyder, which runs on the operating system Blackberry 4.5.0 (our original goal was to 8330 devices).  I had all this work with bb-ant-tools to compile the library, which is located in a separate project, and deploy it in C:\Program Files\eclipse\plugins\net.rim.ejde.componentpack4.5.0_4.5.0.21\components\simulator.  The Spyder application debugged very well in the eclipse plugin (I use Galileo with the 1.1.2 version of the plugin RIM).

  Today, however, I went to debug the Spyder application after making a few changes to the code (no code changes have been made in Toad) and found that the application could not find the module Ichabod suddenly.  I noticed that there is now a directory net.rim.ejde.componentpack4.5.0_4.5.0.28\ in my eclipse plugins folder, thinking that maybe I've updated component packs without realizing account, I adjusted the path target library of Ichabod and rebuilt with bb-ant-tools.  The same problem.  So, I tried to delete the .cod and all associated files the two directories 4.5.0.21 and 4.5.0.28, recompiled the Ichabod library to deploy in two places and found that it worked with 4.5.0.21, but not with 4.5.0.28 (it is not listed in the screen modules under settings, either).

  I checked the .cod file is present in the components\simulator folder, but I can't understand why the simulators do not recognize the file.

  Any suggestions?

  My build.xml ant-bb-tools script is attached.

  Thank you

  ~ Scott

  So it turns out, after removing the 4.5.0.28 Eclipse plugin and put it back, it was what was causing my problems.  I don't know if this has anything to do with it, but I also removed the JDE 4.5.0 library (which has been correctly updated version 28) from the path of construction of the project Ichabod and replaced by the JDE even.

  After all of this nonsense, my library now appears in the Simulator.

• Impossible to deploy my application on the Simulator more

  Since there are 4 days, I can't deploy and run my application on the Simulator more, I get this message all the time:

  Failure of deployment: Info: request shipment: install and launch
  Info: Action: install and launch
  News: Native debugging: on
  Info: File size: 482774
  Info: Installing eir.bb10.CorporateContacts.testDev_ateContacts1e5ecb89...
  Info: Treatment 482774 bytes

  What could be the problem? I later use NDK, reinstalled all, using 3 different simulators, including the most recent, but without success.

  I'd appreciate any help. It is very annoying, because I can't do any work and ship expected app updates, I face the environment of dev for 4 days! I have worked on many platforms and with many different tools, but I've never experienced anything like this.

  Thanks for the reply!

  I managed to get things running in a similar way. I uninstalled everything, including the NDK and start over. I returned to VMWare Player v.4. I work mainly with outdated Simulator, we run the fastest for me, although later runs now too.

  Yet EACH deployment on a Simulator takes several attempts, I don't remember when was the last time that the deployed application and runs correctly on the first attempt. I also change the download settings, switching between 'install bar' and 'clean install', these two works more often for me. Another thing to try in the meantime is to go for debugging directly, if the race does not...

  It is a terrible experience and it's very laborious, as I end up losing most of my time trying to run my application on the Simulator, instead of productive coding. Sorry BlackBerry, but it's worse that develop for Android, iOS, Windows Phone, Java ME... I develop for these systems and has never had any topic also with any of them.

  One of the reasons for the app started working again maybe do something with the code, because it contained errors, but the construction still successfully passed and they never showed me any error message in the IDE or in the Simulator. Anyway, I'll never know if my code had something to do with the cause of the problem, because the 'hack' held an older VM etc. But I write this so that people know that it can theoretically hinder deployment too.