I am learning to create an ADF enterprise application. I have separated my apps in jar modules as described by Sten E. Vesterli in Developing Web application with ADF. I have two jars that contain two taskflows. How do I link the two in my main app so that after login the button takes me to the DashTaskFlow?
LoginApp has an AuthTaskflow and Dashboard has a DashTaskflow.
Try creating a containing taskflow - either bounded or unbounded (depending on how you want to enter/invoke it) and drag/drop the two JAR'd taskflows into the containing taskflow, then have one TF call/navigate to the other. Since the JAR'd TFs are bounded TFs, when one calls the other the called TF default activity will be invoked automatically on entry.
Related
I have 2 existing projects that are independent of each other, and I was tasked to bring them together under a suite of some sort and share some small data between them. The problem is one platform is using ReactJs and the other using VueJs.
Example:
To give you a small example, it's like having Facebook and Instagram using different JS frameworks, and bringing them together under one platform let's call it Meta so the user goes to one platform and finds all products that the company offers.
(Example of the data that needs to be shared: Dark/Light Mode, User is logged, ....)
And is it possible to wrap both apps inside another, like having a whole new project consisting of a Navbar and a body, and the body switches between showing the first and the second platform using the navbar links?
Please if you have any suggestions throw them at me.
I have two Django projects that need to use the same postgres database.
I created the database in one of the projects -- no problems;
I just created the second project. It will need access to tables in the database. It will also need some additional tables that only it will access.
Two questions:
In the second project, I am getting the 'unapplied migrations' message from the main app. How do I safely get rid of this? I don't want the second project changing the parts of the database that were created by the first app. However, I don't want necessary Django setup to not be done (is there any)?
Suppose I want to create a table used only by the second project. Should I do it in the second project and migrate it? Or should I do it in the first project to prevent the second project 'messing' with the database?
Many thanks.
Background
I have to migrte a existing javascript application (one page app) to extjs. The display and behavior of the application depends on the users permission.
Current design
The application is divided into plugins, which represent a feature set to which permissions are granted. Each of those plugins consists of a single javascript file. A user can have permissions for one or more plugins. Depending on the permissions, those files are loaded in the head of the page. Each of these plugins will add its entries to the main menu and expose the methods used to drive the application.
The permissions are stored in a mysql database.
ExtJs's default design
In ExtJs the source files contain each a class. During the build process, all .js files are concatenated to yield one big .js file, that contains everything.
What would be the best design approach?
I considered to use custom compilation with sencha cmd, and create that way a .js file for each plugin. Then I could load these plugins the same way I do it now. But this results in a complicated build and deployment process.
I also thought about creating one and only .js file with a standard Ext build process. I would then load the permissions from the server via ajax in order to construct the menu. All the objects and methods would exist, but only those are accessible where the user has permissions.
In my opinion, the second approach is much easier maintainable, but it seens to have a security problem, because everyone could look at the source and find out about the data interfaces exposed on the server and consumed by ajax.
Any comments, ideas or advices are welcome. Thanks !
Number two would be the way to go. If you keep your server side permissions in check (while updating data etc) you only need ExtJS to show/hide menu items based on permissions. That way, malicious users can turn certain plugins/items on or off, but they can never execute something that requires more permissions then they would normally have.
My RCP application contains 5 views which fill contents via database queries.
The problem is that the application start completely depends on database queries. In addition, if underlying db is closed the application start time takes too long.
What is the best practice for eclipse rcp views that use db as content source?
Is using a separate thread for filling views be a solution?
Move all your view updating code into an UIJob, then schedule it. User can find the progress of these tasks in the progress view if it is included in your RCP.
In addition, one UIJob takes care one view.
For past projects(the last few have been web using asp.net mvc) we created a service that caches our reference tables(as required) to be used primarily for dropdown lists.
Now I'm working on a desktop application.An upgrade from vb6/sybase to vb.net/sql server
I'm trying out WPF.
I started down the same path building up my DAL. one entity for each reference table.
I'm at the stage now where I want to setup the business layer (some reference tables can be edited)
And I'm not sure if I should follow the same process which is to use ReferenceTableService to "manage" the reference tables.(interacts with the DAL, Controller)
This will be an application that sits on a share that multiple users run.
What's the best way to deal with the reference tables? Caching them doesn't seem to be an option. Should I simply load them as each user opens up a new form in the application? Perhaps using a "ReferenceTableService"?
In this case, the Reference Table Service is thin layer in the application. Not a process running elsewhere.
I haven't done much WPF (be interesting to see what the WPF Gurus think) but I think your existing approach is sound and I don;t see why you should deviate from it.
Loading up on app start sounds reasonable; you just have to think about the expected lifetime of a user session vs the expected frequency of changes to the reference data.
Caching: if the data comes from a central service you could always introduce caching there.