[JBoss JIRA] Created: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
3:37 a.m.
Provide a way to filter out elements which will be generated by exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector object
in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:47 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4269:
--------------------------------------------
The only reason I can think of for doing it in ArtifactCollector is to actually have the
generation be complete but just generate only the files that pass the filter.
have you considered how the ant tasks/eclipse ui will be able to use this ?
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:10 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-4269:
----------------------------------------
For ant task we need to allow user to pass ArtifactCollector's subclass object to
exporter task.
For eclipse ui we need to hold selected elements in launch configuration file(convert to
string) and restore them to configured ArtifactCollector object.
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:21 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-4269:
----------------------------------------
But if consider hibernate ant tasks it is much more easier to realize filtering by second
variant(filter out pojos by name).
I can add something like
<artifactcollector merge="owerwrite|skip" filter="MyPojoName1,
MyPojoName2"
acceptenumerated="true|false"/>
Where if 'acceptenumerated=true' then accept only pojos from 'filter'
otherwise filter out pojos from 'filter'.
We can use the similar syntax to save such filter in launch configuration file.
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:26 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-4269:
----------------------------------------
I meant not exaclty second variant, but:
public class GenericExporter{
protected void exportPOJO(Map additionalContext, POJOClass element) {
if (!getArtifactCollector().accept(element)) return;
...
}
}
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4269:
--------------------------------------------
I dont think we should expose the artfiactcollector completely to users yet. Lets keep it
to the more highlevel operations so implemetations details is not relevant.
For the ant tasks I suggest:
What you call merge is not related to filtering, it is related to how the exporter behave
so I would put an
attribute on the exporters and possibly also on <hibernatetool> for a default that
says
overwrite="no|yes|merge|ask" and the default will be ask.
enablement of merge is a bit tricky since it applies only to .java (for now).
Should we throw an error if merge is enabled and we dont support it for that type of file
or
should we just fallback to overwriting ?
About filtering then I guess we are filtering the actual output (i.e. the filename and not
the element being used for the generation).
Thus using a simple <patternset> would match in the Ant world, would it not ?
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4269:
--------------------------------------------
hmm - maybe filtering is on the incoming element but it just depends on what the exporter
is actually looking at, i.e. table, entity, component, conifiguration etc.
maybe simply <filter match="org.model.(Customer|Order)"
exclude="true|false"/> is enough (match is a regular expresion) and then what
it matches on is decided by the exporter.
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:27 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-4269:
----------------------------------------
Configuration,entity,component uses the same element class POJOClass. And this make our
life easier.
Not sure that it is possible to filter out such element like Table.
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:39 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-4269:
----------------------------------------
By the way all subclasses of GenericExporter uses iterator of PojoClass eslements to make
their export with different templates.
Hbm2DDLExporter, HibernateConfigurationExporter, QueryExporter produces only 1 file as I
think. We do not need to make file content filtering we only need to make *files*
filtering as I think, so can forget about this exporters as I think.
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:43 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-4269:
----------------------------------------
If anybody want to create it's own exporter(which uses something else then pojo
iterator) he will could realize such filtering from string <filter
match="org.model.(Customer|Order)" exclude="true|false"/> like you
suggested.
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:57 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Dmitry Geraskov updated JBIDE-4269:
-----------------------------------
Attachment: patch.txt
Added to base interface set/getFilter methods. Filter is an interface with only 1 method
public void accept(Object o). Each exporter could use this filter field in internal logic
as it want-this gives much flexibility to developers. Also developers must aware about
null-filter. GenericExporter passes in the filter PojoClass's objects. Test shows how
it works.
From other hand in my realization filter should know about Exporter
objects ( like PojoClass)
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Attachments: patch.txt
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:06 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Dmitry Geraskov reassigned JBIDE-4269:
--------------------------------------
Assignee: Max Rydahl Andersen (was: Dmitry Geraskov)
Max, need your review
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.M1
Attachments: patch.txt
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:04 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4269:
---------------------------------------
Fix Version/s: 3.1.0.M3
(was: 3.1.0.M2)
no access to svn causes this to slip
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.M3
Attachments: patch.txt
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:36 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4269:
---------------------------------------
Fix Version/s: 3.1.0.M4
(was: 3.1.0.M3)
slip to next version.
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.M4
Attachments: patch.txt
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:35 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4269:
---------------------------------------
Priority: Blocker (was: Major)
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.1.0.M4
Attachments: patch.txt
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:10 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-4269:
---------------------------------
Fix Version/s: 3.1.0.CR1
(was: 3.1.0.M4)
Bulk move from M4 to CR1
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.1.0.CR1
Attachments: patch.txt
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:05 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://jira.jboss.org/jira/browse/JBIDE-4269?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4269:
---------------------------------------
Fix Version/s: 3.2.next
(was: 3.1.0.CR1)
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.2.next
Attachments: patch.txt
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
[
https://issues.jboss.org/browse/JBIDE-4269?page=com.atlassian.jira.plugin...
]
Dmitry Geraskov updated JBIDE-4269:
-----------------------------------
Fix Version/s: 3.3.x
(was: 3.2.x)
slip to next version.
Provide a way to filter out elements which will be generated by
exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://issues.jboss.org/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.3.x
Attachments: patch.txt
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify
subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector
object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector
class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations
should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in
GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5004
days inactive
5670
days old
jbosstools-issues@lists.jboss.org
17 comments
3 participants
participants (3)
-
Denis Golovin (JIRA) -
Dmitry Geraskov (JIRA)
-
Max Rydahl Andersen (JIRA)