• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
FileUpload in Modern D2W help/ideas needed
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FileUpload in Modern D2W help/ideas needed


  • Subject: FileUpload in Modern D2W help/ideas needed
  • From: Markus Ruggiero <email@hidden>
  • Date: Sat, 27 Sep 2014 16:11:05 +0200

I am converting a legacy D2W application to Modern style. In the old application the create page for a given entity was frozen and then hand edited. The application implements something similar to ERAttachment and in the frozen edit page there is a plain WOFileUpload button. All the files go into the same directory (unlike with ERAttachment, where the files are stored in a multi-level subdirectory structure).

I want to do as much as possible without custom components (at least no page level components). I can easily do the Create/Edit/List page configuration for the given entity, but I am struggling with the file upload. I don't think I can use ERAttachment, or can I? My data model is Product <-->> Attachment (yes, the name already maches). Attachment has just a to-one relationship to product and a file name attribute (path is "hard coded" via properties file. It is is certainly possible to extend the existing Attachment entity with more fields, but how wold I handle the differing way of storing the attached files? This is a legacy application where I cannot just simply alter the file system layout. And there are already several 1000's of attachments.

Thanks for any input
---markus---
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: ERRest with non-PK attribute
  • Next by Date: [no subject]
  • Previous by thread: Re: ERRest with non-PK attribute
  • Next by thread: [no subject]
  • Index(es):
    • Date
    • Thread