Ok: Heres what I want to do with babeldoc: Do away with the whole properties thing and try and replace it with the spring framework.
Firstly I need a volunteer to keep version 1.x going. Names please.
Secondly we need to explore Spring. The parts of the current properties files Is this worth the effort? What else should we be doing in the java exchange business. Code is always appreciated. Here are some ideas:
1, Properties implemented in XML Databases like Exist and Xindice. Standard interface using XMLdb interface classes or XML-RPC or SOAP.
2. More gui components. We need lots of work on swing bits and pieces. Drawing pipelines using jgraph might be a good idea.
3. Decide on a security model. JAAS or what?
4. Spring configuration and / or properties files configuration. Both I am thinking, where the properties files can invoke objects from Spring BeanFactory. I think it is compatible with we what we have.
Bruce.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Bruce,
This sounds pretty cool. I like Spring and building next generation of Babeldoc on the top of it could good idea. Do you have some code to show more details? What does it mean to current pipeline stages/scanner workers and other classes that can be extended by users?
What about pipeline configurations? Would they stay the same or they should be rewritten to be used on Babeldoc 2.x?
Dejan
P.S.
Unfortunatelly, I don't use Babeldoc too much, so I didn't work on it for quite long time. I did fixed some bugs we encountered in company (pipelines we built in last few years are still working) but some big plans we had with it didn't came true. This could change in next few months so it could happen that I would have much more time for it!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok: Heres what I want to do with babeldoc: Do away with the whole properties thing and try and replace it with the spring framework.
Firstly I need a volunteer to keep version 1.x going. Names please.
Secondly we need to explore Spring. The parts of the current properties files Is this worth the effort? What else should we be doing in the java exchange business. Code is always appreciated. Here are some ideas:
1, Properties implemented in XML Databases like Exist and Xindice. Standard interface using XMLdb interface classes or XML-RPC or SOAP.
2. More gui components. We need lots of work on swing bits and pieces. Drawing pipelines using jgraph might be a good idea.
3. Decide on a security model. JAAS or what?
4. Spring configuration and / or properties files configuration. Both I am thinking, where the properties files can invoke objects from Spring BeanFactory. I think it is compatible with we what we have.
Bruce.
Bruce,
This sounds pretty cool. I like Spring and building next generation of Babeldoc on the top of it could good idea. Do you have some code to show more details? What does it mean to current pipeline stages/scanner workers and other classes that can be extended by users?
What about pipeline configurations? Would they stay the same or they should be rewritten to be used on Babeldoc 2.x?
Dejan
P.S.
Unfortunatelly, I don't use Babeldoc too much, so I didn't work on it for quite long time. I did fixed some bugs we encountered in company (pipelines we built in last few years are still working) but some big plans we had with it didn't came true. This could change in next few months so it could happen that I would have much more time for it!