[jira] Resolved: (TUSCANY-720) DAS Companyweb sample missing companyConfig.xml
[ http://issues.apache.org/jira/browse/TUSCANY-720?page=all ] Brent Daniel resolved TUSCANY-720. -- Resolution: Fixed > DAS Companyweb sample missing companyConfig.xml > --- > > Key: TUSCANY-720 > URL: http://issues.apache.org/jira/browse/TUSCANY-720 > Project: Tuscany > Issue Type: Bug > Components: Java DAS Samples >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende > Fix For: Java-M2 > > Attachments: tuscany720.lresende.20060912.txt > > > The companyweb sample war file is missing the companyConfig.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-441) Remove DAS use of Class variable to trigger logging.
[ http://issues.apache.org/jira/browse/TUSCANY-441?page=all ] Brent Daniel resolved TUSCANY-441. -- Resolution: Fixed > Remove DAS use of Class variable to trigger logging. > > > Key: TUSCANY-441 > URL: http://issues.apache.org/jira/browse/TUSCANY-441 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Assigned To: Luciano Resende > Fix For: Java-Mx > > Attachments: lresende.tuscany441.20060913.txt > > > DAS uses jsr-47 logging behind a utility class and is triggered by a class > variable being true. The utility class needs to be removed to allow clients > to enable logging without having to recompile implementation classes or set > the class variable at runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-726) Update apache legal headers on some resource files
[ http://issues.apache.org/jira/browse/TUSCANY-726?page=all ] Brent Daniel resolved TUSCANY-726. -- Resolution: Fixed > Update apache legal headers on some resource files > -- > > Key: TUSCANY-726 > URL: http://issues.apache.org/jira/browse/TUSCANY-726 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende > Fix For: Java-M2 > > Attachments: tuscany726.lresende.20060914.txt > > > I noticed some resources files were still with the old version of the > headers > This JIRA takes care of these files by updating the contents of the headers > based on the info available at : http://www.apache.org/legal/src-headers.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-740) Misleading exception when SDO does not find definition for specific column
[ http://issues.apache.org/jira/browse/TUSCANY-740?page=all ] Brent Daniel reassigned TUSCANY-740: Assignee: Brent Daniel > Misleading exception when SDO does not find definition for specific column > -- > > Key: TUSCANY-740 > URL: http://issues.apache.org/jira/browse/TUSCANY-740 > Project: Tuscany > Issue Type: Bug > Components: Java BigBank Scenario, Java SDO Implementation >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Brent Daniel > Fix For: Java-M2 > > > While working on Bigbank, was getting the following exception : > Exception in thread "main" java.lang.NullPointerException > at > org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDerivedStructuralFeatureID(BasicEObjectImpl.java:1072) > at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet > (BasicEObjectImpl.java:650) > at org.apache.tuscany.sdo.impl.DataObjectImpl.set(DataObjectImpl.java:140) > at > org.apache.tuscany.das.rdb.graphbuilder.impl.DataObjectMaker.createAndAddDataObject(DataObjectMaker.java > :90) > at > org.apache.tuscany.das.rdb.graphbuilder.impl.ResultSetProcessor.addRowToGraph(ResultSetProcessor.java:126) > at > org.apache.tuscany.das.rdb.graphbuilder.impl.ResultSetProcessor.processResultSet(ResultSetProcessor.java > :97) > at > org.apache.tuscany.das.rdb.graphbuilder.impl.ResultSetProcessor.processResults(ResultSetProcessor.java:81) > at > org.apache.tuscany.das.rdb.impl.ReadCommandImpl.buildGraph(ReadCommandImpl.java:92) > at > org.apache.tuscany.das.rdb.impl.ReadCommandImpl.executeQuery(ReadCommandImpl.java:61) > at > bigbank.account.services.accountdb.AccountDBInit.testStrockPurchaseThroughDAS(AccountDBInit.java:271) > at bigbank.account.services.accountdb.AccountDBInit.main > (AccountDBInit.java:466) > This was due to a mismatch between data returned from the query and the > generated DataObject model. The query in this case is doing "select * > from stocks", which will return columns ID, Symbol, Quantity, > purchasePrice, purchaseDate, and purchaseLotNumber. The wsdl used to > generated the SDO model doesn't have an ID column. Looking at > AccountDBInit, it looks like ID is supposed to identify a customer. > Nothing in the StockSummary type in the wsdl looks like it corresponds > to this. > Regardless, we need to return a meaningful exception for this rather > than the NPE from SDO. > See discussion thread for details : > http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg08177.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-740) Misleading exception when SDO does not find definition for specific column
[ http://issues.apache.org/jira/browse/TUSCANY-740?page=all ] Brent Daniel resolved TUSCANY-740. -- Resolution: Fixed > Misleading exception when SDO does not find definition for specific column > -- > > Key: TUSCANY-740 > URL: http://issues.apache.org/jira/browse/TUSCANY-740 > Project: Tuscany > Issue Type: Bug > Components: Java BigBank Scenario, Java SDO Implementation >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Brent Daniel > Fix For: Java-M2 > > > While working on Bigbank, was getting the following exception : > Exception in thread "main" java.lang.NullPointerException > at > org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDerivedStructuralFeatureID(BasicEObjectImpl.java:1072) > at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet > (BasicEObjectImpl.java:650) > at org.apache.tuscany.sdo.impl.DataObjectImpl.set(DataObjectImpl.java:140) > at > org.apache.tuscany.das.rdb.graphbuilder.impl.DataObjectMaker.createAndAddDataObject(DataObjectMaker.java > :90) > at > org.apache.tuscany.das.rdb.graphbuilder.impl.ResultSetProcessor.addRowToGraph(ResultSetProcessor.java:126) > at > org.apache.tuscany.das.rdb.graphbuilder.impl.ResultSetProcessor.processResultSet(ResultSetProcessor.java > :97) > at > org.apache.tuscany.das.rdb.graphbuilder.impl.ResultSetProcessor.processResults(ResultSetProcessor.java:81) > at > org.apache.tuscany.das.rdb.impl.ReadCommandImpl.buildGraph(ReadCommandImpl.java:92) > at > org.apache.tuscany.das.rdb.impl.ReadCommandImpl.executeQuery(ReadCommandImpl.java:61) > at > bigbank.account.services.accountdb.AccountDBInit.testStrockPurchaseThroughDAS(AccountDBInit.java:271) > at bigbank.account.services.accountdb.AccountDBInit.main > (AccountDBInit.java:466) > This was due to a mismatch between data returned from the query and the > generated DataObject model. The query in this case is doing "select * > from stocks", which will return columns ID, Symbol, Quantity, > purchasePrice, purchaseDate, and purchaseLotNumber. The wsdl used to > generated the SDO model doesn't have an ID column. Looking at > AccountDBInit, it looks like ID is supposed to identify a customer. > Nothing in the StockSummary type in the wsdl looks like it corresponds > to this. > Regardless, we need to return a meaningful exception for this rather > than the NPE from SDO. > See discussion thread for details : > http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg08177.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-758) Handle databases that don't support generated keys
Handle databases that don't support generated keys -- Key: TUSCANY-758 URL: http://issues.apache.org/jira/browse/TUSCANY-758 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Reporter: Brent Daniel Some databases don't support the JDBC functionality that returns generated keys. Currently in the DAS we always use the JDBC RETURN_GENERATED_KEYS option when we create a Statement. Some databases will throw an exception when this happens rather than just ignore it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-758) Handle databases that don't support generated keys
[ http://issues.apache.org/jira/browse/TUSCANY-758?page=all ] Brent Daniel reassigned TUSCANY-758: Assignee: Brent Daniel > Handle databases that don't support generated keys > -- > > Key: TUSCANY-758 > URL: http://issues.apache.org/jira/browse/TUSCANY-758 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > Some databases don't support the JDBC functionality that returns generated > keys. Currently in the DAS we always use the JDBC RETURN_GENERATED_KEYS > option when we create a Statement. Some databases will throw an exception > when this happens rather than just ignore it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-758) Handle databases that don't support generated keys
[ http://issues.apache.org/jira/browse/TUSCANY-758?page=all ] Brent Daniel closed TUSCANY-758. Resolution: Fixed > Handle databases that don't support generated keys > -- > > Key: TUSCANY-758 > URL: http://issues.apache.org/jira/browse/TUSCANY-758 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > Some databases don't support the JDBC functionality that returns generated > keys. Currently in the DAS we always use the JDBC RETURN_GENERATED_KEYS > option when we create a Statement. Some databases will throw an exception > when this happens rather than just ignore it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-277) Need better handling of null Connection objects
[ http://issues.apache.org/jira/browse/TUSCANY-277?page=all ] Brent Daniel closed TUSCANY-277. Resolution: Fixed > Need better handling of null Connection objects > --- > > Key: TUSCANY-277 > URL: http://issues.apache.org/jira/browse/TUSCANY-277 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Brent Daniel > Fix For: Java-Mx > > > An invalid Connection definition in the Config will result in a > NullPointerException in ReadCommandImpl when it tries to do setAutoCommit() > on the Connection object -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-769) Improve DAS distribution to include any provided legal text file into the distribution
[ http://issues.apache.org/jira/browse/TUSCANY-769?page=comments#action_12439220 ] Brent Daniel commented on TUSCANY-769: -- What files need to be picked up other than LICENSE and NOTICE? I hesitate to put in a wildcard in case some build artifact with a .txt extension is added later. > Improve DAS distribution to include any provided legal text file into the > distribution > -- > > Key: TUSCANY-769 > URL: http://issues.apache.org/jira/browse/TUSCANY-769 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB, Java DAS Samples >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende > Fix For: Java-M2 > > Attachments: tuscany769.lresende.20060930.txt > > > Currently DAS distribution only look for LICENSE and NOTICE text files. > I want to update the distribution assembly to get any provided text files > into the distribution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-807) DAS Header Files Updates
[ http://issues.apache.org/jira/browse/TUSCANY-807?page=all ] Brent Daniel resolved TUSCANY-807. -- Resolution: Fixed > DAS Header Files Updates > > > Key: TUSCANY-807 > URL: http://issues.apache.org/jira/browse/TUSCANY-807 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende >Priority: Critical > Fix For: Java-M2 > > Attachments: tuscany807.lresende.20061009.txt > > > As reported by Daniel Kulp, some DAS files are missing legal header >http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg09256.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-808) DAS Samples Header files updates
[ http://issues.apache.org/jira/browse/TUSCANY-808?page=all ] Brent Daniel resolved TUSCANY-808. -- Resolution: Fixed > DAS Samples Header files updates > > > Key: TUSCANY-808 > URL: http://issues.apache.org/jira/browse/TUSCANY-808 > Project: Tuscany > Issue Type: Bug > Components: Java DAS Samples >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende >Priority: Critical > Fix For: Java-M2 > > Attachments: tuscany808.lresende.20061009.txt > > > As reported by Daniel Kulp, some DAS files are missing legal header >http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg09256.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-820) Configuration info for Command Parameters should include an "index"
[ http://issues.apache.org/jira/browse/TUSCANY-820?page=all ] Brent Daniel reassigned TUSCANY-820: Assignee: Brent Daniel > Configuration info for Command Parameters should include an "index" > --- > > Key: TUSCANY-820 > URL: http://issues.apache.org/jira/browse/TUSCANY-820 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Assigned To: Brent Daniel > Fix For: Java-Mx > > > The configuration for command parameters should include an index. As an > example, the current SP example with an OUT parameter has the following > associated config file: > xsi:noNamespaceSchemaLocation="http:///org.apache.tuscany.das.rdb/config.xsd"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > kind="procedure"> > > > > > In keeping with our philosophy that only config that needs to vary from the > defaults should be provided, the first parameter should not need to be > defined since it is of the default IN type. However, removing the first > parameter definition results in the following error. > > java.lang.RuntimeException: SQL Exception: Parameter 1 cannot be registered > as an OUT parameter because it is an IN parameter. > at > org.apache.tuscany.das.rdb.impl.SPCommandImpl.executeQuery(SPCommandImpl.java:73) > at > org.apache.tuscany.das.rdb.test.StoredProcs.testGetNamedCustomers(StoredProcs.java:116) > > I assume this error is caused by the runtime inferring index positionally > from the config input and the first parameter is necessary as a place holder > in order for the OUT parameter to properly have an index of 2. > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-828) Update companyweb.war location in sample distribution
[ http://issues.apache.org/jira/browse/TUSCANY-828?page=all ] Brent Daniel resolved TUSCANY-828. -- Resolution: Fixed > Update companyweb.war location in sample distribution > - > > Key: TUSCANY-828 > URL: http://issues.apache.org/jira/browse/TUSCANY-828 > Project: Tuscany > Issue Type: Bug > Components: Java DAS Samples >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende >Priority: Minor > Fix For: Java-M2 > > Attachments: tuscany828.lresende.20061011.txt > > > Move CompanyWeb.war to root directory of the distribution as per comments > from M2 RC2 >http://www.mail-archive.com/tuscany-user%40ws.apache.org/msg00270.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-834) Missing version information for junit plugin in das pom.xml
[ http://issues.apache.org/jira/browse/TUSCANY-834?page=all ] Brent Daniel resolved TUSCANY-834. -- Resolution: Fixed > Missing version information for junit plugin in das pom.xml > --- > > Key: TUSCANY-834 > URL: http://issues.apache.org/jira/browse/TUSCANY-834 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende >Priority: Minor > Fix For: Java-M2 > > Attachments: tuscany834.lresende.20061012.txt > > > DAS RDB pom has no version information for junit dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-835) "Version" column should default to "managed = true"
[ http://issues.apache.org/jira/browse/TUSCANY-835?page=all ] Brent Daniel reassigned TUSCANY-835: Assignee: Brent Daniel > "Version" column should default to "managed = true" > --- > > Key: TUSCANY-835 > URL: http://issues.apache.org/jira/browse/TUSCANY-835 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Assigned To: Brent Daniel > Fix For: Java-Mx > > > This is fine with me. Most of the time users will probably want to > have the DAS do the work rather than manually updating the version > column or having a database trigger do it. > Brent > On 10/12/06, Kevin Williams <[EMAIL PROTECTED]> wrote: > > While writing the User level documentation for Optimistic Concurrency > > Control I started wondering about our current default which is to NOT > > manage the designated version column. That is, we assume that it is the > > client's responsibility to modify this column whenever they modify any > > other column in the associated row. > > > > We also provide another option in which the DAS is responsible for > > bumping the value of the designated column whenever any other column is > > modified in the associated row. It seems to me that this will be the > > typical case and should also be the default to save the developer from > > specifying another piece of config. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-835) "Version" column should default to "managed = true"
[ http://issues.apache.org/jira/browse/TUSCANY-835?page=all ] Brent Daniel resolved TUSCANY-835. -- Resolution: Fixed > "Version" column should default to "managed = true" > --- > > Key: TUSCANY-835 > URL: http://issues.apache.org/jira/browse/TUSCANY-835 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Assigned To: Brent Daniel > Fix For: Java-Mx > > > This is fine with me. Most of the time users will probably want to > have the DAS do the work rather than manually updating the version > column or having a database trigger do it. > Brent > On 10/12/06, Kevin Williams <[EMAIL PROTECTED]> wrote: > > While writing the User level documentation for Optimistic Concurrency > > Control I started wondering about our current default which is to NOT > > manage the designated version column. That is, we assume that it is the > > client's responsibility to modify this column whenever they modify any > > other column in the associated row. > > > > We also provide another option in which the DAS is responsible for > > bumping the value of the designated column whenever any other column is > > modified in the associated row. It seems to me that this will be the > > typical case and should also be the default to save the developer from > > specifying another piece of config. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-820) Configuration info for Command Parameters should include an "index"
[ http://issues.apache.org/jira/browse/TUSCANY-820?page=all ] Brent Daniel resolved TUSCANY-820. -- Resolution: Fixed > Configuration info for Command Parameters should include an "index" > --- > > Key: TUSCANY-820 > URL: http://issues.apache.org/jira/browse/TUSCANY-820 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Assigned To: Brent Daniel > Fix For: Java-Mx > > > The configuration for command parameters should include an index. As an > example, the current SP example with an OUT parameter has the following > associated config file: > xsi:noNamespaceSchemaLocation="http:///org.apache.tuscany.das.rdb/config.xsd"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > kind="procedure"> > > > > > In keeping with our philosophy that only config that needs to vary from the > defaults should be provided, the first parameter should not need to be > defined since it is of the default IN type. However, removing the first > parameter definition results in the following error. > > java.lang.RuntimeException: SQL Exception: Parameter 1 cannot be registered > as an OUT parameter because it is an IN parameter. > at > org.apache.tuscany.das.rdb.impl.SPCommandImpl.executeQuery(SPCommandImpl.java:73) > at > org.apache.tuscany.das.rdb.test.StoredProcs.testGetNamedCustomers(StoredProcs.java:116) > > I assume this error is caused by the runtime inferring index positionally > from the config input and the first parameter is necessary as a place holder > in order for the OUT parameter to properly have an index of 2. > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-866) [DAS] Use overqualified update by default
[DAS] Use overqualified update by default - Key: TUSCANY-866 URL: http://issues.apache.org/jira/browse/TUSCANY-866 Project: Tuscany Issue Type: New Feature Components: Java DAS RDB Reporter: Brent Daniel Currently in the DAS we either use a user-defined version column or do not use any concurrency control. We have enough information to build an overqualified update in cases where a version column is not defined. For example, if a field "name" is changed from "Bob" to "John", we would generate a query such as: UPDATE CUSTOMER SET NAME = 'John' WHERE ID = 1 AND NAME = 'Bob' If the statement does not update any rows in the database, the DAS will throw a concurrency control exception. This scheme will not work in case of LONG VARCHAR, BLOB, or CLOB columns, so an exception should be thrown in that case indicating that a version column must be defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-893) Provide a utility to retrieve a URI from a Factory class
Provide a utility to retrieve a URI from a Factory class Key: TUSCANY-893 URL: http://issues.apache.org/jira/browse/TUSCANY-893 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: Brent Daniel Priority: Minor The DAS needs a utility in SDO that allows us to retrieve a namespace URI from a factory class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-903) Integration testing for SCA properties
Integration testing for SCA properties -- Key: TUSCANY-903 URL: http://issues.apache.org/jira/browse/TUSCANY-903 Project: Tuscany Issue Type: Test Components: Java SCA Core Reporter: Brent Daniel I have the start of some tests for component properties using the itest plugin that I would like to contribute to an integration test suite for tuscany. I plan on building on top of these, but would like to go ahead and contribute them and gather feedback so that we can nail down some basics. I will attach a patch with the current tests to this JIRA, but there are a few unresolved issues: 1) I'm not sure where these tests should live in the build. My proposal would be to place them in tuscany/java/sca/testing. 2) Will future integration tests be contained in one large bucket or will there be seperate buckets for various technology combinations? (ie, would there just be java/sca/testing or would there be java/sca/testing/properties, java/sca/testing/integrationWebapp, java/sca/testing/ws-bindings, etc?) 3) When does integration testing happen? Is it part of the main-line build or will it be required to run it seperately? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-903) Integration testing for SCA properties
[ http://issues.apache.org/jira/browse/TUSCANY-903?page=all ] Brent Daniel updated TUSCANY-903: - Attachment: propertyTests.txt Attaching propertyTests.txt, some simple integration tests for properties using the itest plugin. > Integration testing for SCA properties > -- > > Key: TUSCANY-903 > URL: http://issues.apache.org/jira/browse/TUSCANY-903 > Project: Tuscany > Issue Type: Test > Components: Java SCA Core >Reporter: Brent Daniel > Attachments: propertyTests.txt > > > I have the start of some tests for component properties using the itest > plugin that I would like to contribute to an integration test suite for > tuscany. I plan on building on top of these, but would like to go ahead and > contribute them and gather feedback so that we can nail down some basics. I > will attach a patch with the current tests to this JIRA, but there are a few > unresolved issues: > 1) I'm not sure where these tests should live in the build. My proposal would > be to place them in tuscany/java/sca/testing. > 2) Will future integration tests be contained in one large bucket or will > there be seperate buckets for various technology combinations? (ie, would > there just be java/sca/testing or would there be java/sca/testing/properties, > java/sca/testing/integrationWebapp, java/sca/testing/ws-bindings, etc?) > 3) When does integration testing happen? Is it part of the main-line build or > will it be required to run it seperately? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-905) FK references not correctly resolved when an alias is used
FK references not correctly resolved when an alias is used -- Key: TUSCANY-905 URL: http://issues.apache.org/jira/browse/TUSCANY-905 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Reporter: Brent Daniel There's a potential NPE in InsertGenerator.getAttributeProperties() and UpdateGenerator.getChangedFields() when foreign key fields have propertyName mappings. Both need to be updated to search for foreign key field Property objects by the propertyName. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-905) FK references not correctly resolved when an alias is used
[ http://issues.apache.org/jira/browse/TUSCANY-905?page=all ] Brent Daniel reassigned TUSCANY-905: Assignee: Brent Daniel > FK references not correctly resolved when an alias is used > -- > > Key: TUSCANY-905 > URL: http://issues.apache.org/jira/browse/TUSCANY-905 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > There's a potential NPE in InsertGenerator.getAttributeProperties() and > UpdateGenerator.getChangedFields() when foreign key fields have propertyName > mappings. Both need to be updated to search for foreign key field Property > objects by the propertyName. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-905) FK references not correctly resolved when an alias is used
[ http://issues.apache.org/jira/browse/TUSCANY-905?page=all ] Brent Daniel resolved TUSCANY-905. -- Resolution: Fixed > FK references not correctly resolved when an alias is used > -- > > Key: TUSCANY-905 > URL: http://issues.apache.org/jira/browse/TUSCANY-905 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > There's a potential NPE in InsertGenerator.getAttributeProperties() and > UpdateGenerator.getChangedFields() when foreign key fields have propertyName > mappings. Both need to be updated to search for foreign key field Property > objects by the propertyName. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-924) Many valued properties not supported
Many valued properties not supported Key: TUSCANY-924 URL: http://issues.apache.org/jira/browse/TUSCANY-924 Project: Tuscany Issue Type: Bug Components: Java SCA Core Reporter: Brent Daniel The SCA runtime currently does not support -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-925) Complex properties not supported
Complex properties not supported Key: TUSCANY-925 URL: http://issues.apache.org/jira/browse/TUSCANY-925 Project: Tuscany Issue Type: Bug Components: Java SCA Core Reporter: Brent Daniel This may be intented to be covered in TUSCANY-773, but it was not clear to me. Complex properties are currently not supported by the tuscany runtime. Caused by: java.lang.IllegalArgumentException: Complex property is not supported. at org.apache.tuscany.core.property.SimplePropertyObjectFactory.getInstance(SimplePropertyObjectFactory.java:56) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-937) Multiple test failures while connecting with MySQL
[ http://issues.apache.org/jira/browse/TUSCANY-937?page=all ] Brent Daniel resolved TUSCANY-937. -- Resolution: Fixed I didn't realize this JIRA was open - I committed changes to the MySQL test suite yesterday that resolve the problems with dog kennel and one of the stored procedure tests. > Multiple test failures while connecting with MySQL > -- > > Key: TUSCANY-937 > URL: http://issues.apache.org/jira/browse/TUSCANY-937 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Affects Versions: Java-Mx > Environment: MySQL and Win32 >Reporter: Luciano Resende > Assigned To: Brent Daniel > Fix For: Java-Mx > > > With the insertion of Dog Kennel, there are couple of tests failing with > invalid sql and inserts are also failing... > I'll use this JIRA to concentrate all changes to allow testing with MySQL > again -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-916) OCC recovery framework
[ http://issues.apache.org/jira/browse/TUSCANY-916?page=all ] Brent Daniel reassigned TUSCANY-916: Assignee: Brent Daniel > OCC recovery framework > -- > > Key: TUSCANY-916 > URL: http://issues.apache.org/jira/browse/TUSCANY-916 > Project: Tuscany > Issue Type: New Feature > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Assigned To: Brent Daniel > Fix For: Java-Mx > > > A framework to assist client in recovering from optimistic collision failures -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-866) [DAS] Use overqualified update by default
[ http://issues.apache.org/jira/browse/TUSCANY-866?page=all ] Brent Daniel reassigned TUSCANY-866: Assignee: Brent Daniel > [DAS] Use overqualified update by default > - > > Key: TUSCANY-866 > URL: http://issues.apache.org/jira/browse/TUSCANY-866 > Project: Tuscany > Issue Type: New Feature > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > Currently in the DAS we either use a user-defined version column or do not > use any concurrency control. We have enough information to build an > overqualified update in cases where a version column is not defined. For > example, if a field "name" is changed from "Bob" to "John", we would generate > a query such as: > UPDATE CUSTOMER SET NAME = 'John' WHERE ID = 1 AND NAME = 'Bob' > If the statement does not update any rows in the database, the DAS will throw > a concurrency control exception. > This scheme will not work in case of LONG VARCHAR, BLOB, or CLOB columns, so > an exception should be thrown in that case indicating that a version column > must be defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-866) [DAS] Use overqualified update by default
[ http://issues.apache.org/jira/browse/TUSCANY-866?page=all ] Brent Daniel resolved TUSCANY-866. -- Resolution: Fixed Fixed in revision 465025 > [DAS] Use overqualified update by default > - > > Key: TUSCANY-866 > URL: http://issues.apache.org/jira/browse/TUSCANY-866 > Project: Tuscany > Issue Type: New Feature > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > Currently in the DAS we either use a user-defined version column or do not > use any concurrency control. We have enough information to build an > overqualified update in cases where a version column is not defined. For > example, if a field "name" is changed from "Bob" to "John", we would generate > a query such as: > UPDATE CUSTOMER SET NAME = 'John' WHERE ID = 1 AND NAME = 'Bob' > If the statement does not update any rows in the database, the DAS will throw > a concurrency control exception. > This scheme will not work in case of LONG VARCHAR, BLOB, or CLOB columns, so > an exception should be thrown in that case indicating that a version column > must be defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-939) DAS Should throw an exception when ResultSetMetadata is invalid
[ http://issues.apache.org/jira/browse/TUSCANY-939?page=all ] Brent Daniel reassigned TUSCANY-939: Assignee: Brent Daniel > DAS Should throw an exception when ResultSetMetadata is invalid > --- > > Key: TUSCANY-939 > URL: http://issues.apache.org/jira/browse/TUSCANY-939 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Assigned To: Brent Daniel >Priority: Minor > Fix For: Java-Mx > > > This test seems to have strayed from its original purpose. > C:\apacheSVN\java\das\rdb\src\test\java\org\apache\tuscany\das\rdb\test\ResultSetShapeTests.java > "testReadSingleVerifyShapeUse" > The query used intentionally produces invalid ResultSetMetadata and there is > no ResultSetShape specified to override its use by the DAS. Since the test > assumes the ResultSetMetadata is invalid, I would expect the DAS to throw and > exception rather than return an invalid data graph which it seems to be doing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-939) DAS Should throw an exception when ResultSetMetadata is invalid
[ http://issues.apache.org/jira/browse/TUSCANY-939?page=all ] Brent Daniel resolved TUSCANY-939. -- Resolution: Fixed Fixed in revision 479744 > DAS Should throw an exception when ResultSetMetadata is invalid > --- > > Key: TUSCANY-939 > URL: http://issues.apache.org/jira/browse/TUSCANY-939 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Assigned To: Brent Daniel >Priority: Minor > Fix For: Java-Mx > > > This test seems to have strayed from its original purpose. > C:\apacheSVN\java\das\rdb\src\test\java\org\apache\tuscany\das\rdb\test\ResultSetShapeTests.java > "testReadSingleVerifyShapeUse" > The query used intentionally produces invalid ResultSetMetadata and there is > no ResultSetShape specified to override its use by the DAS. Since the test > assumes the ResultSetMetadata is invalid, I would expect the DAS to throw and > exception rather than return an invalid data graph which it seems to be doing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-951) NullPointerException when setting an invalid property
NullPointerException when setting an invalid property
-
Key: TUSCANY-951
URL: http://issues.apache.org/jira/browse/TUSCANY-951
Project: Tuscany
Issue Type: Bug
Components: Java SDO Implementation
Reporter: Brent Daniel
Calling set() with an invalid property name results in a NullPointerException.
For example:
dataObject.setInt("invalidProperty", 5);
results in:
java.lang.NullPointerException
at
org.apache.tuscany.sdo.util.DataObjectUtil.getSetValue(DataObjectUtil.java:1440)
at
org.apache.tuscany.sdo.util.DataObjectUtil.setInt(DataObjectUtil.java:537)
at
org.apache.tuscany.sdo.impl.DataObjectImpl.setInt(DataObjectImpl.java:526)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-954) Need to throw an exception when users try to set a relationship and FK property
Need to throw an exception when users try to set a relationship and FK property --- Key: TUSCANY-954 URL: http://issues.apache.org/jira/browse/TUSCANY-954 Project: Tuscany Issue Type: Improvement Components: Java DAS RDB Reporter: Brent Daniel The DAS resolves database foreign key columns in one of two ways. The value can come from the primary key property of a parent DataObject, or it can come directly from the foreign key property. The value must come from one or the other, so it is not legal to set both a relationship and a foreign key property for that relationship for a particular DataObject. The DAS needs to throw an exception in this case so that the behavior is clear. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-954) Need to throw an exception when users try to set a relationship and FK property
[ http://issues.apache.org/jira/browse/TUSCANY-954?page=all ] Brent Daniel reassigned TUSCANY-954: Assignee: Brent Daniel > Need to throw an exception when users try to set a relationship and FK > property > --- > > Key: TUSCANY-954 > URL: http://issues.apache.org/jira/browse/TUSCANY-954 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > The DAS resolves database foreign key columns in one of two ways. The value > can come from the primary key property of a parent DataObject, or it can come > directly from the foreign key property. The value must come from one or the > other, so it is not legal to set both a relationship and a foreign key > property for that relationship for a particular DataObject. The DAS needs to > throw an exception in this case so that the behavior is clear. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-961) DAS: Using deprected SDO method causes Type lookup failure
DAS: Using deprected SDO method causes Type lookup failure -- Key: TUSCANY-961 URL: http://issues.apache.org/jira/browse/TUSCANY-961 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Reporter: Brent Daniel The DAS is still using SDOUtil.createTypeHelper() rather than TypeHelper.INSTANCE. This causes the DAS to not have visibility of types defined by TypeHelper or XSDHelper. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-961) DAS: Using deprected SDO method causes Type lookup failure
[ http://issues.apache.org/jira/browse/TUSCANY-961?page=all ] Brent Daniel reassigned TUSCANY-961: Assignee: Brent Daniel > DAS: Using deprected SDO method causes Type lookup failure > -- > > Key: TUSCANY-961 > URL: http://issues.apache.org/jira/browse/TUSCANY-961 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > The DAS is still using SDOUtil.createTypeHelper() rather than > TypeHelper.INSTANCE. This causes the DAS to not have visibility of types > defined by TypeHelper or XSDHelper. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-968) Invalid FK columns causes NPE
Invalid FK columns causes NPE - Key: TUSCANY-968 URL: http://issues.apache.org/jira/browse/TUSCANY-968 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Reporter: Brent Daniel Specifying an invalid foreign key column in a relationship definition will cause a NullPointerException when trying to generate an update or insert statement. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-968) Invalid FK columns causes NPE
[ http://issues.apache.org/jira/browse/TUSCANY-968?page=all ] Brent Daniel reassigned TUSCANY-968: Assignee: Brent Daniel > Invalid FK columns causes NPE > - > > Key: TUSCANY-968 > URL: http://issues.apache.org/jira/browse/TUSCANY-968 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > Specifying an invalid foreign key column in a relationship definition will > cause a NullPointerException when trying to generate an update or insert > statement. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-968) Invalid FK columns causes NPE
[ http://issues.apache.org/jira/browse/TUSCANY-968?page=all ] Brent Daniel resolved TUSCANY-968. -- Resolution: Fixed > Invalid FK columns causes NPE > - > > Key: TUSCANY-968 > URL: http://issues.apache.org/jira/browse/TUSCANY-968 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > Specifying an invalid foreign key column in a relationship definition will > cause a NullPointerException when trying to generate an update or insert > statement. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-954) Need to throw an exception when users try to set a relationship and FK property
[ http://issues.apache.org/jira/browse/TUSCANY-954?page=all ] Brent Daniel resolved TUSCANY-954. -- Resolution: Fixed > Need to throw an exception when users try to set a relationship and FK > property > --- > > Key: TUSCANY-954 > URL: http://issues.apache.org/jira/browse/TUSCANY-954 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > The DAS resolves database foreign key columns in one of two ways. The value > can come from the primary key property of a parent DataObject, or it can come > directly from the foreign key property. The value must come from one or the > other, so it is not legal to set both a relationship and a foreign key > property for that relationship for a particular DataObject. The DAS needs to > throw an exception in this case so that the behavior is clear. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-957) DAS generates invalid INSERT statement when no properties are set on the new DO
[ http://issues.apache.org/jira/browse/TUSCANY-957?page=all ]
Brent Daniel reassigned TUSCANY-957:
Assignee: Brent Daniel
> DAS generates invalid INSERT statement when no properties are set on the new
> DO
> ---
>
> Key: TUSCANY-957
> URL: http://issues.apache.org/jira/browse/TUSCANY-957
> Project: Tuscany
> Issue Type: Bug
> Components: Java DAS RDB
>Affects Versions: Java-Mx
>Reporter: Kevin Williams
> Assigned To: Brent Daniel
> Fix For: Java-Mx
>
>
> If a new DO is created but no properties are set then the DAS generates an
> invalid INSERT statement that looks something like this:
> "insert into COMPANY( values ("
> The following test case (added to
> /das/src/test/java/org/apache/tuscany/das/rdb/test/GeneratedId.java)
> illustrates this bug:
> /**
> * Test insert into row with generated ID and no attributes set
> */
> public void testInsert5() throws Exception {
> DAS das = DAS.FACTORY.createDAS(getConfig("CompanyConfig.xml"),
> getConnection());
> Command select = das.getCommand("all companies");
> DataObject root = select.executeQuery();
> root.createDataObject("COMPANY");
> das.applyChanges(root);
> // Verify insert
> root = select.executeQuery();
> assertEquals(4, root.getList("COMPANY").size());
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-957) DAS generates invalid INSERT statement when no properties are set on the new DO
[ http://issues.apache.org/jira/browse/TUSCANY-957?page=all ]
Brent Daniel resolved TUSCANY-957.
--
Resolution: Fixed
Fixed in 482731
> DAS generates invalid INSERT statement when no properties are set on the new
> DO
> ---
>
> Key: TUSCANY-957
> URL: http://issues.apache.org/jira/browse/TUSCANY-957
> Project: Tuscany
> Issue Type: Bug
> Components: Java DAS RDB
>Affects Versions: Java-Mx
>Reporter: Kevin Williams
> Assigned To: Brent Daniel
> Fix For: Java-Mx
>
>
> If a new DO is created but no properties are set then the DAS generates an
> invalid INSERT statement that looks something like this:
> "insert into COMPANY( values ("
> The following test case (added to
> /das/src/test/java/org/apache/tuscany/das/rdb/test/GeneratedId.java)
> illustrates this bug:
> /**
> * Test insert into row with generated ID and no attributes set
> */
> public void testInsert5() throws Exception {
> DAS das = DAS.FACTORY.createDAS(getConfig("CompanyConfig.xml"),
> getConnection());
> Command select = das.getCommand("all companies");
> DataObject root = select.executeQuery();
> root.createDataObject("COMPANY");
> das.applyChanges(root);
> // Verify insert
> root = select.executeQuery();
> assertEquals(4, root.getList("COMPANY").size());
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1007) ApplyChnages fails when added DO does not include a modified property
[ http://issues.apache.org/jira/browse/TUSCANY-1007?page=comments#action_12459812 ] Brent Daniel commented on TUSCANY-1007: --- Kevin, I'm not sure what behavior you want here. The ID column in your test case is not a generated column. How do you want the DAS to pick an ID value? The issue with doing an empty insert with a generated ID column was fixed in tuscany-957. > ApplyChnages fails when added DO does not include a modified property > - > > Key: TUSCANY-1007 > URL: http://issues.apache.org/jira/browse/TUSCANY-1007 > Project: Tuscany > Issue Type: Bug >Reporter: Kevin Williams > > Looks like the generated insert is invalid when the change history for an > added DO does not include a modified property. I think the correct behavior > should be to generate an ID-only INSERT. An alternative would be to generate > an INSERT that initializes all columns ... i'd be interested in hearing > arguments to justify the latter. > This test: > > /das/src/test/java/org/apache/tuscany/das/rdb/test/CrudWithChangeHistory.testReadInsertApply() > demonstrates the problem. I have temporarily commented it out. > Here is the stack trace: > java.lang.RuntimeException: SQL Exception: Column 'ID' cannot accept a NULL > value. > at > org.apache.tuscany.das.rdb.impl.InsertCommandImpl.execute(InsertCommandImpl.java:47) > at > org.apache.tuscany.das.rdb.impl.ChangeOperation.execute(ChangeOperation.java:73) > at org.apache.tuscany.das.rdb.impl.Changes.execute(Changes.java:57) > at > org.apache.tuscany.das.rdb.impl.ApplyChangesCommandImpl.execute(ApplyChangesCommandImpl.java:69) > at > org.apache.tuscany.das.rdb.impl.DASImpl.applyChanges(DASImpl.java:244) > at > org.apache.tuscany.das.rdb.test.CrudWithChangeHistory.testReadInsertApply(CrudWithChangeHistory.java:289) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:615) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.extensions.TestSetup.run(TestSetup.java:23) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > Caused by: SQL Exception: Column 'ID' cannot accept a NULL value. > at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown > Source) > at > org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown > Source) > at > org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown > Source) > at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown > Source) > at > org.apache.tuscany.das.rdb.impl.Statement.executeUpdate(Statement.java:173) > at > org.apache.tuscany.das.rdb.impl.Statement.executeUpdate(Statement.java:133) > at > org.apache.tuscany.das.rdb.impl.InsertCommandImpl.execute(InsertCommandImpl.java:44) > ... 28 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
[jira] Created: (TUSCANY-1107) Multiple calls to getNamespaceContext
Multiple calls to getNamespaceContext - Key: TUSCANY-1107 URL: https://issues.apache.org/jira/browse/TUSCANY-1107 Project: Tuscany Issue Type: Improvement Components: Java SDO Implementation Reporter: Brent Daniel In SDOXMLHelperImpl, both getPrefix() and getURI() make calls to OMStAXWrapper.getNamespaceContext(). This causes multiple calls to getNamespaceContext each time an element is parsed. If possible, this value should be cached to increase performance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1960) JSONRPCServiceServlet should use getQueryString() instead of getParameter()
JSONRPCServiceServlet should use getQueryString() instead of getParameter()
---
Key: TUSCANY-1960
URL: https://issues.apache.org/jira/browse/TUSCANY-1960
Project: Tuscany
Issue Type: Bug
Components: Java SCA JSON-RPC Binding Extension
Affects Versions: Java-SCA-1.0.1
Reporter: Brent Daniel
Priority: Minor
The current JSONRPCServiceServlet uses the following code to handle SMD
requests:
if (request.getParameter("smd") != null) {
handleSMDRequest(request, response);
}
With some web containers, a path such as "/HelloWorldService?smd" will result
in request.getParameter("smd") returning null since no value is assigned to the
parameter. A better way to check would be to use getQueryString():
if ("smd".equalsIgnoreCase(request.getQueryString())) {
handleSMDRequest(request, response);
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1990) Helloworld-dojo sample not working on WebSphere 6.1
[
https://issues.apache.org/jira/browse/TUSCANY-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560169#action_12560169
]
Brent Daniel commented on TUSCANY-1990:
---
This should be resolved by TUSCANY-1960. WebSphere returns null for
"request.getParameter("smd")" when a URL of "/HelloWorldService?smd" is passed
in. This causes the JSONRPCServiceServlet to use handleServiceRequest() instead
of handleSMDRequest().
> Helloworld-dojo sample not working on WebSphere 6.1
> ---
>
> Key: TUSCANY-1990
> URL: https://issues.apache.org/jira/browse/TUSCANY-1990
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Samples
>Affects Versions: Java-SCA-1.1
> Environment: WebSphere Application Server 6.1.0.9
> Linux RHEL5
> Tuscany 1.1 RC1
>Reporter: Jean-Sebastien Delfino
> Fix For: Java-SCA-1.1
>
>
> Steps to reproduce the problem:
> - use ant package to build the helloworld-dojo sample WAR
> - install it by following the steps at
> http://jsdelfino.blogspot.com/2007/10/how-to-use-apache-tuscany-with.html
> - open http://localhost:8080/sample-helloworld-dojo-webapp/ in your Web
> browser
> The DOJO debug log section of the sample page will show the following error
> messages:
> [ Error: bad http response code:404 ]
> [ Error: Unable to load SMD from HelloWorldService?smd ]
> The WebSphere error log contains the following exception:
> Stack Dump = java.lang.RuntimeException: Unable to parse request
> at
> org.apache.tuscany.sca.binding.jsonrpc.JSONRPCServiceServlet.handleServiceRequest(JSONRPCServiceServlet.java:134)
> at
> org.apache.tuscany.sca.binding.jsonrpc.JSONRPCServiceServlet.service(JSONRPCServiceServlet.java:89)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
> at
> org.apache.tuscany.sca.host.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:102)
> at
> org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.doFilter(TuscanyServletFilter.java:88)
> at
> com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
> at
> com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
> at
> com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
> at
> com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:761)
> at
> com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:673)
> at
> com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:688)
> at
> com.ibm.ws.wswebcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:96)
> at
> com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.invokeFilters(DefaultExtensionProcessor.java:758)
> at
> com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:718)
> at
> com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:113)
> at
> com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3252)
> at
> com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:264)
> at
> com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
> at
> com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)
> at
> com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:112)
> at
> com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
> at
> com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
> at
> com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
> at
> com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
> at
> com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
> at
> com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
> at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
> at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
> at
> com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
> at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
> Caused by: java.text.ParseException: A JSONObject must begin with '{' at
> character 1 of
> at org.json.JSONTokener.syntaxError(JSONTokener.jav
[jira] Created: (TUSCANY-2057) Namespace information not preserved by ContributionMetadataProcessor.write()
Namespace information not preserved by ContributionMetadataProcessor.write() Key: TUSCANY-2057 URL: https://issues.apache.org/jira/browse/TUSCANY-2057 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.0.1 Reporter: Brent Daniel Namespace information is not preserved by ContributionMetadataProcessor.write(). You can reproduce this by modifying ContributionMetadataDocumentProcessorTestsCase.testLoad() to add a write at the end. The input XML is: private static final String VALID_XML = "" + "http://www.osoa.org/xmlns/sca/1.0\"; xmlns:helloworld=\"http://helloworld\";>" + "" + "" + ""; The output from ContributionMetadataProcessor.write() is: http://www.osoa.org/xmlns/sca/1.0";> -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-203) SDO: Calling getProperty() freezes property list
SDO: Calling getProperty() freezes property list Key: TUSCANY-203 URL: http://issues.apache.org/jira/browse/TUSCANY-203 Project: Tuscany Type: Bug Components: Java SDO Implementation Reporter: Brent Daniel Priority: Minor I'm trying to create properties for a Type. In this particular case, I'm checking to see if I've created the Property already. Calling Type.getProperty(String) causes a "property name to Property" Map object to be cached in ClassImpl. Any Property objects added to the Type after this will not be returned by Type.getProperty(String). I think I can remove this check without any issues for the time being, so this is a minor problem for me right now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TUSCANY-260) Backward pointing relationships in DAS Config not correct
Backward pointing relationships in DAS Config not correct - Key: TUSCANY-260 URL: http://issues.apache.org/jira/browse/TUSCANY-260 Project: Tuscany Type: Bug Components: Java DAS RDB Reporter: Brent Daniel Table.getConfig(), Relationship.getConfig(), Parameter.getCommand(), and others all return a String rather than the associated Config or Command object. These are intended to be the opposite side of the parent-child relationship. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TUSCANY-153) ChangeSummary on root data object not supported
[ http://issues.apache.org/jira/browse/TUSCANY-153?page=comments#action_12377619 ] Brent Daniel commented on TUSCANY-153: -- Frank, Our scenario is that we need to create a new Type that has reference properties to each Type in a set of generated types. This new type would correspond to the root object of the DataGraph. However, when we try to use DataGraph.createRootObject() with this Type, the create delegates to the generated package, which can't find our dynamic Type. When I brought this up, Steve suggested that we use SDO without a DataGraph. Is there a better way to accomplish this? > ChangeSummary on root data object not supported > --- > > Key: TUSCANY-153 > URL: http://issues.apache.org/jira/browse/TUSCANY-153 > Project: Tuscany > Type: Bug > Components: Java SDO Implementation > Reporter: Kevin Williams > > The RDB DAS intends to produce data graphs without using a DataGraph instance > and this requires us to attach a change history to the root DataObject. It > seems that this capability is not yet implemented. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TUSCANY-277) Need better handling of null Connection objects
Need better handling of null Connection objects --- Key: TUSCANY-277 URL: http://issues.apache.org/jira/browse/TUSCANY-277 Project: Tuscany Type: Improvement Components: Java DAS RDB Reporter: Brent Daniel An invalid Connection definition in the Config will result in a NullPointerException in ReadCommandImpl when it tries to do setAutoCommit() on the Connection object -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TUSCANY-278) DAS sometimes obtaining Connection objects twice
DAS sometimes obtaining Connection objects twice Key: TUSCANY-278 URL: http://issues.apache.org/jira/browse/TUSCANY-278 Project: Tuscany Type: Improvement Components: Java DAS RDB Reporter: Brent Daniel Priority: Minor When a CommandGroup is used, the DAS will obtain Connection objects twice. At initialization, individual runtime command objects will be created, which will cause each of them to obtain a Connection. Then, when the user requests a Command, the CommandGroup will obtain the Connection and set it on the Command object. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TUSCANY-153) ChangeSummary on root data object not supported
[ http://issues.apache.org/jira/browse/TUSCANY-153?page=comments#action_12377870 ] Brent Daniel commented on TUSCANY-153: -- I was creating the new Type with the same URI as the generated Types. When I change the URI to something unique, this seems to work. > ChangeSummary on root data object not supported > --- > > Key: TUSCANY-153 > URL: http://issues.apache.org/jira/browse/TUSCANY-153 > Project: Tuscany > Type: Bug > Components: Java SDO Implementation > Reporter: Kevin Williams > > The RDB DAS intends to produce data graphs without using a DataGraph instance > and this requires us to attach a change history to the root DataObject. It > seems that this capability is not yet implemented. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TUSCANY-406) DAS needs new parameter marker
DAS needs new parameter marker -- Key: TUSCANY-406 URL: http://issues.apache.org/jira/browse/TUSCANY-406 Project: Tuscany Type: Bug Components: Java DAS RDB Versions: Java-Mx Reporter: Brent Daniel The DAS currently uses paramater markers defined with a colon, eg, :param1. This causes a problem with our parsing when a client issues a query with colons in it, such as a query with a hardcoded time value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TUSCANY-186) Need APIs for CommandFactory (and probably CommandGroupFactory) to accept Config instance in addition to the current API for FileStream
[ http://issues.apache.org/jira/browse/TUSCANY-186?page=all ] Brent Daniel updated TUSCANY-186: - Attachment: commandgroup.txt CommandFactory was addressed earlier. This patch addresses CommandGroupFactory > Need APIs for CommandFactory (and probably CommandGroupFactory) to accept > Config instance in addition to the current API for FileStream > > > Key: TUSCANY-186 > URL: http://issues.apache.org/jira/browse/TUSCANY-186 > Project: Tuscany > Type: New Feature > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Fix For: Java-Mx > Attachments: commandgroup.txt > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-213) Errors in config model result in NPE rather than helpful error message
[ http://issues.apache.org/jira/browse/TUSCANY-213?page=all ] Brent Daniel updated TUSCANY-213: - Attachment: invalidConfig.txt The attached patch resolves the issue with relationship table names. > Errors in config model result in NPE rather than helpful error message > -- > > Key: TUSCANY-213 > URL: http://issues.apache.org/jira/browse/TUSCANY-213 > Project: Tuscany > Type: Bug > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Fix For: Java-Mx > Attachments: invalidConfig.txt > > Typos in the config.xml can lead to meaningless NPE errors. > For example, changing from the following change in > OrdersOrderDetailsConfig.xml > foreignKeyTable="ORDERDETAILS" many="true"> > > > to this ... > foreignKeyTable="ORDERDETAILS" many="true"> > > > results in a harsh NPE rather than of a cozy message exlaining that we are > sorry but we have no table/property named "" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-234) column names in config file that don't correspond to actual table names are silently ignored.
[ http://issues.apache.org/jira/browse/TUSCANY-234?page=comments#action_12413293 ] Brent Daniel commented on TUSCANY-234: -- This is a difficult one to address. One of the core design principles of the DAS is to not require configuration for information that can be inferred. Not finding a column in the config would be the normal case, and not an exception. Obviously, this causes some problems in this case where you want to specify config for a column, but it doesn't match the information pulled back from the ResultSet. Some possible solutions: 1) Implement a "Heavy Validation" mode, where we report warnings on columns in the ResultSetMetadata that don't have an equivalent in the Config, or vice versa. 2) Have some sort of validation tool outside of the runtime that accomplishes the same thing. 3) In this particular case, we may be able to catch exceptions that occur on data retrieval because of a lack of converter. At that point, we could throw an error telling the user to either write a converter or check the config to make sure the converter was specified correctly. This would work in cases where the converter is doing a class conversion, but wouldn't be as useful for other types of converters. > column names in config file that don't correspond to actual table names are > silently ignored. > - > > Key: TUSCANY-234 > URL: http://issues.apache.org/jira/browse/TUSCANY-234 > Project: Tuscany > Type: Bug > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Rick Rineholt > Fix For: Java-Mx > > When adding a converter in the config file my case mis matched to the column > name this is related to TUSCANY-233 but it seems that if there are no > matches altogether there is no check. An exception needs to be thrown that > states the table and column that was searched for. Without a fix like this > it can real difficult for the end user to isolate this error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-436) Some DAS tests can never fail
Some DAS tests can never fail
-
Key: TUSCANY-436
URL: http://issues.apache.org/jira/browse/TUSCANY-436
Project: Tuscany
Type: Bug
Components: Java DAS RDB
Reporter: Brent Daniel
Priority: Minor
In ExceptionTests, testEmptyStream() and testEmptyStream2() can never fail.
They both do something like this:
try {
...
fail("Error should be thrown");
} catch (Error e) {
...
}
JUnit's fail() method throws a subclass of Error, so it is impossible for this
to fail. The exception that is expected from the DAS runtime in these tests is
also an Error, so the runtime will need to be modified to fix this. The DAS
should not be using Error anyway, as it is intended for abnormal and
unrecoverable errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-436) Some DAS tests can never fail
[ http://issues.apache.org/jira/browse/TUSCANY-436?page=all ]
Brent Daniel updated TUSCANY-436:
-
Attachment: tuscany436.txt
Attaching a patch for this issue
> Some DAS tests can never fail
> -
>
> Key: TUSCANY-436
> URL: http://issues.apache.org/jira/browse/TUSCANY-436
> Project: Tuscany
> Type: Bug
> Components: Java DAS RDB
> Reporter: Brent Daniel
> Priority: Minor
> Attachments: tuscany436.txt
>
> In ExceptionTests, testEmptyStream() and testEmptyStream2() can never fail.
> They both do something like this:
> try {
>...
> fail("Error should be thrown");
> } catch (Error e) {
> ...
> }
> JUnit's fail() method throws a subclass of Error, so it is impossible for
> this to fail. The exception that is expected from the DAS runtime in these
> tests is also an Error, so the runtime will need to be modified to fix this.
> The DAS should not be using Error anyway, as it is intended for abnormal and
> unrecoverable errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-231) Need to replace use of ResultSetShape with Config's ResultDescriptor
[ http://issues.apache.org/jira/browse/TUSCANY-231?page=comments#action_12414785 ] Brent Daniel commented on TUSCANY-231: -- We need to investigate some the architecture a bit before we can do this. Currently, a ResultDescriptor instance is scoped to a Command. If we move over completely to ResultDescriptor, users will have to use a CommandGroup with defined Commands to pass in a shape. This takes away the simple option of creating a Command directly and passing in an instance of ResultSetShape, and moves further towards a model where users have to specify a complex config file before they can accomplish simple tasks. Maybe this is OK, but we need to step back and decide if this is what we want. > Need to replace use of ResultSetShape with Config's ResultDescriptor > > > Key: TUSCANY-231 > URL: http://issues.apache.org/jira/browse/TUSCANY-231 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Fix For: Java-Mx > > We need to convert to using the config-defined ResultDescriptor instead of > ResultSetShape for user provided result sahpe metadata. As part of this > effort, we should consider the impications of having this in the config > instance. My concern is that,currently, the config instance allows one > desriptor instance. This instance applies to all queries in the config which > may not be the best approach since COmmandGroups allow for multiple queries. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-442) Clean up DAS Configuration model
[ http://issues.apache.org/jira/browse/TUSCANY-442?page=all ] Brent Daniel reassigned TUSCANY-442: Assign To: Brent Daniel > Clean up DAS Configuration model > > > Key: TUSCANY-442 > URL: http://issues.apache.org/jira/browse/TUSCANY-442 > Project: Tuscany > Type: Bug > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > > The DAS Configuration model needs to be scrubbed. Here are a few items I > have identified: >. Table should have "tableName" and "typeName" rather than "name" and > "propertyName" >. Column should have "columnName" rather than "name" >. Parameter should contain "direction" >. DriverManager info should be removed from ConnectionProperties since it > is resonable for clients to pass a connection in non-managed environments >. . If DriverManager info is removed then ConnectionProperties can > probably be replaced with "DataSourceName" attribute on Config -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-466) [DAS] Generate SDO for test cases at build time
[DAS] Generate SDO for test cases at build time --- Key: TUSCANY-466 URL: http://issues.apache.org/jira/browse/TUSCANY-466 Project: Tuscany Type: Improvement Components: Java DAS RDB Reporter: Brent Daniel Priority: Minor The DAS is currently generating its config model at build time, but there are a couple ofl generated SDO models for the DAS tests that are checked into the repository. The build should generate SDO from customer.xsd and company.xsd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-469) Collpase CommandFactory and CommandGroup
[ http://issues.apache.org/jira/browse/TUSCANY-469?page=all ] Brent Daniel reassigned TUSCANY-469: Assign To: Brent Daniel > Collpase CommandFactory and CommandGroup > > > Key: TUSCANY-469 > URL: http://issues.apache.org/jira/browse/TUSCANY-469 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > > These two interfaces provide too much overlapping capability. Lets collapse > the two into a new interface and rename it "DAS" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-469) Collpase CommandFactory and CommandGroup
[ http://issues.apache.org/jira/browse/TUSCANY-469?page=all ] Brent Daniel updated TUSCANY-469: - Attachment: daspatch.txt Changes to the das runtime for Tuscany-469. CommandGroup has been renamed to DAS. > Collpase CommandFactory and CommandGroup > > > Key: TUSCANY-469 > URL: http://issues.apache.org/jira/browse/TUSCANY-469 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > Attachments: bigbank.txt, daspatch.txt > > These two interfaces provide too much overlapping capability. Lets collapse > the two into a new interface and rename it "DAS" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-469) Collpase CommandFactory and CommandGroup
[ http://issues.apache.org/jira/browse/TUSCANY-469?page=all ] Brent Daniel updated TUSCANY-469: - Attachment: bigbank.txt Changes to the BigBank sample required by Tuscany-469 > Collpase CommandFactory and CommandGroup > > > Key: TUSCANY-469 > URL: http://issues.apache.org/jira/browse/TUSCANY-469 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > Attachments: bigbank.txt, daspatch.txt > > These two interfaces provide too much overlapping capability. Lets collapse > the two into a new interface and rename it "DAS" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-469) Collpase CommandFactory and CommandGroup
[ http://issues.apache.org/jira/browse/TUSCANY-469?page=all ] Brent Daniel updated TUSCANY-469: - Attachment: companyweb.txt Changes to the DAS company sample required by Tuscany-469 > Collpase CommandFactory and CommandGroup > > > Key: TUSCANY-469 > URL: http://issues.apache.org/jira/browse/TUSCANY-469 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > Attachments: bigbank.txt, companyweb.txt, daspatch.txt > > These two interfaces provide too much overlapping capability. Lets collapse > the two into a new interface and rename it "DAS" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-466) [DAS] Generate SDO for test cases at build time
[ http://issues.apache.org/jira/browse/TUSCANY-466?page=all ] Brent Daniel reassigned TUSCANY-466: Assign To: Brent Daniel > [DAS] Generate SDO for test cases at build time > --- > > Key: TUSCANY-466 > URL: http://issues.apache.org/jira/browse/TUSCANY-466 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Reporter: Brent Daniel > Assignee: Brent Daniel > Priority: Minor > > The DAS is currently generating its config model at build time, but there are > a couple ofl generated SDO models for the DAS tests that are checked into the > repository. The build should generate SDO from customer.xsd and company.xsd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-466) [DAS] Generate SDO for test cases at build time
[ http://issues.apache.org/jira/browse/TUSCANY-466?page=all ] Brent Daniel updated TUSCANY-466: - Attachment: sdogen.txt Patch to generate SDO models at build time. Also, one config xml file needed to be updated to support changes that were made to the generator at some point. > [DAS] Generate SDO for test cases at build time > --- > > Key: TUSCANY-466 > URL: http://issues.apache.org/jira/browse/TUSCANY-466 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Reporter: Brent Daniel > Assignee: Brent Daniel > Priority: Minor > Attachments: sdogen.txt > > The DAS is currently generating its config model at build time, but there are > a couple ofl generated SDO models for the DAS tests that are checked into the > repository. The build should generate SDO from customer.xsd and company.xsd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-475) Class cast exception on
[ http://issues.apache.org/jira/browse/TUSCANY-475?page=all ]
Brent Daniel updated TUSCANY-475:
-
Component: Java SDO Implementation
(was: Java DAS RDB)
The indexing here should start at 1. As for the error, when you try to use a
zero index it should probably be handled the way other out of bounds indices
are handled, by throwing an IndexOutOfBoundsException. Assigning this over to
the SDO component.
> Class cast exception on
> ---
>
> Key: TUSCANY-475
> URL: http://issues.apache.org/jira/browse/TUSCANY-475
> Project: Tuscany
> Type: Bug
> Components: Java SDO Implementation
> Versions: Java-M1
> Environment: Windows XP
> Reporter: Simon Laws
>
> I'm trying to retrieve rows from a database via the relational DAS. When I
> run my test prgram I get
> Exception in thread "main" java.lang.ClassCastException:
> org.eclipse.emf.ecore.util.EcoreEList$Dynamic incompatible with
> commonj.sdo.DataObject
> at
> org.apache.tuscany.sdo.impl.DataObjectImpl.getDataObject(DataObjectImpl.java:322)
> at
> org.apache.tuscany.sdo.interop.SDOInterop.testReadAndWriteRelationalDB2(SDOInterop.java)
> at org.apache.tuscany.sdo.interop.SDOInterop.main(SDOInterop.java:136)
> The code looks like.
> CommandGroup commandGroup =
> CommandGroup.FACTORY.createCommandGroup(getClass().getResourceAsStream("interopconfig-db2.xml"));
> Command read = commandGroup.getCommand("all type");
> DataObject root = read.executeQuery();
> DataObject firstRow = root.getDataObject("alltype[0]");
> Now I expect to get a "firstRow" DataObject back. Indeed
> DataObjectImpl.getDataObject() casts the return to a DataObject
> public DataObject getDataObject(String path)
> {
> return (DataObject)get(path);
> }
> However the the DataObjectUtil.get() operation creates an Accessor and calls
> getAndRecycle
> public static Object get(DataObject dataObject, String path)
> {
> Property property = dataObject.getType().getProperty(path);
> if (property != null) {
> return dataObject.get(property);
> } else {
> return Accessor.create((EObject)dataObject, path).getAndRecyle();
> }
> }
> getAndRecycle call get which, because I have specified a 0 index, just
> returns the value which happens to be of type EcoreEList$Dynamic
> So while I may have an error in my code somewhere or it might not be
> retrieving any data from the database a class cast exception inside of SDO
> doesn't seem like the correct way to tell me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-231) Need to replace use of ResultSetShape with Config's ResultDescriptor
[ http://issues.apache.org/jira/browse/TUSCANY-231?page=all ] Brent Daniel updated TUSCANY-231: - Attachment: tuscany231.txt Patch for this issue. > Need to replace use of ResultSetShape with Config's ResultDescriptor > > > Key: TUSCANY-231 > URL: http://issues.apache.org/jira/browse/TUSCANY-231 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Fix For: Java-Mx > Attachments: tuscany231.txt > > We need to convert to using the config-defined ResultDescriptor instead of > ResultSetShape for user provided result sahpe metadata. As part of this > effort, we should consider the impications of having this in the config > instance. My concern is that,currently, the config instance allows one > desriptor instance. This instance applies to all queries in the config which > may not be the best approach since COmmandGroups allow for multiple queries. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-231) Need to replace use of ResultSetShape with Config's ResultDescriptor
[ http://issues.apache.org/jira/browse/TUSCANY-231?page=all ] Brent Daniel reassigned TUSCANY-231: Assign To: Brent Daniel > Need to replace use of ResultSetShape with Config's ResultDescriptor > > > Key: TUSCANY-231 > URL: http://issues.apache.org/jira/browse/TUSCANY-231 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > Attachments: tuscany231.txt > > We need to convert to using the config-defined ResultDescriptor instead of > ResultSetShape for user provided result sahpe metadata. As part of this > effort, we should consider the impications of having this in the config > instance. My concern is that,currently, the config instance allows one > desriptor instance. This instance applies to all queries in the config which > may not be the best approach since COmmandGroups allow for multiple queries. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-493) [DAS] Converter load needs to use appropriate classloader
[DAS] Converter load needs to use appropriate classloader - Key: TUSCANY-493 URL: http://issues.apache.org/jira/browse/TUSCANY-493 Project: Tuscany Type: Bug Components: Java DAS RDB Reporter: Brent Daniel Loading of converters by classname is currently using Class.forName(). This won't work if the converter is only available in the application classloader. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-483) Some refactoring is necessary after adding the DAS/CommandGroup
[ http://issues.apache.org/jira/browse/TUSCANY-483?page=all ] Brent Daniel reassigned TUSCANY-483: Assign To: Brent Daniel > Some refactoring is necessary after adding the DAS/CommandGroup > --- > > Key: TUSCANY-483 > URL: http://issues.apache.org/jira/browse/TUSCANY-483 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > > It is apparent that we need to go back and refactor after adding the DAS > interface (formerly CommandGroup) and the addition of the ConfigHelper. I > think we can base this refactoring on the following assumptions: > 1. Config can be built up with the ConfigHelper > 2. Config can be loaded from a Config file > 3. Config can only be applied to a DAS (via a factory method) > 4. Commands can only be got from a DAS > Some specific items we should consider: > 1. Connection instance should be provided to a DAS instance via a factory > method > 2. SDO ObjectModel is really part of the configuration and should be > specified in the config rather than in a factory method or a setter on Command > 3. Keys are defined in the Config and so "Key" can be removed from the > interface package > 4. Parameter can be removed from the interface package > 5. SDODataTypes just labels and caches SDO Data Types from SDO TypeHelper > and can be removed > 6. Converter can be removed from Config.ResultDesriptor > 7. "addParameter" method can be removed from Command > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-483) Some refactoring is necessary after adding the DAS/CommandGroup
[ http://issues.apache.org/jira/browse/TUSCANY-483?page=all ] Brent Daniel updated TUSCANY-483: - Attachment: tuscany438.txt Attaching a patch for this issue. This is, again, a rather large patch because of the number of test cases affected by the programming model change. > Some refactoring is necessary after adding the DAS/CommandGroup > --- > > Key: TUSCANY-483 > URL: http://issues.apache.org/jira/browse/TUSCANY-483 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > Attachments: tuscany438.txt > > It is apparent that we need to go back and refactor after adding the DAS > interface (formerly CommandGroup) and the addition of the ConfigHelper. I > think we can base this refactoring on the following assumptions: > 1. Config can be built up with the ConfigHelper > 2. Config can be loaded from a Config file > 3. Config can only be applied to a DAS (via a factory method) > 4. Commands can only be got from a DAS > Some specific items we should consider: > 1. Connection instance should be provided to a DAS instance via a factory > method > 2. SDO ObjectModel is really part of the configuration and should be > specified in the config rather than in a factory method or a setter on Command > 3. Keys are defined in the Config and so "Key" can be removed from the > interface package > 4. Parameter can be removed from the interface package > 5. SDODataTypes just labels and caches SDO Data Types from SDO TypeHelper > and can be removed > 6. Converter can be removed from Config.ResultDesriptor > 7. "addParameter" method can be removed from Command > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-483) Some refactoring is necessary after adding the DAS/CommandGroup
[ http://issues.apache.org/jira/browse/TUSCANY-483?page=all ] Brent Daniel updated TUSCANY-483: - Attachment: tuscany438b.txt Attaching a patch file that contains only the changes to the BigBank sample required by the API change here. > Some refactoring is necessary after adding the DAS/CommandGroup > --- > > Key: TUSCANY-483 > URL: http://issues.apache.org/jira/browse/TUSCANY-483 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > Attachments: tuscany438.txt, tuscany438b.txt > > It is apparent that we need to go back and refactor after adding the DAS > interface (formerly CommandGroup) and the addition of the ConfigHelper. I > think we can base this refactoring on the following assumptions: > 1. Config can be built up with the ConfigHelper > 2. Config can be loaded from a Config file > 3. Config can only be applied to a DAS (via a factory method) > 4. Commands can only be got from a DAS > Some specific items we should consider: > 1. Connection instance should be provided to a DAS instance via a factory > method > 2. SDO ObjectModel is really part of the configuration and should be > specified in the config rather than in a factory method or a setter on Command > 3. Keys are defined in the Config and so "Key" can be removed from the > interface package > 4. Parameter can be removed from the interface package > 5. SDODataTypes just labels and caches SDO Data Types from SDO TypeHelper > and can be removed > 6. Converter can be removed from Config.ResultDesriptor > 7. "addParameter" method can be removed from Command > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-278) DAS sometimes obtaining Connection objects twice
[ http://issues.apache.org/jira/browse/TUSCANY-278?page=comments#action_12417836 ] Brent Daniel commented on TUSCANY-278: -- The changes in Tuscany 483 make this issue go away. > DAS sometimes obtaining Connection objects twice > > > Key: TUSCANY-278 > URL: http://issues.apache.org/jira/browse/TUSCANY-278 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Brent Daniel > Priority: Minor > Fix For: Java-Mx > > When a CommandGroup is used, the DAS will obtain Connection objects twice. At > initialization, individual runtime command objects will be created, which > will cause each of them to obtain a Connection. Then, when the user requests > a Command, the CommandGroup will obtain the Connection and set it on the > Command object. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-278) DAS sometimes obtaining Connection objects twice
[ http://issues.apache.org/jira/browse/TUSCANY-278?page=all ] Brent Daniel closed TUSCANY-278: Resolution: Fixed > DAS sometimes obtaining Connection objects twice > > > Key: TUSCANY-278 > URL: http://issues.apache.org/jira/browse/TUSCANY-278 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Brent Daniel > Priority: Minor > Fix For: Java-Mx > > When a CommandGroup is used, the DAS will obtain Connection objects twice. At > initialization, individual runtime command objects will be created, which > will cause each of them to obtain a Connection. Then, when the user requests > a Command, the CommandGroup will obtain the Connection and set it on the > Command object. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-481) Config.Column.type is not used
[ http://issues.apache.org/jira/browse/TUSCANY-481?page=all ] Brent Daniel reassigned TUSCANY-481: Assign To: Brent Daniel > Config.Column.type is not used > -- > > Key: TUSCANY-481 > URL: http://issues.apache.org/jira/browse/TUSCANY-481 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > > We need to either determine a purpose for this attribute or get rid of it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-493) [DAS] Converter load needs to use appropriate classloader
[ http://issues.apache.org/jira/browse/TUSCANY-493?page=all ] Brent Daniel reassigned TUSCANY-493: Assign To: Brent Daniel > [DAS] Converter load needs to use appropriate classloader > - > > Key: TUSCANY-493 > URL: http://issues.apache.org/jira/browse/TUSCANY-493 > Project: Tuscany > Type: Bug > Components: Java DAS RDB > Reporter: Brent Daniel > Assignee: Brent Daniel > > Loading of converters by classname is currently using Class.forName(). This > won't work if the converter is only available in the application classloader. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-153) ChangeSummary on root data object not supported
[ http://issues.apache.org/jira/browse/TUSCANY-153?page=all ] Brent Daniel updated TUSCANY-153: - Attachment: tuscany153.jar I'm attaching a copy of the test case that was discussed on the dev list. > ChangeSummary on root data object not supported > --- > > Key: TUSCANY-153 > URL: http://issues.apache.org/jira/browse/TUSCANY-153 > Project: Tuscany > Type: Bug > Components: Java SDO Implementation > Versions: Java-Mx > Reporter: Kevin Williams > Fix For: Java-Mx > Attachments: tuscany153.jar > > The RDB DAS intends to produce data graphs without using a DataGraph instance > and this requires us to attach a change history to the root DataObject. It > seems that this capability is not yet implemented. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-528) Implementation clean up after removing named parameters
[ http://issues.apache.org/jira/browse/TUSCANY-528?page=all ] Brent Daniel reassigned TUSCANY-528: Assign To: Brent Daniel > Implementation clean up after removing named parameters > --- > > Key: TUSCANY-528 > URL: http://issues.apache.org/jira/browse/TUSCANY-528 > Project: Tuscany > Type: Improvement > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > > The option to use named parameters has been removed from the Command > interaface. The runtime needs some cleanup and maybe refactoring to optimize > around indexed-only parameters. Some test cases still need to be cleaned up > too. For example, some of the Config files still specify SQL with named > parameters. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-533) Need to add a new config entity to specify passive use of the connection
[ http://issues.apache.org/jira/browse/TUSCANY-533?page=all ] Brent Daniel reassigned TUSCANY-533: Assign To: Brent Daniel > Need to add a new config entity to specify passive use of the connection > > > Key: TUSCANY-533 > URL: http://issues.apache.org/jira/browse/TUSCANY-533 > Project: Tuscany > Type: Bug > Components: Java DAS RDB > Versions: Java-Mx > Reporter: Kevin Williams > Assignee: Brent Daniel > Fix For: Java-Mx > > Need to modify the config model to specify passive use of the connection (no > commit/rollback). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-552) CompanyWeb sample problem
[ http://issues.apache.org/jira/browse/TUSCANY-552?page=all ] Brent Daniel reassigned TUSCANY-552: Assignee: Brent Daniel > CompanyWeb sample problem > - > > Key: TUSCANY-552 > URL: http://issues.apache.org/jira/browse/TUSCANY-552 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > > The companyWeb sample is not working. It looks like its config file was not > updated in response to DAS changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-552) CompanyWeb sample problem
CompanyWeb sample problem - Key: TUSCANY-552 URL: http://issues.apache.org/jira/browse/TUSCANY-552 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Reporter: Brent Daniel The companyWeb sample is not working. It looks like its config file was not updated in response to DAS changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-560) DAS: managedtx attribute can default to false
DAS: managedtx attribute can default to false - Key: TUSCANY-560 URL: http://issues.apache.org/jira/browse/TUSCANY-560 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Reporter: Brent Daniel Assigned To: Brent Daniel If ConnectionInfo is specified, but the managedtx attribute is not, managedtx will default to false instead of true. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-579) getString on Date field results in IllegalArgumentException
[ http://issues.apache.org/jira/browse/TUSCANY-579?page=all ]
Brent Daniel updated TUSCANY-579:
-
Component/s: Java SDO Implementation
> getString on Date field results in IllegalArgumentException
> ---
>
> Key: TUSCANY-579
> URL: http://issues.apache.org/jira/browse/TUSCANY-579
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
>Reporter: Brian Murray
>
> On page 146 of V2.01 of the spec, it is stated that conversion from Date to
> String is supported. However, getString on Date type results in an
> IllegalArgumentException. Here is a code segment:
> public void testShowErrorsInSimpleFormat() throws Exception
> {
> DataObject test_obj = DataFactory.INSTANCE.create(API_TEST_TYPE);
> Date current_date = new Date(System.currentTimeMillis());
> // getString does not work on Date type
> test_obj.setDate("dateVal", current_date);
> String returned_string = test_obj.getString("dateVal"); //Gives
> IllegalArgumentException
> }
>And here is the XSD:
> http://www.w3.org/2001/XMLSchema";
> xmlns:sdo="commonj.sdo"
> xmlns:simple="http://www.example.com/api_test";
> targetNamespace="http://www.example.com/api_test";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> name="children" type="simple:APITest"/>
>
>
>
>
>
> I originally thought that also getDate was not working on String, but this
> was an error in my test case. I had been setting the String value to be
> Date.toString(). Fuhwei correctly pointed out that the String format that
> would allow conversion is given on page 72 of the specification and is
> different than what is returned by Date.toString(). I have tested with the
> correct String format and found that getDate works, so clearly this is not an
> error. However, I wonder if it would be a good idea to aditionally support
> the String format that results from Date.toString().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-578) Exceptions thrown by SDO runtime not the same as defined in the spec
[ http://issues.apache.org/jira/browse/TUSCANY-578?page=all ] Brent Daniel updated TUSCANY-578: - Summary: Exceptions thrown by SDO runtime not the same as defined in the spec (was: NullPointerException when expecting IllegalArgumentException) Description: On page 27 of V2.01 of the spec, specific exceptions are listed for certain kinds of errors. In some cases, a different exception is thrown (each case will be added as a subtask). Either the specification or the implementation should be updated. (was: On page 27 of V2.01 of the spec, it is stated that both .get(-1) and .get(getInstanceProperties().size() + 1) should result in an IllegalArgumentException. However, each results in a NullPointerException. Either the behavior or the specification should be updated.) Edited on Brian's request > Exceptions thrown by SDO runtime not the same as defined in the spec > > > Key: TUSCANY-578 > URL: http://issues.apache.org/jira/browse/TUSCANY-578 > Project: Tuscany > Issue Type: Bug > Components: Java SDO Implementation >Reporter: Brian Murray >Priority: Minor > > On page 27 of V2.01 of the spec, specific exceptions are listed for certain > kinds of errors. In some cases, a different exception is thrown (each case > will be added as a subtask). Either the specification or the implementation > should be updated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-581) IllegalArgumentException when expecting ClassCastException
[ http://issues.apache.org/jira/browse/TUSCANY-581?page=all ]
Brent Daniel updated TUSCANY-581:
-
Priority: Minor (was: Major)
Reduced priority to "Minor" based on Brian's request.
> IllegalArgumentException when expecting ClassCastException
> --
>
> Key: TUSCANY-581
> URL: http://issues.apache.org/jira/browse/TUSCANY-581
> Project: Tuscany
> Issue Type: Sub-task
> Components: Java SDO Implementation
>Reporter: Brian Murray
>Priority: Minor
>
> In V2.01 (dated November 2005) of the SDO specification it is stated in the
> table on page 28 that a ClassCastException is expected when get cannot
> convert from a value to the requested type. However, in many instances an
> IllegalArgumentException is instead thrown.
> Here is the example explicitly mentioned in the table as throwing a
> ClassCastException (getDate on a float value), however an
> IllegalArgumentException is seen in the test case.
>// IllegalArgumentException when expecting ClassCastException
>test_obj.setFloat("floatVal", Float.MAX_VALUE);
>test_obj.getDate("floatVal");
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-583) Add a method to SDOUtil to return all Types associated with a specific URI
Add a method to SDOUtil to return all Types associated with a specific URI -- Key: TUSCANY-583 URL: http://issues.apache.org/jira/browse/TUSCANY-583 Project: Tuscany Issue Type: New Feature Components: Java SDO Implementation Reporter: Brent Daniel Priority: Minor The DAS needs a way to get a list of the Types for a specific URI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-584) DAS - Failures in mysql test suite
DAS - Failures in mysql test suite -- Key: TUSCANY-584 URL: http://issues.apache.org/jira/browse/TUSCANY-584 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Reporter: Brent Daniel There are several failures in the MySQL test suite. 1) Database tables are not being created correctly -- in a couple of cases it is using a generated key syntax that is not supported by mysql 2) One stored procedure is not being created -- the code to create it is commented out, though I don't think there is any reason for it to be anymore 3) The current mysql jdbc drivers do not support PreparedStatement.getParameterMetaData() 4) For some reason invalid sql like "update customer asdflakjsadf set name = 'bob' where id = 2" succeeds 5) Some case sensitivity issues -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-584) DAS - Failures in mysql test suite
[ http://issues.apache.org/jira/browse/TUSCANY-584?page=all ] Brent Daniel reassigned TUSCANY-584: Assignee: Brent Daniel > DAS - Failures in mysql test suite > -- > > Key: TUSCANY-584 > URL: http://issues.apache.org/jira/browse/TUSCANY-584 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > Attachments: tuscany584.txt > > > There are several failures in the MySQL test suite. > 1) Database tables are not being created correctly -- in a couple of cases it > is using a generated key syntax that is not supported by mysql > 2) One stored procedure is not being created -- the code to create it is > commented out, though I don't think there is any reason for it to be anymore > 3) The current mysql jdbc drivers do not support > PreparedStatement.getParameterMetaData() > 4) For some reason invalid sql like "update customer asdflakjsadf set name = > 'bob' where id = 2" succeeds > 5) Some case sensitivity issues -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-584) DAS - Failures in mysql test suite
[ http://issues.apache.org/jira/browse/TUSCANY-584?page=all ] Brent Daniel updated TUSCANY-584: - Attachment: tuscany584.txt Attaching a patch to resolve these issues > DAS - Failures in mysql test suite > -- > > Key: TUSCANY-584 > URL: http://issues.apache.org/jira/browse/TUSCANY-584 > Project: Tuscany > Issue Type: Bug > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > Attachments: tuscany584.txt > > > There are several failures in the MySQL test suite. > 1) Database tables are not being created correctly -- in a couple of cases it > is using a generated key syntax that is not supported by mysql > 2) One stored procedure is not being created -- the code to create it is > commented out, though I don't think there is any reason for it to be anymore > 3) The current mysql jdbc drivers do not support > PreparedStatement.getParameterMetaData() > 4) For some reason invalid sql like "update customer asdflakjsadf set name = > 'bob' where id = 2" succeeds > 5) Some case sensitivity issues -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-590) DAS: Additional ConfigHelper methods needed
DAS: Additional ConfigHelper methods needed --- Key: TUSCANY-590 URL: http://issues.apache.org/jira/browse/TUSCANY-590 Project: Tuscany Issue Type: Improvement Components: Java DAS RDB Reporter: Brent Daniel Assigned To: Brent Daniel Currently, only a small subset of Config information can be created programmaticly using the ConfigHelper. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-590) DAS: Additional ConfigHelper methods needed
[ http://issues.apache.org/jira/browse/TUSCANY-590?page=all ] Brent Daniel updated TUSCANY-590: - Attachment: Tuscany590.txt The attached patch adds several methods to ConfigHelper with associated unit tests. > DAS: Additional ConfigHelper methods needed > --- > > Key: TUSCANY-590 > URL: http://issues.apache.org/jira/browse/TUSCANY-590 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > Attachments: Tuscany590.txt > > > Currently, only a small subset of Config information can be created > programmaticly using the ConfigHelper. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-592) DAS: Need a way to create an empty graph without a database read
DAS: Need a way to create an empty graph without a database read Key: TUSCANY-592 URL: http://issues.apache.org/jira/browse/TUSCANY-592 Project: Tuscany Issue Type: Improvement Components: Java DAS RDB Reporter: Brent Daniel Assigned To: Brent Daniel There needs to be a way to create an empty DataGraph without accessing the database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-592) DAS: Need a way to create an empty graph without a database read
[ http://issues.apache.org/jira/browse/TUSCANY-592?page=all ] Brent Daniel updated TUSCANY-592: - Attachment: Tuscany592.txt This patch adds a simple utility to GraphMerger to create an empty graph given a Config instance that defines static types. We need to discuss further whether this is the right place for it (and, if it is, rename GraphMerger to GraphHelper.) But, this patch will at least make the function available. > DAS: Need a way to create an empty graph without a database read > > > Key: TUSCANY-592 > URL: http://issues.apache.org/jira/browse/TUSCANY-592 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Reporter: Brent Daniel > Assigned To: Brent Daniel > Attachments: Tuscany592.txt > > > There needs to be a way to create an empty DataGraph without accessing the > database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-608) DAS diagrams don't show up in IE
DAS diagrams don't show up in IE Key: TUSCANY-608 URL: http://issues.apache.org/jira/browse/TUSCANY-608 Project: Tuscany Issue Type: Bug Components: Website Reporter: Brent Daniel The images on 'http://incubator.apache.org/tuscany/das_index.html' don't show up in internet explorer. Firefox seems fine. The two image tags affected are: It looks like IE is interpreting the empty width and height attributes as meaning the image is 0x0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-571) Remove reference to EPackage for Type look up
[ http://issues.apache.org/jira/browse/TUSCANY-571?page=all ] Brent Daniel reassigned TUSCANY-571: Assignee: Brent Daniel > Remove reference to EPackage for Type look up > - > > Key: TUSCANY-571 > URL: http://issues.apache.org/jira/browse/TUSCANY-571 > Project: Tuscany > Issue Type: Improvement > Components: Java DAS RDB >Affects Versions: Java-Mx >Reporter: Kevin Williams > Assigned To: Brent Daniel > Fix For: Java-Mx > > > The current use of EPackage to get Types associated with a URI should be > replaced with an SDO-only alternative -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
