[JBoss Tools (users)] - Re: Feedback on the Smooks editor
by mzeijen
I understand that you want to release it. Most developers probably don't try Beta or RC releases. I do hope that not everybody runs into the same critical problems with the graph editor as I did.
Regarding to your questions:
How are we going to handle multiple versions of Smooks if the tooling become dependent on the runtime it self?
That is a very good question. I have an idea how to solve that. By creating a custom classloader repository for each version of Smooks, you can provide support for multiple Smooks versions. In the java project the user needs to configure which Smooks version he uses. The Smooks editor can then dynamically use the classloader repository that belongs to that version. I believe that creating this classloader system is probably easier then creating Smooks independent readers, for every input source that Smooks supports.
Are the Smooks readers capable of handling partial documents which is how users normally edit files.
I hope I get what you mean with the question. As long as the reader gets a syntax correct file, it will be able to create a data structure from it. It is then up to the editor to decide if the structure is compatible enough against the data structure it may already have. But that wouldn't probably be any different then what it now already does for it's XML or Java source.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216859#4216859
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216859
17 years, 1 month
[Persistence, JBoss/CMP, Hibernate, Database] - Datasource is not very JCA like
by b.eckenfels
Hello,
the JBoss (loxal-tx/xa/no)-transaction datasource for JDBC is not very RA like. It is mapping logical connections rather 1:1 to JDBC connections from the underlying Datasource or driver.
This has some implications, for example that a lot of idle connections from beans will as well result in real idle JDBC connections (if the DB driver itself is not a smart pool). It also means that broken connections could be recovered in some cases more easyly if the DB pool would hand out logical jdbc connections to the clients, and bind the more losely to physical connectios.
In the JMS Area we have an JMS-RA which is made for that, it will provide logical connections and bind them on demand to physical JMS resources.
Am I missing an obvious solution for JDBC (other than looking into other pools).
For oracle I am planning to go with the caching datasource in order to use some of the more advanced failover features, however that will not work for other DBs and the transparency with JMX into the pool statistics seems not be given (yet).
Is this the right Forum or should I go over to the JCA/DataSource group with the discussion?
Greetings
Bernd
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216858#4216858
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216858
17 years, 1 month
![img]http://xmedeko.googlepages.com/eclipse1.PNG[/img](http://img]http://xmedeko.googlepages.com/eclipse1.PNG[/img){kind=link}
![img]http://xmedeko.googlepages.com/eclipse2.PNG[/img](http://img]http://xmedeko.googlepages.com/eclipse2.PNG[/img){kind=link}