[
https://issues.apache.org/jira/browse/TORQUE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-151.
---
Resolution: Fixed
Fix Version/s: 4.0
> Support Bit as
: Thomas Fischer
Assignee: Thomas Fischer
Priority: Minor
Currently if a BIT column is declared as (composite) PK a compilation error
occurs.
Bit values should be supported as primary keys.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add
I tried to fix the problem in the generator but did not check whether the
fix solves the problem on linux. Could you svn update the generator, mvn
install it and then try to build the templates again ?
Thanks,
Thomas
> >>> ...
> >>> - Can you run the tests inside an IDE (e.g. eclips
> Hi Thomas,
> ...
> The startElement method is called and reads the following values:
> systemId: http://db.apache.org/torque/4.0/templates/database.xsd
> ressource: ../../xsd/database-4-0.xsd
>
> I found out that adding the references to the configuration fails and
> creates an ConfigurationExcep
Hi Patrick,
> > ...
> > - Can you run the tests inside an IDE (e.g. eclipse) and set a
breakpoint
> > in org.apache.torque.generator.configuration.source.EntityReferences.
> > resolveEntity() (in the generator jar) and see whether it gets called
and
> > if yes why it fails ?
>
> I got the project
[
https://issues.apache.org/jira/browse/TORQUE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917889#action_12917889
]
Thomas Fischer commented on TORQUE-148:
---
In this special case no runtime Excep
[
https://issues.apache.org/jira/browse/TORQUE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917888#action_12917888
]
Thomas Fischer commented on TORQUE-147:
---
I should have been more clear before.
Hi Patrick,
> after looking into the test reports
which is always a good idea to do :-)
> I found the following reason:
>
> testProcessSchemaXml + [ Detail ] 0.864
>Error parsing controller Configuration : Could not read entity
> reference http://db.apache.org/torque/4.0/templates/database
> I would like to try to set up a test environment for running Torque4
> with HSQLDB.
Just to make sure you know this: Currently no HSQLDB SQL templates exist in
Torque 4. SQL generation will fail for HSQLDB in the current state of
Torque 4.
Thomas
--
> > Hello,
> >
> > I would like to try to set up a test environment for running
> > Torque4 with HSQLDB. I follow the steps for running the test
> > project. I work with current sources from Torque4 branch.
> maybe it is caused due to Thomas latest changes. He made Torque
> generified intern
[
https://issues.apache.org/jira/browse/TORQUE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917217#action_12917217
]
Thomas Fischer commented on TORQUE-150:
---
Done in 4.0 branch except for mana
I should have said that of course only the torque 4 runtime was changed.
The torque3 runtime is left as is.
Thomas
-
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h
I am quite sure I did not break everything
but there might be some pieces which are not tested by the test project. In
any case, if you notice somethin which does not work please open a jira
issue.
Thomas
Dr. Thomas Fi
[
https://issues.apache.org/jira/browse/TORQUE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917215#action_12917215
]
Thomas Fischer commented on TORQUE-147:
---
No, there will still be BaseXXX and XXX
[
https://issues.apache.org/jira/browse/TORQUE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917213#action_12917213
]
Thomas Fischer commented on TORQUE-150:
---
BasePeer.doSelect() returns a lis
use generics in the Runtime
---
Key: TORQUE-150
URL: https://issues.apache.org/jira/browse/TORQUE-150
Project: Torque
Issue Type: Improvement
Components: Runtime
Reporter: Thomas Fischer
Java
Thomas Vandahl wrote
>
> On 30.09.10 06:40, Thomas Fischer wrote:
> > From the lack of answers to the qeustion whether or not to release
> > Torque-4.0-alpha1 soon, I conclude that the idea does not have strong
> > support and that we want to have a go at the runtime fi
[
https://issues.apache.org/jira/browse/TORQUE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-149.
---
Assignee: Thomas Fischer
Fix Version/s: 3.3.1
Resolution: Fixed
>
: Torque
Issue Type: Bug
Reporter: Thomas Fischer
If the option torque.om.silentDbFetch is false (which is NOT the default
value), then Torque generates from the schema
the following code in BaseAuthor:
public void addBook(Book l) throws
[
https://issues.apache.org/jira/browse/TORQUE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-148.
---
Fix Version/s: 4.0
Resolution: Fixed
> remove throws clause in setter for referen
: Improvement
Reporter: Thomas Fischer
Assignee: Thomas Fischer
Priority: Minor
for the schema
Torque generates (complexObjectModel=true) in BaseBook:
public void setAuthor(Author v) throws TorqueException
{
if (v
> On 01.10.10 21:31, Thomas Fischer wrote:
> > I intend to make this behaviour configurable using the option
> > torque.om.complexObjectModel.localFieldSetterException
> > If the default value is set to to TorqaueException, the behaviour of
3.3 is
> > retained.
> &g
Reporter: Thomas Fischer
Assignee: Thomas Fischer
Currently it is an error if database objects do not inherit from BaseObject.
This makes embedding of Torque objects in other frameworks very difficult,
because it does not allow to choose an own parent to inherit from.
The minimum
Thomas Vandahl wrote:
> On 30.09.10 05:24, Thomas Fischer wrote:
> > I would be in favour of dropping the need for "extends BaseObject".
>
> I don't think this is meant to be necessary. The objects only must
> implement Persistent. The schema supports the "bas
This question is best explained by an example
If I have
then Torque generates (complexObjectModel=true) in BaseBook:
public void setAuthor(Author v) throws TorqueException
{
if (v == null)
{
setAuthorId(0);
}
els
[
https://issues.apache.org/jira/browse/TORQUE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-146.
---
Fix Version/s: 4.0
Resolution: Fixed
> Options should be made available in
[
https://issues.apache.org/jira/browse/TORQUE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-145.
---
Assignee: Thomas Fischer
Fix Version/s: 4.0
Resolution: Fixed
> rem
[
https://issues.apache.org/jira/browse/TORQUE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer closed TORQUE-143.
-
Site deployed
> Repository URLs of Runtime and Generator modules aren't
Just a heads up that I redeployed the Torque 4 site.
Thomas
-
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org
> >> I would try to implement a SourceProvider in the first stage after
there
> >> was some discussion, enough interest and a basic concept how to
> >> implement it.
>
> It would be (in my opinion) a nice possibility if Torque would use
> the same annotations as JPA or JAXB. So there can be one cla
> ...
> About the problem with inheritance I guess there needs to be some
> discussion. There would be one way which possibly most people around
> here do not like, that would be bytecode enhancement after compilation.
> Since this would be some kind of religious war I'm open to other
> possibilite
>>> 3) keep the larger possible user base: in this case devs should ask the
>>> community and then see if the requests for asked dbs are satisfiable
>>> with the available manpower
>>>
>> Good idea. I will do that.
> Do you know how many people are subscribed to the user list?
No idea, sorry. But
Fischer
Assignee: Thomas Fischer
The options elements of the various elements are not queryable through the
database map. It would be useful if they were.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online
remove inputValidator attribute on column element
-
Key: TORQUE-145
URL: https://issues.apache.org/jira/browse/TORQUE-145
Project: Torque
Issue Type: Sub-task
Reporter: Thomas
[
https://issues.apache.org/jira/browse/TORQUE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-144.
---
Fix Version/s: 4.0
Resolution: Fixed
> remove alias attribute on table elem
[
https://issues.apache.org/jira/browse/TORQUE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer updated TORQUE-144:
--
Description: Nobody knows what the alias attribute is used for or has a use
case. Its usage in
remove alias attribute on table element
---
Key: TORQUE-144
URL: https://issues.apache.org/jira/browse/TORQUE-144
Project: Torque
Issue Type: Sub-task
Reporter: Thomas Fischer
[
https://issues.apache.org/jira/browse/TORQUE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-143.
---
Assignee: Thomas Fischer
Resolution: Fixed
Patch applied. Thanks!
> Repository U
Dr. Thomas Fischer
Software-Entwicklung
Tel. +49 (0) 7531 36598-22
Fax +49 (0) 7531 36598-11
E-Mail fisc...@seitenbau.com
SEITENBAU GmbH
Seilerstraße 7
D-78467 Konstanz
http://www.seitenbau.com
Amtsgericht Freiburg HRB
> 3) keep the larger possible user base: in this case devs should ask the
> community and then see if the requests for asked dbs are satisfiable
> with the available manpower
Good idea. I will do that.
Thomas
-
To unsub
> Scott Eade wrote
> On 28/09/10 4:03 AM, Thomas Vandahl wrote:
> > On 26.09.10 19:49, Thomas Fischer wrote:
> >> Does anybody think that we should support more databases and do not
thest
> >> the integration?
> > Testing on DB2/AS400 would be kind of a hurdl
Hi Christoph,
> I'll like the idea of using POJOs with annotations and I would be glat
> to see it in Torque as well. This would make things a lot easier since
> we use interfaces and concrete implementations. These implementations
> are wrapped by adapter-classes so annotations would be a great s
>From the lack of answers to the qeustion whether or not to release
Torque-4.0-alpha1 soon, I conclude that the idea does not have strong
support and that we want to have a go at the runtime first.
Of course, changing the runtime will also change the generated classes and
thus the templates.
How
> >> Greg suggested to use the map
> >> classes for the metadata which sounds quite reasonable.
> >
> > I'd rather not do it. We have all the information for processing data
in a
> > typesafe manner, so why do we want to have a class in the middle which
> > stores information as a Object with no ty
> > table.abstract
> > I'm of the opinion that the abstract attribute works but Thomas V is of
> > another opinion. But, thinking about it, we can make it work once the
Peer
> > class is not static any more. So the question is do we think it's
useful
> > and should be kept or should we drop it (Thi
> ...
>
> > Or did I musunderstand what you were saying ?
>
> Probably. What happens in our case is that the call always goes to
> TablePeer.getOMClass(). If that does not exist,
> BaseTablePeer.getOMClass() gets called. If this didn't work, we could
> never use TablePeer.doSelect() because the me
> > We could release the generator, templates, maven 2 plugin and ant tasks
as
> > 4.0-alpha1, and simultaneously do a 3.3.1 release of the runtime and
> > village.
> > Of course, this would need a bit of testing and tweaking before
releasing,
> > but do you think it is a good idea in general? I'd
Ok, so let me summarize (please object if I misinterpreted somebody)
table.alias:
Noboby thinks that the alias attribute is useful and will be missed. So
I'll create a jira issue for it and we drop it.
table.abstract
I'm of the opinion that the abstract attribute works but Thomas V is of
another
> > As far as I know, static methods are bound at compile time and cannot
be
> > overridden (i.e the BasePeer code will always access this
implementation
> > and thus always fail).
>
> AFAICT, no runtime code ever calls getOMClass(). The generated peer
> classes call TablePeer.getOMClass() and thus
I am wondering whether we should do a Torque-4.0-alpha1 release in the near
future.
In my opinion, the generator is quite stable ,the templates are also ok,
and the build tool integration seems to be working.
Nothing much has happened to the runtime, so it is not near a 4.0 release.
So this releas
Currently there is an attribute inputValidator on the column element. It is
only used to set the inputValidator property on the column map, which is
not further used.
Ok to remove this attribute ?
Thomas
-
To unsubscribe,
What is the attribute "abstract" used for? I'm curious because it does not
seem to work currently. In Torque 3.3, the following snippet is in the base
peer template:
public static Class getOMClass()
throws TorqueException
{
public static Class getOMClass()
throws Torque
[
https://issues.apache.org/jira/browse/TORQUE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914870#action_12914870
]
Thomas Fischer commented on TORQUE-45:
--
The solution does not work for foreign key
[
https://issues.apache.org/jira/browse/TORQUE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-45.
--
Fix Version/s: 4.0
Resolution: Fixed
Dropped foreign key before dropping tables
Status time again...
Today I deployed a new version for the Torque 4 site (the Torque 3 site was
not updated). The tutorials for both ant and maven2 are now online and
should work overall, though minor errors could still be present. Error
reports are welcome :-) (please empty your browser cache b
...
> Out of curiosity, does this mean all schema.xml files will have
> to be modified with the xsd headers? Not a bad thing, just wondering
> if you had figured out how to support both ddt and xsd. FWIW, I briefly
> experimented with writing some code that would read the first few lines
> of th
[
https://issues.apache.org/jira/browse/TORQUE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer reopened TORQUE-128:
---
There is no problem on tables with composite primary key where none of the
columns are
I added Greg's suggestion for a schema xsd to the torque 4.0 templates, and
support in the generator to check xml sources against a schema.
A few things were changed as compared to Greg's initial proposal
- I changed the namespace from http://db.apache.org/torque4.0 to
http://db.apache.org/torque/
[
https://issues.apache.org/jira/browse/TORQUE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-131.
---
Assignee: Thomas Fischer
Fix Version/s: 4.0
Resolution: Fixed
> reom
[
https://issues.apache.org/jira/browse/TORQUE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-130.
---
Assignee: Thomas Fischer
Fix Version/s: 4.0
Resolution: Fixed
> remove
[
https://issues.apache.org/jira/browse/TORQUE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-91.
--
Fix Version/s: 4.0
Resolution: Fixed
Resolved in the transition from database.dtd to
[
https://issues.apache.org/jira/browse/TORQUE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-48.
--
Fix Version/s: 4.0
Resolution: Fixed
Greg monroe has translated the current dtd to a
[
https://issues.apache.org/jira/browse/TORQUE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-128.
---
Fix Version/s: 4.0
Resolution: Fixed
Change made with Greg's transition t
[
https://issues.apache.org/jira/browse/TORQUE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-127.
---
Assignee: Thomas Fischer
Fix Version/s: 4.0
Resolution: Fixed
> remove &q
Time for another Torque 4 status.
- I am currently (but slowly) working on the tutorial, which is integrated
into the torque-site project (the torque-tutorial project will go away). A
first shot is available in svn but I have to re-read and check for errors.
I intend to add an ant part once ant i
> > -The prepared statement opened in the Schema.schema() method should be
> > closed after usage. Preferably using a finally clause.
>
> See lines 154-164 of Schema.java
Sorry, I missed that. My fault :-(. The code is correct.
...
> Could you do me a favor: If you have a working Torque runtime
I have looked through the patch. I am not very deep in the logic of
village, so I am not sure that the code works.
But still, I have come across some stuff that is not yet perfect:
-The prepared statement opened in the Schema.schema() method should be
closed after usage. Preferably using a finally
> > That caching in schema is the one that I remembered a month ago. It's a
> > pity that the connection is not provided in the constructor
QueryDataSet
> > (ResultSet resultSet). Thed most difficult task is to create an
adequate
> > key for caching, as one can connections to multiple databases, an
> I'm currently trying to fix that long outstanding problem of excessive
> meta-data access in Village. I find that I could need some net.wisdom.
> So if someone could try to reproduce/confirm my thoughts I'd be grateful.
>
> - The problem is most probably in Column.populate()
Seems a fair guess,
[
https://issues.apache.org/jira/browse/TORQUE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-123.
---
Resolution: Fixed
Already committed:-)
> Statement is left open when Exception is thr
[
https://issues.apache.org/jira/browse/TORQUE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897014#action_12897014
]
Thomas Fischer commented on TORQUE-123:
---
I'm going to use anot
[
https://issues.apache.org/jira/browse/TORQUE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer reopened TORQUE-123:
---
Assignee: Thomas Fischer (was: Thomas Vandahl)
The applied patch does not work for java
> I am trying to create a table like BookAuthorMap which has two columns :-
> BookId and AuthorId. These are my primary key in another table. I want to
> insert my values in these column rather auto increment.
> ...
You need to set the attribute idMethod to "none" in the table element. See
http:/
> FYI - When I was talking about the "Generator" component for Torque,
> I was thinking that the Generator component was the holder for the
> Torque specific "build" tool "interface" code.
>
> I was assuming that the "Output" generator framework would eventually
> be in a separate sub project since
The announced refactoring in the generator is done. Sorry for the big
commits.
This does not mean that the naming discussion for the Outlet interface is
done. If a good name suggestion comes up, the interface name can be changed
again.
Thomas
---
> Don't have a strong opinion... just a take it or leave it thought
> that since gf is sort of a Template engine that something like
> Transformer might be slightly more appropriate.
Hm a ??? is not just a template wrapper. It could also be a java class or a
xslt stylesheet or just anything which
In the tiscussion about accepting the current generator codebase, it was
suggested that the project name remains "generator". However, in the
current codebase, the project name is "torque-gf" (gf for generation
framework). Also, "Generator" is the name of an interface for a java class
producing th
Derby support in Torque4 is up and running. There are two test profiles in
the torque-test project, derby (using the network client) and derbyEmbedded
(using the embedded client). Network server was made default because the
embedded profile will not run in maven because we have the fork mode
perTe
> When torque generates set methods for foreign keys, the methods thorws a
> TorqueException.
>
> Why is this? There is nothing in the methods that throws a
TorqueException
> and removing the throws clause does not generate a compiler error.
Maybe it is generated for overriding. Someone who wants
If you want to come up with a suggestion, please go ahead
Thomas
> I think we should take advantage of the fact we are writing an hypeterxt.
> We should have an elevator pitch and use links in his keywords to
> forward the reader to techinical explanation.
> Even better to forward the reader to
+1, very nice.
Do you want to replace the current text on the 3.3 and 4.0 website with
it ? The 4.0 site deployment description at
http://db.apache.org/torque/releases/torque-4.0/developer-info/site-edit-deploy.html
should be up do date.
Thomas
> OK, this isn't an elevator pitch anymore...
> I think Torque would benefit from us defining such a statement to
> help frame what Torque
> 4.0 is working towards.
>
> That said, my personal elevator speech for Torque is:
>
> Torque is designed to simplify using SQL data in Java
> applications across all the common SQL
> database serv
I redeployed the torque 3 site(with a link to torque4) and the torque4
site.
The changes should be live in a couple of hours.
If I broke anything please tell me.
Thomas
-
To unsubscribe, e-mail: torque-dev-unsubscr...@db.a
[
https://issues.apache.org/jira/browse/TORQUE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-138.
---
Resolution: Fixed
Fix Version/s: 4.0
> rename the "torque 4" menu ite
[
https://issues.apache.org/jira/browse/TORQUE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer resolved TORQUE-140.
---
Resolution: Fixed
Fix Version/s: 4.0
> change section order and headlines on in
Affects Versions: 4.0
Reporter: Thomas Fischer
Assignee: Thomas Fischer
Priority: Minor
The section "releases" should appear before "elements of Torque". The section
"elements of Torque" should be renamed to "elements
> >> - something needs to be done about the ant tasks that were in 3.3. but
> >>
> > are
> >
> >> not yet present in 4.0.
> >>
> there are others than jdbc2xml ?
Yes, there is datadtd, datadump, and jdbc (though I do not know what the
latter does). Datasql is in the scope of the generator/template
> > The thing which we should decide next is what do we do with the
generator
> > features which do not have to do anything with code generation (like
> > jdbc2xml).
> As I already mentioned, my experience says this is a quite important
> module, for me it has been fundamental.
> I can sure try to
ion
Affects Versions: 4.0
Reporter: Thomas Fischer
--
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: torque-dev-unsub
> >> - The external-schema support is missing, I hope I get at it in the
near
> >> future. However, I'm curious to know what it is good for. Does
anybody
> >> have a use case ?
> >
> > I haven't used this yet, so this is just my understanding what it was
> > meant for. Let's say you have a number
Issue Type: Sub-task
Components: Documentation
Affects Versions: 4.0
Reporter: Thomas Fischer
Assignee: Thomas Fischer
Priority: Minor
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment
> In any case I would move the releseases section in the Overview page
> up, right under the What is Torque section.
I'm not sure what you mean by this. But promped by this comment, I have
looked again at the menu structure and what is confusing about it is that
the "module documentation" menu ite
[
https://issues.apache.org/jira/browse/TORQUE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842583#action_12842583
]
Thomas Fischer commented on TORQUE-137:
---
village should be mentioned as rem
> > What I also would like is some kind of plan on what Torque4 actually
will
> > contain. It would be nice to know what the "heavy development"
mentioned
> on
> > the first page is and what is left of it.
>
> There were occasional discussions about this during the last three years,
> and most cert
> I have studied the generator getting started page for torque 4 and the
> concept reference. But I have a situation that I think is not mentioned
> there, since that documentation is about building things from scratch.
>
> What I want to do is use some of the standard components, more specific
th
Reporter: Thomas Fischer
Assignee: Thomas Fischer
The url
http://db.apache.org/torque/releases/torque-4.0/documentation/modules.html is
referenced from the menu but does not exist as html page
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a
[
https://issues.apache.org/jira/browse/TORQUE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fischer updated TORQUE-135:
--
Component/s: Documentation
> Torque 4 site chan
Reporter: Thomas Fischer
Assignee: Thomas Fischer
The description wehre to find which documentation needs some overhaul. E.g. it
is not clear that the documentation how to crteate the om classes is found in
the templates module.
--
This message is automatically generated
Torque 4 site changes
-
Key: TORQUE-135
URL: https://issues.apache.org/jira/browse/TORQUE-135
Project: Torque
Issue Type: Bug
Affects Versions: 4.0
Reporter: Thomas Fischer
This is an umbrella issue for
> What I also would like is some kind of plan on what Torque4 actually will
> contain. It would be nice to know what the "heavy development" mentioned
on
> the first page is and what is left of it.
There were occasional discussions about this during the last three years,
and most certainly I do no
1 - 100 of 1143 matches
Mail list logo
