I am working with JDeveloper 12.2.1 and when I try to run the Application Module to test the view object instance the ADF tester model windows does not load. Here a print screen:
The ADF tester windows appear only when there is not any view object instance in the data model. Can you help explain why this is or resolve it? I can not work or test the application module.
Related
I have created a very simple application in app builder in oracle apex. But its not working. When i run this application "Page not found error" is showing. I'm using ORDS 21.0 and APEX 20.0.
Installations are perfectly fine. I've kinda double checked my installations and i think there is no error/defact in my installation.
Otherwise, APEX is working fine just not running my application. Please guide and help me in this !
Looks like Home and/or Login URL point to page that doesn't exist. Check that at:
App. Builder
select that application
in upper right corner you'll see Edit application properties button
go to User interface tab
have a look at Home/Login URLs; fix them. For example, in f?p=&APP_ID.:100:&SESSION., 100 represents page number
I am trying to run this form in the browser, but I keep getting this message not sure how to fix it so can you help me please.
"Ui Designer form type is selected and no target form is defined for overview page mapping. an autogenerated form will be used in the development environment ONLY"
here is a screen shoot of the message.
/Users/user/Desktop/Screen Shot 2017-08-03 at 5.31.44 pm.png
/Users/user/Desktop/Screen Shot 2017-08-03 at 6.34.41 pm.png
Unfortunatly I cant see any pics from your problem and I just think your problem might be with deploying your process.
As the error mentions the form you see when you Run the process from studio is an autogenerated form for testing the process in development mode(Obvious)
So if you want to deploy your process on a deployed Bonita BPM engin you have to create all those forms.
Select the Task (containing the contract cause forms are only generated for contracts) --> Under details panel ---> Execution Tab ---> Form :
Here you have 4 options and as it seems your new to Bonita so I suggest that you go with the UI Designer cause it will generate a form for deploying , simply choose UI Designer then from the right side of Target Form text area click the pencil icon (Edit) , it will create a new form for your contract and opens UI Designer to modify it.
If you just want to see how your process works in deployment environment and don't want to spend time on designing the UI just change the form name from "newForm" to what you want (All the forms created by UI Designer have the "newForm" name before you change it and it may cause problems if you don't modify the name ) and save it.
Build your project and deploy it.
I just started working on the silverlight application automation using QTP 11.0.
On the successful installation and with the required add-ins, I am able to identify the silverlight objects such as window(SlvWindow), Editbox(SlvEdit), Button(Slvbutton) and so on.
But in our application, in a particular page,we have a tree control(Slv tree view) view with nodes and we are not able to click the objects which are in slvtree and also wherever we spy in that page and nothing is getting recorded in QTP when we perform any operations in the tree control view.
Please let me know if any of you faced the above issue and the possible resolutions if available.
Note : Following are the add-ins and application information,
Add-Ins Used
1) Web
2) .NET
3) Activex
4) WPF->Silverlight
Thanks!
I have a wpf application, which has file menu and can open and save projects. I am using Prism and MEF.
Now I need to have a wizard showing the user:
To continue as usual
MRU history so that he can load the project to the work area by double clicking.
MRU service is also in a module(dll), which we add to the catalog in mefbootstrapper.
What would be the best way to achieve this?
As commented above, there would be no need to show the Wizard before loading the Shell:
Using OnDemand modules as you mentioned, you could create an initial generic ShellView, perform the Bootstrapper tasks and finally show the Wizard with the Shell and Bootstrapper already initialized, and the Wizard would then decide the flow of the app according to the user choice.
As the Modules would be loading OnDemand, you would not be initializing unnecessary Modules or objects.
Regards.
I have a desktop application that is based on the Caliburn Micro framework. Everything works great. Now I am trying to port the same app into Outlook as a plugin.
In the desktop app, based on an entry inside app.xaml, Caliburn knows where to find the bootstrapper and instantiates it.
In case of the Outlook plugin, I've created an overridden bootstrapper that I instantiate explicitly inside ThisAddIn.ThisAddIn_Startup(). This one of course does not use the Application object.
I can even invoke a particular view using code similar to this
var windowManager = IoC.Get<IWindowManager>();
windowManager.ShowDialog(new MyViewModel());
And that will cause the view associated with the view model to be shown in a modal window on top of Outlook (hence validating that Caliburn Micro is able to find a view from a view model inside my Outlook plugin)
What I haven't figured out how to do is instantiate the Shell so that I can start using its functionality.
My expectation was that since my bootstrapper derives from BootStrapper, and I have registered my shell view model implementation with the MEF container as exporting IShell, Caliburn will automatically instantiate the shell view model and start using it. That is not happening.
My goal is to get the shell loaded inside my plugin's task pane as the container for other views that I will be loading based on user actions.
Any ideas or tips on how I can get this to work? In general has anyone got a shell implementation loading inside an Outlook or Office plugin's task pane?
Thanks!
Do you mean instantiate via Bootstrapper<Shell>. This uses the Window Manager underneath but I don't think that extends to outlook. There is nothing stopping you using the same code above to initialize your shell manually, composition will handle the rest of the application.
IoC.Get, by default calls Activator.CreateInstance so it is possible your problem is with MEF. The method that drives opening the Shell DisplayRootViewFor() calls this line.
windowManager.ShowWindow(IoC.GetInstance(viewModelType, null), null, settings);
If MEF is not hooked up properly it will fail causing your shell not to load.