There's some big questions in there. Maybe you should stick to one for now and then get follow up on the details if you decide on Django: Python and Django vs Java and some enterprise framework. I use Java for my main project and also looked at Seam and JBPM. My day project is limited to Java for a variety of reasons but I've been using Django for smaller projects for myself and friends. If I could move work over to Python and Django I'd do it in a heartbeat. I feel like each new Java framework attempts to hide complexity but ends up hiding capability and introducing new compatibility issues. I've taken a new approach at work by striping away as many frameworks as I can and slowly adding only what is needed.
With Python and Django I feel closer to the code and have as much capability as I need. There is also a lot less code to deal with. Also, don't forget Java's compile and deploy cycle compared to Django much faster turnaround. This become especially noticeable if you start using Ajax techniques. I could probably rewrite my project in Django in the spare time I have waiting for On 7/30/07, Snirp <[EMAIL PROTECTED]> wrote: > > > I am considering Django to develop a business-to-business service. It > should handle invoices (accounts payable) for my customers. It more or > less comes down to: > > 1. enter invoices [we | various XML formats go into the > database] > 2. complete invoices [automated | interface with customers > accounting system] > 3. validate invoices [customer ] > 4. make booking [automated | interface with customers > accounting system] > > The actual story is much more complex, as it deals with invoices on a > line-item level. These must be able to be distributed / discussed / > divided among users who act as budget-keepers of distinct > departments. > > I have had a little playtime with django, and I found it pleasing to > work with. It seems to be up to the task. I also compared it to Seam > (RedHat Java-framework). Some questions came up: > > - The Java application stack boasts excellent scalability, will this > ever be a problem for python / django (database-transactions etc.)? > > - Integration with Jbpm (workflow engine) is a strong-point with Seam; > designing pageflow directly from process management. Is there anything > like it for Django? > > - The default django user-interface uses permissions and users. Is > this easily expanded with roles? Or is there a reason why there is no > definition of roles? > > - On what level should I seperate different customers? Different > websites / different databases / same database? Is there a smart > choice, or a really stupid one here? > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
