Skip to main content

Simple script to upload images into XML-DB (EPG)

By
When you develop your APEX application using the APEX Listener or OHS, it is a good habit to create a separate (sub)folder to serve your images - and other files - into your application. Usually the name of the subfolder reflects the name of the application. So you reference these images, like an "enabled" image in your application by '#IMAGE_PREFIX#my-app/enabled.png'. So far so good.
But now you need to deploy this to a server that is using the Embedded PLSQL Gateway (EPG)? How to serve these images into that application without changing your code? Uploading the images the regular way into the workspace or application doesn't help, because you won't get the subdirectory prefix. The only way (I know of) is to upload these images into the XML-DB Repository. 

So I created this script - feel free to use, edit or whatever you want to do with it (no guarantees!):

Comments

Unknown said…
The script looks easy but copying it is extremely hard! :)
2:30 pm
Roel said…
Yeah, I know. But this was the easiest/fastest way to let it look nice.
2:48 pm
Byte64 said…
Uhm I must be missing something here Roel, because I have been uploading all files I needed during the last years very easily, by using the WebDAV (HTTP) protocol that you just need to enable in the EPG configuration.
That allows me to see the XDB file system as a top folder where I can create as many subfolders I want to using the normal client OS methods (in Mac OS X this works just great, I go to the Finder menu and then Go, specify the server name or ip address with the port if other than 80 and I'll get connected to the root XDB folder).

So, besides the usual "i" folder containing all the built-in apex stuff, I created my own folders that I can then reference from within Apex by using a custom substitution string.
Alternatively one can create a subfolder "myapp" of "i" and the reference #IMAGE_PREFIX#/myapp, as you described, but I find that less than desirable because it will get "renamed" along with "i" when you perform a major upgrade of Apex even if I don't need to change my app's images.

Please tell me if I mistook something.

Regards
Flavio
6:42 pm
Marco Gralike said…
AS far as I read the post, Roel only demonstrated the SQL, PL/SQL way of doing it. In principle your doing the same without knowing it, via the drag & drop method while using WebDAV

Marco
9:29 pm
Post a Comment

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more