idrs-dev Mailing List for Internet Document and Report Server
Brought to you by:
bigman921
Menu
▾
▴
idrs-dev — this list is for all who wish to discuss developing the IDRS
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(3) |
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(37) |
Feb
(16) |
Mar
(7) |
Apr
(4) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(4) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2003 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Marc B. <mbo...@ya...> - 2003-03-17 14:38:29
|
Hello Everyone,
After an overly long time in planning, initial EJB support has been
added to the idrs! There are 3 parts so far:
1. A JDBC wrapper around a Jndi Connection for connecting to EJB
servers
2. A ResultSet implementation that can take a Collection of
Objects, A collection of HashMaps, an Array of Objects, and
array of hashmaps, a single object and a 2d array of strings
3. A factory method in the idrs scripting object to get refrences
to an ejb that only supports an argumentless create() method
The next step is to add support for caching of home interfaces and
beans. If a bean is stateless it will be cached in the connection, if
it is stateful it will be stored in the user's session.
The latest and greates is in cvs, i'm attaching a jar of the latest
testing code.
Marc
--
Marc Boorshtein <mbo...@ya...>
|
|
From: Marc B. <mbo...@ya...> - 2003-03-06 06:11:15
|
Hello Everyone, I am revisiting the idea of integrating EJBs into the IDRS. I have greatly simplified the process by rellying on the current substructures instead of redesigning it. I have posted a new EJB Integration paper on the site. http://idrs.sourceforge.net/dev/papers/ejb/index.html is the link, for your convinience here is the text: ------------------------------------------------------------------------ IDRS EJB Integration The purpose of this paper is to describe a process for integrating EJB's into the IDRS. The goal of integrating EJBs into the IDRS is for the IDRS to become a front end to an existing application. In order to have the smoothest integration and usage process, the IDRS' substructure should be utilized. The IDRS sub-structure is based on JDBC. This substructure currently handles resource managment and presentation. This substructure can be utlized in the following ways: * Utilize the current Connection pooling framwork * Utlizie the current Object and Report Pooling * Allow for EJBs to be used from any context where a datbase would be used, including the <head> and <body> sections * Allow the IDRS to handle as much of the connection and resolution process as possible. These feature can all be used without changing the fundamentals of the IDRS. There will be two purposes for using EJBs in the IDRS, either to report data or handle data entry. In either case, it can be assumed that Session Beans, be it statefull or stateless, will be used as the primary interface to the EJB server. =20 In the case of reporting, there needs to be a way to use the IDRS' presentation tags and structure to display the data. There are several ways data is brought back from an EJB. The three most common seem to be either a single bean, a Collection of beans or a RowSet. The RowSet is easiest to handle, becaus eit implements ResultSet. The single EJB or the Collection of beans can be handled by a special implementation of the ResultSet class that can use reflection to map bean properties to fields in a database table. By handling the beans in a way that is consitent with a JDBC ResultSet, we will not need to change the internal structure of the IDRS. For data entry/input, IDRS DataObjects can be used as a go-between from the IDRS application and the EJB server. DataObjects can populate a skeleton object for passing to a session bean. Since transactions are managed by the container, there is no need for the IDRS to handle the managment. =20 The last piece is to handle connections to the EJB container. This can be accomplished with two special implementations of the java.sql.Connection interface. One for none-jndi based connections and one for jndi based connections. These Connection objects will store the Context refrence and be responsible for instancing EJBs. This will allow the standard pooling substructure to be utilized. ---------------------------------------------------------------------------= ---- Any thoughts would be greatly appeciated. Happy hacking marc --=20 Marc Boorshtein <mbo...@ya...> |
|
From: Marc B. <mbo...@ya...> - 2003-03-04 23:01:57
|
Hello Everyone, I am nearing a realease of 2.0alpha5. Part of that is a new demo site that has all of the tutorials (right now 2) that are posted so people can see them in action. I also have one that I will be uploading soon that is an address book. =20 the site is http://idrs.homelinux.org:8080/ Marc --=20 Marc Boorshtein <mbo...@ya...> |
|
From: Marc B. <mbo...@ya...> - 2003-01-15 16:18:55
|
Hello Everyone,
I am looking for some insight into whether or not RML & the IDRS should
remain a "proprietary" system separate from JSP, or if RML tags should
be implemented as JSP taglibs. There are some key reasons as to why I
want to make a move to JSP:
1. RML is a set of tags, not a scripting language like WebMacro.=20
It relies on external engines for scripting
2. It give more flexibility in it's implementation, allowing for
other taglib implementations to be used in conjunction with RML.
3. It takes away a lot of the compile/deploy complexity out of the
system.
4. Use of standard development tools
There are some dis-advantages though :
1. Breaking of legacy apps. Perhaps a translation utility? Since
RML does a conversion into XML, it shouldn't be that hard.
2. Loss of control. A key aspect of RML is to limit control to the
system resources. JSP is a much more general system with a lot
more flexibility.
3. It would be harder to "embed" RML into applications (something
that isn't very difficult right now)
I would appreciate anyone's opinion on this matter.
Thanks
Marc Boorshtein
--=20
Marc Boorshtein <mbo...@ya...>
|
|
From: Marc B. <mbo...@ya...> - 2002-12-29 05:00:24
|
Hello Everyone,
I am writing to report some progress :
1. I have fixed some stability issues with the authentication,
while I still do not have pluggable authentication built (or
designed for that matter), the current implementation works
quite well.
2. I have added net.sourceforge.idrs.utils.Validators as a new
Class. This class will provide basic error handling
functionality. I have also made the
net.sourceforge.idrs.utils.CleanUp class a subclass of
Validators. This, when combined with the idrs' error handling
capabilities will make form creation and handling as simple and
powerful as any other web based development platform out there.
3. I am giving a new direction to the idrs in creating an official
development process for creating web applications. This process
is born mostly out of how I tend to use this system in
application development. The first part of this process is to
define two sets of objects, DataObjects and ReportObjects.
DataObjects are meant for input and form handling, while
ReportObjects are designed for extracting information. If
someone can think of better lables, I am all ears.
4. As many of you might have seen, I have tried (unsuccessfully) to
sell a Python script I wrote a while ago to assist in the
creation of DataObjects. The downside of this is that I haven't
sold any copies. The up side is that without any advertising,
close to 100 people have viewed the page over the last couple of
months. This tells me that there is a demand for a good
development environment for the IDRS. To answer this I have
built a wizard for integration with IBM's eclipse. It is pretty
all-encompassing for a code generator. It runs both inside the
eclipse IDE and as a standalone. I have attached some screen
shots and the code that has been generated. I am currently
integrating validation functions into it, but I hope this will
be the beginning of a complete environment, including wizards &
an RML editor all based on eclipse.
If there is anyone who would like to beta-test the software, please
email me.
Marc
ps, hope everyone had a great holiday
--
Marc Boorshtein <mbo...@ya...>
|
|
From: Marc B. <mbo...@ya...> - 2002-10-13 15:10:25
|
Hey everyone, I have added a new package to the class structure, net.sourceforge.idrs.test. This package contains an implementation of the request,response, and session object which allow you to create a facade of running un a servlet container. The IDRSTester class does the leg work of compiling and running te page. Here's the flow: Create Tester --> Add parameters, create facade objects, create connections --> compile the page --> initiailize From here there is an option to run the output or not. I envision this class for testing the <head> section deirectly and is not meant to repolace a Cactus like system. =20 As I built this class pretty quickly for an immediate need, its pretty bare bones and can use a good deal of refinement to stream line the testing process. Marc |
|
From: Marc B. <mbo...@ya...> - 2002-09-16 15:37:24
|
I have commited the following to source control: 1. Fixed hot deployment bug 2. Added Datapaging Happy Hacking Marc |
|
From: Marc B. <mbo...@ya...> - 2002-09-15 18:57:58
|
Hello Everyone, Data paging has been added to the system. Unfortunatly, I can't seem to gain access to the cvs system to make the commit (working on this).=20 THis brings the IDRS into compliance with idrs 1.5! Marc |
|
From: Marc B. <mbo...@ya...> - 2002-09-13 22:07:31
|
Hello Everyone, I have begun the design of integrating EJBs into the IDRS I have added a paper to the website (attached) on integration. I would really appreciate help on this. Thanks Marc Boorshtein __________________________________________________ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com |
|
From: Marc B. <mbo...@ya...> - 2002-09-10 04:53:19
|
Hello everyone. I have added a couple of features that conform to the
path towords 2.0!
The two new main features are:
1. Transaction handling support
2. Automatic Error Handling
Transaction Support is designed allow for a page developer to not worry
about transactions that span multiple connections. Inorder to use a
transaction in a <db> tag, there must be a transaction tag. This tag
can have 1 of 2 values:
BEGIN -- Begin a transaction
COMPLETE -- If not yet begin, begin a transaction; commit all
transactions
=20
Any errors that are generated (part of Automatic Error Handling) or
exceptions force a rollback of all transactions. There is no longer any
need for programmers to manualy track transactions.
Automatic error handkling allows the IDRS to have a 2-RML Page Form
Entry Process. When a form is created using the <formInput> an elemnet
called "doc_GoBack" should contain the name of the RML page contaning
the form. If an error occurrs, the entire request is forwarded back to
the doc_GoBack page and combined with the "paramfirst" option in
<formInput>. There is also an <error> tag which allows for the display
of an error if one occurrs. =20
Errors are generated using the IdrsScript.createError(description)
causes all business logic to stop and to have the request forwarded to
the doc_GoBAck input parameter if it exists, or an exception will be
thrown with the passed in description going to the error page.
These 2 new features will be featured in a new tutorial.
The next major feature I am working on is EJB support. I will be
publishing a project paper int he next few days.
Marc Boorshtein
|
|
From: Marc B. <mbo...@ya...> - 2002-08-23 14:43:30
|
Hey everone, I know it's been a while, but with work and what not I have not had any time this summer! I have wrapped up 2.0 Alpha 4 with the following changes: Added New XML Based Compilation System Deprecated all Pooling Code Added Plugable Authentication Managment Uses Jakarta Commons for default pooling Re-factored IDRSServlet Added Exceptions Added The Ability to Have an Error Page Allow for RML pages to be accessed as .rml (www.someplace.com/idrs/somePage.rml?...). Added File Upload capabilities Added Hashed Password Support I am very excited by these new features, as the IDRS is beginning to become a truly portable AND scalabe development framework! Marc |
|
From: Marc B. <mbo...@ya...> - 2002-06-19 20:44:42
|
Hello Everyone, I know it's been a while, but A LOT has been done. Tonights I will be committing the following changes to CVS: 1. Based on Tim's design work I have added plugable resource managment to the system, as well as deprecated use of the old pooling code. Now the Jakarta-Commons pool package is the default pooling system (but others can be easitly added_ 2. Support for *.rml urls. Now a oage can be refrenced by it's name followed by a .rml. This makes abstraction much easier. the doc_Name parameter is still supported 3. A re-built servlet that is much more efficent and much more straight forward. 4. The ability to specify a different database for authentication and doc storage. With this feature is a more standard connection description system. 5. A new tutorial on using the business logic of the idrs. 6. The ability to forward errors to an "error" page I have also created a path to idrs 2.0: 2.0 alpha 4: This is the next release with the current code base (probably tonight or tommorrow). This will include all of the above features and the previous features from 2.0 alpha 3. This realease will also co-inside with the release of the new website (http://idrs.sourceforge.net/newsite/). I will also be making it easier to deploy the idrs from scratch by building a "distibution" of needed jars and a base web.xml file. 2.0 alpha 5 : Plugable security managment as well as another suprise i will be able to tell everyone in a few days. Also will include better form handling support to complement the new <formInput> tags, as well as a tutorial on form use and creation. 2.0 alpha 6 : EJB support for passing a context to a method (simmilar to passing a connection) and directly calling a session bean's methods in a simmilar way to calling a standard java method. The methods will be able to return a ResultSet (or RowSet) and be able to return a single object. Tags will be created to access the properties of that object 2.0 alpha 7 : Finally throw data-pagin support back into the idrs. This will bring 100% backwards compatability to the idrs. Feature freeze 2.0 Betas 2.0 Final I would like to have 2.0 final in the fall (i know it seems like a lot, but it's a lot less then it seems). In order to meet this, I REALLY need some help. Here is where I really need some help from people: 1. MacroToXML - My macro transformer mostly works. It transforms the tag correctly, but the carriage returns are off. The problem occurrs with tags that have no visible counterpart, like <repeat>. Since there shouldn't be a line where <repeat> is, I need to adjust the text and it's placement on it's flow out. I am mostly there, but it's really getting squirly. I just need another pair of eyes to go over the code and help me find something i seem to be missing. 2. EJB support - I am jsut now learning how to use EJBs. If someone could really help me out here from time to time it would be greatly appreciated. Even if you do not have time for coding, jsut guidence would be very helpful. Thanks, Marc __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
|
From: Marc B. <mbo...@ya...> - 2002-04-14 14:13:48
|
Hello, I've added a bit of security to the IDRS with the ability to use encrypted passwords. In order to use this feature, there is a new init-param in the web.xml file called "digestType". This param is optional and contains the name of the algorithim used to encrypt the passwords (MD5, SHA...) or NONE for no encryption. If the tag is not present, then no encryption is performed. Marc |
|
From: Marc B. <mbo...@ya...> - 2002-04-13 16:19:29
|
Hello everyone. I am prooud to announce that two new RML tags have been added to help working with HTML forms. The first tag is the <yesno> tag. This tag allows for the easy creation of Yes/No option choices. The tag not only generates a set of input tags, but also allows for the value of that tag to come from a request parameter, a database field or an object property. It will also allow for the value to allways come from a parameter first when it should be comming from a db or property. This makes form processesing much easier as there is no need to manually check or load form values. for instance, the following tag: <$ x=0; $> <yesno name="= \"yesnodb\" + x " srcType="db" paramFirst="true" >yesno.val</yesno> with no request parameter named "yesnodb0" and a value of "true" for yesno.val will generate : <input type="radio" name="yesnodb0" value="true" CHECKED> Yes <input type="radio" name="yesnodb0" value="false"> No and with a request parameter named "yesnodb0" set to "false" and a value of "true" for yesno.val will generate : <input type="radio" name="yesnodb0" value="true" > Yes <input type="radio" name="yesnodb0" value="false" CHECKED> No As you can see, this is the first set towordsmaking form handling a two page process, one for entering information and one for handling it. If there is an error, the request can simply be forwarded back to the entry page with all the entered data intact. The second tag is alonf the same lines, but is more gener purpose. THis tag is the <formInput> tag. It acts like <yesno>, except that it allows for the generation of any input type - text,password,checkbox,radio,hidden and textarea - all with the same type of functionality of <yesno>. I would also like to know if anyone has some spare time to contribute to the servlet re-building. Tim has made a great start with the UML doc, we now just need to move forward and begin implementation. If anyone can help out with that, it would be greatly appreciated. Thanks Marc |
|
From: Marc B. <mbo...@ya...> - 2002-04-02 04:37:38
|
Hello, I have added some new features to the new IDRS website including the first "Success Stories" article as well as the papers section. The news is actually real news and was generated using the IDRS. I'd really appreciate it if I could get some feedback on how the site looks/feels and the information on it. Here's the link: http://idrs.sourceforge.net/newsite/ Thanks Marc |
|
From: Marc B. <mbo...@ya...> - 2002-04-01 04:23:39
|
The new idrs website now has consistent and auto generated news. check it out at http://idrs.sourceforge.net/newsite/ Marc |
|
From: Marc B. <mbo...@ya...> - 2002-03-29 05:32:42
|
Hello All, I am happy to announce that the IDRS' web site is being completly re-built. A common complaint I have had is that the site is difficult to navigate and needs a lot of work. Well, I have done this and begun re-building the web site. It is designed to be not only resourcefull, but aestheticly pleasing as well. While not complete, it can be viewed by going to : http://idrs.sourceforge.net/newsite/ I would appreciate any comments you have, as this site is the center of the IDRS community. Marc Boorshtein __________________________________________________ Do You Yahoo!? Yahoo! Greetings - send holiday greetings for Easter, Passover http://greetings.yahoo.com/ |
|
From: Marc B. <mbo...@ya...> - 2002-03-26 04:15:57
|
Use your discretion. Marc On Mon, 2002-03-25 at 19:47, Tim Urberg wrote: > Hello Marc, > > I was looking at the UML document and I remember you mentioned wanting > to break out the Init class. Do you still want me to do this? I can > look for patterns like I did with the other classes. I was also > wondering if you could give me more of an overview of what you're > looking for to examine and refine. > > My plan is to get the UML document looking good and then start coding > based off of it. Once I get that done, I'll try to install the new code > onto my linux box here and get it working on Tomcat and MySQL. Then > it's test time! > > Thanks, > Tim > > Marc Boorshtein wrote: > > >Ok, great. Begin examining and refining the UML document and the > >process flow for request handling and authentication. You go guy on the > >servlet while I finish of the compilation process. Also take into > >account the exceptions in the exceptions package. The new servlet > >should have error checking built in. Eventually I want form entry to be > >a 2 page process, one for input and one for results. If something goes > >wrong, the page should be reloaded and there will be special tags that > >will detect if there had been an error and display the issue. Don't > >worry about this yet though, just know that is our dirrection. > > > >Marc > > > > > _______________________________________________ > Idrs-dev mailing list > Idr...@li... > https://lists.sourceforge.net/lists/listinfo/idrs-dev |
|
From: Tim U. <urb...@us...> - 2002-03-26 00:39:17
|
Hello Marc, I was looking at the UML document and I remember you mentioned wanting to break out the Init class. Do you still want me to do this? I can look for patterns like I did with the other classes. I was also wondering if you could give me more of an overview of what you're looking for to examine and refine. My plan is to get the UML document looking good and then start coding based off of it. Once I get that done, I'll try to install the new code onto my linux box here and get it working on Tomcat and MySQL. Then it's test time! Thanks, Tim Marc Boorshtein wrote: >Ok, great. Begin examining and refining the UML document and the >process flow for request handling and authentication. You go guy on the >servlet while I finish of the compilation process. Also take into >account the exceptions in the exceptions package. The new servlet >should have error checking built in. Eventually I want form entry to be >a 2 page process, one for input and one for results. If something goes >wrong, the page should be reloaded and there will be special tags that >will detect if there had been an error and display the issue. Don't >worry about this yet though, just know that is our dirrection. > >Marc > |
|
From: Marc B. <mbo...@ya...> - 2002-03-23 04:56:36
|
Hello everyone. I have added a new tag, <setprops>. This tag is part of the <object> tag and allows for the IDRS to follow the Java Bean specs by having a setXXX property for each parameter in the form obj-prop_name. Here's how it works: If there is a property in the class Test called setProp(String), use the setprops tag in this way: <object id="testObj"> <class>Test</class> <constructor> </constructor> <setprops>true</setprops> </object> Then, have a parameter in the calling HTML form called testObj-prop_Prop. This will autimaticlly set setProp to the value of testObj-prop_Prop. Marc |
|
From: Marc B. <mbo...@ya...> - 2002-03-14 15:31:27
|
Ok, great. Begin examining and refining the UML document and the process flow for request handling and authentication. You go guy on the servlet while I finish of the compilation process. Also take into account the exceptions in the exceptions package. The new servlet should have error checking built in. Eventually I want form entry to be a 2 page process, one for input and one for results. If something goes wrong, the page should be reloaded and there will be special tags that will detect if there had been an error and display the issue. Don't worry about this yet though, just know that is our dirrection. Marc On Wed, 2002-03-13 at 20:38, Tim Urberg wrote: > Hello Marc, > > I'm ready to continue working on the servlet re-vamp when you are. I > haven't looked at it in a while. I was wondering if you could give me > some direction as to what to work on next, then we can go from there. > Thanks. > > Tim > > Marc Boorshtein wrote: > > >A big leap forward has been made for the IDRS. The IDRS compilation is > >now based on a 100% xml dialect (with a schema and everything)!!!! For > >those who have not yet viewed the project description on the web site, > >here's the jist of it: > > > >1. The current RML Specification is now the RML Macro Scpecification > >2. There is now an RML schema as well as a transformation document > > > >On compilation the following steps occurr in a pipeline: > > > >RML Macro Page ----Macro To XML Translator---> XML Page conforming to > >RML schema ---SAX Parsing of document---> Compilation units ----> RML > >Object Tree > > > >All the major functionality seems to work (though I haven't thouroughly > >tested everything). I have updated InsertToIDRS as well as the > >deployment tool. With this in place, as well as Tim's work on the > >servlet part I think we now have a clear path to IDRS 2.0: > > > >1. Finish testing XML compilation > >2. Update documentation for XML compilation > >3. Polish the compilation system for more descriptive errors for easier > >RML development > >4. Add the <navnext> and <navprev> tags in conjunction with > >data-paging, a feature that was in IDRS 1.5, but not in 2.0 as yet. > >5. Add a <set-properties> tag to the <object> tag. This will allow for > >beans to be used in the IDRS with shorted <method> tags. > >6. Finish servlet re-vamp (I will help Tim on this once I have > >completed the RML front-end work) > >7. Add documentation to cover advanced business logic, file upload, and > >page design. > > > >TEST TEST TEST > > > >With this done we will have reached IDRS 2.0 and a real heavy hitting > >web development platform! > > > >Marc Boorshtein > > > > > > > > > >_______________________________________________ > >Idrs-dev mailing list > >Idr...@li... > >https://lists.sourceforge.net/lists/listinfo/idrs-dev > > > > > > > > _______________________________________________ > Idrs-dev mailing list > Idr...@li... > https://lists.sourceforge.net/lists/listinfo/idrs-dev |
|
From: Tim U. <urb...@us...> - 2002-03-14 01:30:54
|
Hello Marc, I'm ready to continue working on the servlet re-vamp when you are. I haven't looked at it in a while. I was wondering if you could give me some direction as to what to work on next, then we can go from there. Thanks. Tim Marc Boorshtein wrote: >A big leap forward has been made for the IDRS. The IDRS compilation is >now based on a 100% xml dialect (with a schema and everything)!!!! For >those who have not yet viewed the project description on the web site, >here's the jist of it: > >1. The current RML Specification is now the RML Macro Scpecification >2. There is now an RML schema as well as a transformation document > >On compilation the following steps occurr in a pipeline: > >RML Macro Page ----Macro To XML Translator---> XML Page conforming to >RML schema ---SAX Parsing of document---> Compilation units ----> RML >Object Tree > >All the major functionality seems to work (though I haven't thouroughly >tested everything). I have updated InsertToIDRS as well as the >deployment tool. With this in place, as well as Tim's work on the >servlet part I think we now have a clear path to IDRS 2.0: > >1. Finish testing XML compilation >2. Update documentation for XML compilation >3. Polish the compilation system for more descriptive errors for easier >RML development >4. Add the <navnext> and <navprev> tags in conjunction with >data-paging, a feature that was in IDRS 1.5, but not in 2.0 as yet. >5. Add a <set-properties> tag to the <object> tag. This will allow for >beans to be used in the IDRS with shorted <method> tags. >6. Finish servlet re-vamp (I will help Tim on this once I have >completed the RML front-end work) >7. Add documentation to cover advanced business logic, file upload, and >page design. > >TEST TEST TEST > >With this done we will have reached IDRS 2.0 and a real heavy hitting >web development platform! > >Marc Boorshtein > > > > >_______________________________________________ >Idrs-dev mailing list >Idr...@li... >https://lists.sourceforge.net/lists/listinfo/idrs-dev > > |
|
From: Marc B. <mbo...@ya...> - 2002-03-04 23:39:19
|
A big leap forward has been made for the IDRS. The IDRS compilation is now based on a 100% xml dialect (with a schema and everything)!!!! For those who have not yet viewed the project description on the web site, here's the jist of it: 1. The current RML Specification is now the RML Macro Scpecification 2. There is now an RML schema as well as a transformation document On compilation the following steps occurr in a pipeline: RML Macro Page ----Macro To XML Translator---> XML Page conforming to RML schema ---SAX Parsing of document---> Compilation units ----> RML Object Tree All the major functionality seems to work (though I haven't thouroughly tested everything). I have updated InsertToIDRS as well as the deployment tool. With this in place, as well as Tim's work on the servlet part I think we now have a clear path to IDRS 2.0: 1. Finish testing XML compilation 2. Update documentation for XML compilation 3. Polish the compilation system for more descriptive errors for easier RML development 4. Add the <navnext> and <navprev> tags in conjunction with data-paging, a feature that was in IDRS 1.5, but not in 2.0 as yet. 5. Add a <set-properties> tag to the <object> tag. This will allow for beans to be used in the IDRS with shorted <method> tags. 6. Finish servlet re-vamp (I will help Tim on this once I have completed the RML front-end work) 7. Add documentation to cover advanced business logic, file upload, and page design. TEST TEST TEST With this done we will have reached IDRS 2.0 and a real heavy hitting web development platform! Marc Boorshtein |
|
From: Marc B. <mbo...@ya...> - 2002-02-28 00:04:57
|
Hey everyone, I've finally added file upload support to the idrs! The addition is transparent though. When a form's method is port and it's enctype is multipart/form-data the net.sourceforge.idrs.core.servlet.MultiPartRequest is used to parse the request. The nice thing is that there are no temporary files, everything is stored in memory as byte arrays. When a file needs to be saved, call the getMultiPartRequest() method of the idrs scripter object. Once you have the MultiPartRequest, call saveFile(key,path) to save it. Marc |
|
From: Tim U. <urb...@us...> - 2002-02-20 02:13:17
|
Hello Marc, I'm going to start to look at stream lining Init first. Do you want me to look at breaking it out into smaller classes as well? I also took a look at a tutorial on Tomcat's Realms. There is a Realm interface that they implement with JDBCRealm, SecurityRealm, MemoryRealm, ect. I wonder if the easiest thing to do would be to implement Tomcat's Realm interface to provide our implementation, that's if we're allowed to do so. Anyway, let me know what you think. Thanks, Tim Marc Boorshtein wrote: >Sounds good tim, > >As for reflection, I check out the September 2001 Java Developers >Journal online. I think they have free access t their archives. If >not, I know that JavaPro does. As for next steps... Lets refine the uml >doc, then I want to take a look at Init and stream line things their. >Primarily the handling of db connection creation and using connections >for loading of docs, authentication... > >If you get a chance, try and study Tomcat's "Realms" and see how they >work. I don't know much about them, but I think thats the idea we want >to have when dealing with outside roucources. > >MArc > >On Fri, 2002-02-15 at 16:54, Tim Urberg wrote: > >>Hello Marc, >> >>That does clear things up a little. I think I might look online or find a book >>that helps explain that a little more. I'll take a look at the changes you >>made to the UML doc and see what you have in there. Let me know what the next >>step is. Thanks, >> >>Tim >> >> >>--- Marc Boorshtein <mbo...@ya...> wrote: >> >>>Ok.... >>> >>>Now I understand the nature of you question, how will a plugable API >>>work? >>> >>>Here's how I usually do it using some reflection: >>>1. THe Abstract class or Interface that will define the api must have >>>an empty constructor >>> >>>2. As an initialization argument to the servlet, a full class name of >>>an implementation class must be specified >>> >>>3. Execute code similar to this >>>IDRSSecurity secure = (IDRSSecurity) Class.forName(implementationClass); >>> >>>Now as long as the String implementationClass is the full class name >>>(package and all) of the implementation, we can access it using the >>>pre-defined interface. This allows us to not have to know what the >>>evenutal implemntation will be. >>> >>>I hope this clears the matter up. >>> >>>Marc >>> >>> >>>On Fri, 2002-02-15 at 12:51, Tim Urberg wrote: >>> >>>>Hello Marc, >>>> >>>>Let me re-word my question. Currently, the servlet package uses the >>>>IDRSSecrity in a number of classes. If we make it an interface or >>>> >>>abstract, >>> >>>>how would I use the IDRSSecurity in the servlet package once it is >>>> >>>abstract? I >>> >>>>really haven't done anything with pluggable API's so I'm curious as to how >>>> >>>we >>> >>>>would implement this and the Pooling code. >>>> >>>>Let me know your thoughts. >>>>Thanks, >>>>Tim >>>> >>>> >>>>--- Marc Boorshtein <mbo...@ya...> wrote: >>>> >>>>>Tim, >>>>> >>>>>>>As for the IDRSSecurity being abstract, how would we implement the >>>>>>>pluggable security? I ask this because several of the classes in the >>>>>>> >>>>>>>servlet package use it and in order for them to use it, I need to >>>>>>> >>>extend >>> >>>>>it. >>>>> >>>>>I don't see where classes extend IDRSSecurity in your UML diagram. >>>>>Perhaps I misunderstood the question? As I would see it, Wherever >>>>>IDRSSecurity is needed, the variable would be declared as IDRSSecurity, >>>>>thus allowing for the the extended version of IDRSSecurity to be used >>>>>using IDRSSecurity's interface. I hope this helps. >>>>> >>>>>Marc >>>>> >>>>>_______________________________________________ >>>>>Idrs-dev mailing list >>>>>Idr...@li... >>>>>https://lists.sourceforge.net/lists/listinfo/idrs-dev >>>>> >>>>> >>>>> >>>> >>>>__________________________________________________ >>>>Do You Yahoo!? >>>>Got something to say? Say it better with Yahoo! Video Mail >>>>http://mail.yahoo.com >>>> >>>>_______________________________________________ >>>>Idrs-dev mailing list >>>>Idr...@li... >>>>https://lists.sourceforge.net/lists/listinfo/idrs-dev >>>> >> >>__________________________________________________ >>Do You Yahoo!? >>Got something to say? Say it better with Yahoo! Video Mail >>http://mail.yahoo.com >> >>_______________________________________________ >>Idrs-dev mailing list >>Idr...@li... >>https://lists.sourceforge.net/lists/listinfo/idrs-dev >> > > >_______________________________________________ >Idrs-dev mailing list >Idr...@li... >https://lists.sourceforge.net/lists/listinfo/idrs-dev > > |
