No, I can run the workflow from Eclipse without problems.
thorque wrote:
Hmm, happens this if you run the workflow with Eclipse, too?
Then - it seems so - oAW needs both libraries...
--
View this message in context:
will document all in the wiki and announce this.
Thorsten
On 3/28/07, Thorsten Kamann [EMAIL PROTECTED] wrote:
For your information: the oaw repository is maintained by Fornax :)
On 3/28/07, Patrik Nordwall [EMAIL PROTECTED] wrote:
I have submitted a bug report for this:
https
I normally do like this.
No abstract method in the generated abstract base class.
Generated method stub in the generated-once implementation subclass.
// TODO Auto-generated method stub
throw new UnsupportedOperationException(«name» not implemented);
Since the implementation
I think the problem is that you are using the wrong javaee.jar. In the
Installation Guide it is described that you must manually install javaee.jar
in your local maven repository. You must download Java EE 5 SDK and then
install the javaee.jar that is in the Java EE 5 SDK distribution.
Yes, this
KennethP wrote:
I added the following dependency part to dependencies section of
sculptor-helloworld-parent pom.xml:
dependencies
dependency
groupIdorg.fornax.cartridges/groupId
artifactIdoaw-aaa-patch/artifactId
version1.0.0/version
scopecompile/scope
I can't reproduce the problem with maven 2.0.7.
What classpath do you get when you run mvn dependency:build-classpath on
helloworld-parent project?
--
View this message in context:
http://www.nabble.com/Error-when-mvn-installing-sculptor-helloword-parent-tf4330430s17564.html#a12376635
Sent
]
[INFO] Total time: 5 seconds
[INFO] Finished at: Mon Nov 05 10:46:45 IST 2007
[INFO] Final Memory: 2M/5M
[INFO]
help me on this issue.
By,
Sam.R
9902199334
Patrik Nordwall wrote:
We have
confidence into MDSD using fornax.
Maybe Sculptor is it, if I would know what it is.
I mean creating a project right from eclipse would be great.
Wolfgang
Patrik Nordwall wrote:
Can you specify what you are looking for. Fornax Platform consists of
tools and cartridges for MDSD. Look
I have written a mini-how-to in the Developer's Guide:
http://fornax-platform.org/cp/display/fornax/7.+Developer%27s+Guide+%28CSC%29#7.Developer%27sGuide%28CSC%29-Howtouseenumtypes
It is rather easy.
--
View this message in context:
http://www.nabble.com/Enums-tf4865123s17564.html#a13936095
Minor bug fix release. See
http://fornax-platform.org/cp/download/attachments/1128/release-notes-1.1.html
Release Notes .
If you are already using 1.1.0 you only need to update the sculptor version
to 1.1.1 in maven pom.xml files and thereafter run mvn eclipse:eclipse to
update the Eclipse
Yes, there is a limitation (simplification) that only one level of
inheritance is supported.
Not so much for the domain objects (hibernate), but more due to that it
complicates the CRUD GUI.
Add an improvement issue in the tracker and we will try to fix it.
However, from design perspective I
We, in the development team, have only tested with Tomcat and JBoss 4.0.5 and
4.2.2.
When deployed as war there are no EJBs and it should be no problems. We try
to stick to the spec. The only venor (jboss) specific part I can think of is
the stuff for login, but that should be rather easy to
Can there be some mismatch between the eclipse jars in fornax repository and
normal central repository (ibiblio)?
I can see that they have added the eclipse jar Nov 27 at:
http://repo1.maven.org/maven2/org/eclipse/equinox/app/
and that is not the same version as in fornax repo:
Note that we are using repo1.maven.org/maven2 before fornax.repository.
Do you think that is the reason for the error?
settings.xml:
http://www.fornax-platform.org/cp/display/fornax/1.+Installation+Guide+%28CSC%29#1.InstallationGuide%28CSC%29-Maven
/Patrik
thorque wrote:
Hello,
this is a
The order actually matters.
I removed my local repo and was able to reproduce the error.
Thereafter I removed it again and changed the order, fornax repo first.
Then I have build successful.
Probably you didn't remove the repository, and I don't blame you, since the
fornax repo is so slooow
We continue to deliver. This time it is a technical upgrade to be able to use
Eclipse 3.3 and openArchitectureWare 4.2.
The installation is simplified to make it even easier to get started with
Sculptor.
Read more about the release here: http://fornax-platform.org/cp/x/kgc
with the server owner the Fornax
Stuff is hosted.
I hope this helped a little bit
Thorsten
Patrik Nordwall schrieb:
The order actually matters.
I removed my local repo and was able to reproduce the error.
Thereafter I removed it again and changed the order, fornax repo first.
Then I have
Ok, thanks for the suggestion, we will fix that in next version.
/Patrik
thorque wrote:
I think the best way is to add this to the pom and recommend to add this
to the settings. The pom has the advantage that the checkout and build
works out-of-the-box without any configuration.
If you
We have started with the enum implementation and it would be interesting to
find out what you (anyone) think should be supported and how it should be
expressed.
I have been doing some prototyping of the DSL syntax. What do you think
about this?
Simple enum:
ValueObject Weather {
While playing around with the syntax I have now the following conclusions.
Ordered parameters are better, more compact, less typing. The quotes are not
necessary for simple integer attributes.
The examples look like this
Simple enum:
ValueObject Weather {
Date day;
Good that the repository is available.
I have been using maven 2.0.8 without problems.
I add the repositories in maven settings.xml as described in the
http://fornax-platform.org/cp/x/cgQ Installation Guide , but it is true that
it is sometimes better to define them in the pom. We will do that
The answer is here:
http://www.nabble.com/Sculptor-1.2%3A-Help%3A-Modeling-Hierarchy-Relationship-in-DSL-to14584877s17564.html
i.e. sculptor is not using hibernate cartridge.
/Patrik
jskillings wrote:
Hi,
I have question on the available stereotypes in Sculptor 1.2.
In reviewing the
John, did you understand how to do it?
In the Sculptor CRUD GUI we do it like Roland suggests and you can generate
that web archetype to see how the pom should look like. See
http://fornax-platform.org/cp/x/AwU Archetype Tutorial
/Patrik
rolandukor wrote:
Hi,
I suggest you separate
I think we haven't tested hierarchy relationships (references from-to same
DomainObject type) enough. I know about several undocumented
bugs/limitations. I think it is time that we do something about this. I will
try some examples and add a jira issue.
I agree that the naming of the foreign key
Yes, that looks like a bug in the singular/plural naming algorithm, probably
due to the 2 s.
Can you add a bug in jira: http://www.fornax-platform.org/tracker/browse/CSC
/Patrik
jskillings wrote:
Strange error. Looks like a bug.
Here is the error I am getting while generating the CRUD
We have got an interesting comment in
http://www.fornax-platform.org/tracker/browse/CSC-173 CSC-173 that it is
not a good idea to have the repository definition in the pom files.
Another opinion:
repository can define other urls in settings.xml (or change in pom.xml, it
is only generated once).
Correct me if I'm wrong.
/Patrik
Patrik Nordwall wrote:
We have got an interesting comment in
http://www.fornax-platform.org/tracker/browse/CSC-173 CSC-173 that it is
not a good idea to have
I totally agree with Andreas that this is a great idea and we will try to
help you as much as we can.
Here are some links to ideas of how to do it. I would guess that we need
some help from the oAW xText experts, who are very helpful. Don't hesitate
to ask at the oAW forum.
darabi wrote:
In version 1.3 the plan is to have a gui meta model
Did you also plan to have a completely separate gui metamodel? Do you have
any ideas as how it should look like?
In 1.3 (trunk) we have two metamodels: sculptormetamodel and
sculptorguimetamodel. These are located in
Yes, this is a trade off you often have to do when using some tools. It is no
problem to customize sculptor to support this.
You can define the visibility of non changeable properties in
sculptor-generator.properties.
See:
Like this:
Entity User {
String name
- @Address home cascade=all-delete-orphan
}
ValueObject Address {
String street
}
Documentation:
http://fornax-platform.org/cp/display/fornax/3.+Advanced+Tutorial+%28CSC%29#3.AdvancedTutorial%28CSC%29-AdditionalReferenceFeatures
jsmoni wrote:
I have done some testing and created a few issues in jira:
http://www.fornax-platform.org/tracker/browse/CSC-178
http://www.fornax-platform.org/tracker/browse/CSC-179
http://www.fornax-platform.org/tracker/browse/CSC-180
The foreign key naming is tricky (CSC-179). Please contribute with more
I have created a http://fornax-platform.org/cp/x/tgc Sandbox page where we
can put any ideas that would help in development of Sculptor. Do you need
permissions to edit in the wiki you can contact
http://fornax-platform.org/cp/display/fornax/How+to+participate Thorsten by
email.
I have
rmischak wrote:
The file footer.inc is regenerated after running mvn generate-sources on
helloworld-web, but it does not include my changes, if I'm using the
binary build 1.2.0.
Yes, I think this is due to a resource loading issue that we didn't detect
when testing 1.2.0. We have fixed
Good!
I have added some enum stuff lately. Maybe that is something you need to add
also. If you diff the OracleDDL.xpt or MysqlDDL.xpt you can see the changes.
/Patrik
--
View this message in context:
http://www.nabble.com/Starting-Support-for-Apache-Derby-tp14804464s17564p14811160.html
Sent
This looks like a bug. I think I can fix it later tonight.
/Patrik
--
View this message in context:
http://www.nabble.com/Starting-Support-for-Apache-Derby-tp14804464s17564p14882197.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
Jira: http://www.fornax-platform.org/tracker/browse/CSC-182
Fixed. Thank you for finding this.
The fault was that 'opposite' should have been used.
Oracle template looks like this now:
«DEFINE foreignKeyConstraint FOR Reference-»
ALTER TABLE «from.getDatabaseName()» ADD CONSTRAINT
I hope that it is (will be) possible to use a separate DSL (grammar/editor)
for the GUI, and be able to cross reference the model for the business tier.
Separation of concerns.
Here are two links to ideas of how to do it, but I havn't tried any of it.
Alright, I have changed to META-INF/MANIFEST.MF in the two pom.xml files.
/Patrik
--
View this message in context:
http://www.nabble.com/file-directory-name-problems-tp14894813s17564p14925887.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
Perfect, Thanks a lot René!
I have created a jira for this:
http://www.fornax-platform.org/tracker/browse/CSC-183
/Patrik
--
View this message in context:
http://www.nabble.com/Starting-Support-for-Apache-Derby-tp14804464s17564p14957771.html
Sent from the Fornax-Platform mailing list archive
Thanks for your suggestion, I think it is a good idea, but I have to analyse
how that will affect other things.
FYI, we have recently changed the naming conventions for foreign key
columns:
http://www.fornax-platform.org/tracker/browse/CSC-179
/Patrik
Andreas Voss wrote:
Hi all,
we
I have created a jira for this:
http://www.fornax-platform.org/tracker/browse/CSC-186
We will do it as soon as possible and make it available in 1.3.0-SNAPSHOT.
/Patrik
--
View this message in context:
This new feature is available for you in the latest 1.3.0-SNAPSHOT.
See doc:
http://fornax-platform.org/cp/display/fornax/3.+Advanced+Tutorial+%28CSC%29#3.AdvancedTutorial%28CSC%29-databaseNames
Let us know if you need anything else. Feedback and requests are critical
for us to be able to
Andreas Voss wrote:
The models I have use composite keys. As you describe in the advanced
tutorial, these are supported by Sculptor - but I do not really understand
the last sentence All persistent Entities and Value Objects will also
have a surrogate id attribute, which is the primary key
Mark H wrote:
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template = archetype-resources/pom.xml [line 271,column 34] :
${sculptor.version} is not a valid reference.
[INFO] * End of debug info from resources from
generated POM
I removed my local repository and then I have a similar problem.
Downloading:
http://www.fornax-platform.org/m2/repository/org/fornax/toolsupport/fornax-oaw-m2-plugin/2.0.0/fornax-oaw-m2-plugin-2.0.0.pom
3K downloaded
[INFO] snapshot org.fornax:fornax-parent:2-SNAPSHOT: checking for updates
from
Today it works fine again.
--
View this message in context:
http://www.nabble.com/Maven-Repository%3A-Missing-fornax-parent-2-SNAPSHOT.pom-tp15610849s17564p15668633.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
ok wrote:
The one question I have is, why does it have to be
sayHello = MoonService.sayHello;
instead of
sayHello = @MoonService.sayHello;
?
Yes, that makes sense. I have created an issue in the tracker for you:
In Sculptor we do this, but we always use project specific workflow first.
The workflow.oaw in the same project as the maven pom.xml normally just
use another workflow, sculptorworkflow.oaw. This sculptorworkflow.oaw is
included in a dependent jar.
workflow
cartridge
This is an answer to the
http://fornax-platform.org/cp/display/fornax/2.+Hello+World+Tutorial+%28CSC%29?focusedCommentId=2007#comment-2007
comment in the wiki.
I got the same error when trying to deploy in Tomcat. In Tomcat
logs/localhost.date.log I can see that the reason for the problem is
denis lutz wrote:
Hi guys,
i am starting to work with sculptor. Fist of all, greate job to Patrik
and many thanks.
I was wondering how many people criticized sculptor on the server side
:confused: not understandable for me Only the point that sculptor is
integrating MDSD, TDD and
One more thing...
denis lutz wrote:
DDD is saying: Entities are root of an aggregate and there are mutable.
Value Objects are part of their inner object tree , can be accessed only
through an entity and are immutable
Value Objects are not restricted to be used as part of inner object
We encourage a rich domain model, with behaviour. Otherwise it wouIdn't be
much of a DDD ;-).
You can add methods directly in the subclasses of the domain objects. These
are generated only once.
The reason for not including methods in the DSL and code generation is that
it is not much that can
A CRUD GUI is automatically generated, if you have services with crud
operations. You don't have to add anything GUI specific in the DSL.
I think this is described in CRUD GUI Tutorial:
http://www.fornax-platform.org/cp/display/fornax/5.+CRUD+GUI+Tutorial+%28CSC%29
/Patrik
parviz wrote:
Hi
Hi, interesting. I think the generator will find classes in generate-sources
target project. As you said, I tried it that way when I wrote the guide.
I think you will have some better log of the real cause. Probably before the
one that you have supplied here.
FactoryHelper.java:67 logs the
Second thought. compilation is done after generation. Therefore, when this
occurs there is no FooBarAccessObjectStrategy class. I think you have to
move that to another project and add a dependency to that artifact in your
pom.xm
--
View this message in context:
Good!
Of course we can make it public. Bug report created, and fixed.
http://www.fornax-platform.org/tracker/browse/CSC-202
/Patrik
--
View this message in context:
http://www.nabble.com/Problem-with-GenericAccessObjectStrategy-tp17127515s17564p17154656.html
Sent from the Fornax-Platform
In Sculptor we close the ClassPathXmlApplicationContext in tearDown and I
think that works fine. Have a look in your test classes if that is done.
You might need to cast the context:
((ConfigurableApplicationContext) context).close();
/Patrik
cameroon wrote:
Hi all fornax gurus,
I'm
You have to use oAW version 4.2.
termiX wrote:
i have OpenArchitectureWare SDK feature 4.3.0.20080508-1430PRD.
--
View this message in context:
http://www.nabble.com/sculptor-dsl-editor-v.1.3.0-and-opening-model.design-tp17329775s17564p17347276.html
Sent from the Fornax-Platform
I don't have any good reason for why we havn't supported it. Maybe we had
some problems with it when we implemented that part (we used older hibernate
then).
Anyway, thanks for your feedback. I created jira: CSC-203
Fixed in trunk.
/Patrik
Bjoern_G wrote:
I have just enabled fetch=join for
Good.
Let me explain anyway.
The warnings from the initial archetype cmd can be ignored (I will add a
note of that in the tutorial).
Before version 1.3.0 we used to declare the fornax maven repository in
settings.xml. Now we don't and instead it is defined in the pom.xml, which
is generated by
We are going to upgrade Sculptor to oAW 4.3. When will oAW 4.3 be available
in Fornax maven repository?
/Patrik
--
View this message in context:
http://www.nabble.com/oAW-4.3-in-maven-repository--tp17609889s17564p17609889.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
I think I have answered a similar question here:
http://www.nabble.com/Multiple-inheritance-levels-td14117902s17564.html
What do you (all) think? Is it important to support multiple inheritance
levels?
/Patrik
cameroon wrote:
Hi all,
I am trying to model multi level class inheritance
Hi Ivan,
Can you describe your application more so that I can understand in what kind
of situation you have problems with hiberante lazy loading.
Are you using the generated Sculptor CRUD GUI as client or are you using
your own client?
The way the hibernate session is managed in the CRUD GUI
Associations are modeled in Sculptor using References. A reference has a
source DomainObject ('from') and target DomainObject ('to'). Two references
can be connected using the 'opposite' to create a bidirectional association.
When two references are connected the opposite is always set on both
See my previous answer. If opposite == null then it is uni directional
association.
Darth wrote:
Is this a fair assumption -
if ref.opposite = null but this is part of references, that itself says
that its a uni directional assosiation. Since if it wasnt a uni
directional association,
Cardinality for the source end of a unidirectional association doesn't make
sense.
Darth wrote:
How do I figure out the cardinality of the source end, for a
unidirectional relation (opposite = null)
So I was doing something like this (still rough)
«IF opposite != null»
Take a look at 2.2.5.3.2.2. Unidirectional in
http://www.hibernate.org/hib_docs/annotations/reference/en/html/entity.html
You have two cases for unidirectional.
1. target has cardinality many. I think @OneToMany together with @JoinTable
should be used.
2. target has cardinality 1 (not many). I
Thanks for your positive feedback.
Documentation can be added to most elements in model.design using quoted
string above it, like this:
This class is responsible...
Entity Planet {
The name of the planet...
String name
}
JavaDoc based on this documentation is generated. For attributes it is
Add something like this to SpecialCases.xpt:
«EXTENSION extensions::myhelper»
«AROUND *::propertyGetter FOR Attribute»
«formatGetterJavaDoc()»
«getVisibilityLitteralGetter()»«getTypeName()» «getGetAccessor()»() {
return «name»;
};
«ENDAROUND»
«AROUND *::propertySetter FOR
amphoras wrote:
Hi,
I was trying to convert my existing Hibernate mappings into the DSL in
Sculptor, and I was having some problems with certain keywords and
features:
1. Is there a unique keyword for a property? I want to set
unique=true. The Hibernate documentation is here:
Summer, Holiday weather, and Sculptor 1.4.0 is here.
The most important features of this release:
- JSF dialect of CRUD GUI.
- Possibility to split model.design into several files.
- Upgrade to oAW 4.3.
- Support for Eclipse 3.4 Ganymede. Europa 3.3.2 is also supported.
Read more here:
It is exactly as Alberto said, it prints oaw 4.2, but it is actually using
4.3. As soon as fornax-oaw-m2-plugin 2.1 is available in the repository you
can start using it instead. We will post something when it is available.
/Patrik
Alberto de Arriba wrote:
Although it prints 4.2 in the log,
Hi, have you rebuilt sculptor-parent (mvn install)? Are you using the correct
version number in your target project? Trunkow 1.5.0-SNAPSHOT
--
View this message in context:
http://www.nabble.com/-sculptor--weird-errors-after-editing-DSL-tp18389174s17564p18410145.html
Sent from the
Read in Advanced Tutorial to understand the usage of id and natural key.
http://www.fornax-platform.org/cp/display/fornax/3.+Advanced+Tutorial+%28CSC%29#3.AdvancedTutorial%28CSC%29-Key
Note that id is a surrogate key (sequence number) used in the database. You
should never add id in
Feels like a bug, please add an issue in jira:
http://www.fornax-platform.org/tracker/browse/CSC
--
View this message in context:
http://www.nabble.com/possible-bug-in-the-generate.serviceContext%3Dfalse-%28spring-AOP-still-sets-advice-up-%29-tp18459391s17564p18472913.html
Sent from the
This is my experience of debugging sculptor. I normally don't need to debug
oAW source, but I have also noticed that the source jars (plugins) of oAW
4.3 are strange.
I normally use project dependencies from my target project to sculptor.
Explained here:
You are almost there, but you must place the sculptor-generator project
dependency before the jar file dependencies. This is done in project
properties Order and Export tab.
/Patrik
--
View this message in context:
One more thing. You must debug workflow.oaw in your target project, not
sculptorworkflow.oaw in sculptor-generator project.
Patrik Nordwall wrote:
You are almost there, but you must place the sculptor-generator project
dependency before the jar file dependencies. This is done in project
Hi Ryan,
The ServiceContext parameter is added by the Transformation.ext. Therefore
you don't see anything in the templates.
Since you are working on the flex support I don't think you need to involve
SpecialCases.xpt. You can do this directly in the templates, Service.xpt.
This is how I would
Sculptor 1.4.1-SNAPSHOT is available. It corrects some JSF related bugs and
uses new versions of fornax infrastructure.
Read the updated migration instructions here:
http://fornax-platform.org/cp/display/fornax/9.+What%27s+New+%28CSC%29#9.What%27sNew%28CSC%29-Migration
/Patrik
BTW, I like the
Good! You might also be interested in reading the Developer's Guide to get an
understanding of what happens internally.
http://fornax-platform.org/cp/x/dAQ
/Patrik
--
View this message in context:
http://www.nabble.com/sculptor-dsl-to-the-ecore-model-tp18587447s17564p18592559.html
Sent from the
Your second question
rsmith wrote:
Also, is there a way to not have a surrogate key for some tables, and use
a business key instead? I know this isn't the recommended approach, but I
have a couple exception cases where I'd like to do this.
Sculptor adds id to all persistent
I have fixed this, http://www.fornax-platform.org/tracker/browse/CSC-222
CSC-222 , and it will be part of 1.4.1 release. I have deployed a new
1.4.1-SNAPSHOT, which includes this fix.
The workaround for 1.3.1 is that you define the missing
serviceContextStoreAdvice spring bean yourself. You can
Sculptor doesn't support List collection type for many-to-many. The reason is
that we didn't find it very useful to use List for that type of association.
It should have been some kind of constraint violation that gives you an
error message.
Note that a many reference without opposite will also
Anyone working on it?
--
View this message in context:
http://www.nabble.com/Fornax-wiki-server-is-down-tp18815679s17564p18815679.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
-
This SF.Net email
rsmith wrote:
- The foreign key reference columns are named based on the referred-to
table (e.g. ADDRESS). Can I customize this to be the same column name as
the primary key of the referred-to table (ADDRESS_ID in my example).
I don't think it is named based on the referred-to table, it
I'm sorry for the inconvenience. Personally I don't have any access to the
server. I think it is only Karsten and Thorsten who has the possibility to
solve this.
Any ideas of what the problem is? Jira? Can we stop using Jira for a while?
I think the instability started before the hard disk
I think you should start implementing in the templates instead of using
SpecialCases. This flex support is such an big addition that it will soon
become impossible to add everything using oAW AOP.
I think your specific question is easiest solved by replacing
AbstractDomainObject.
In your
Hi Polly,
This is an area that I would very much like to help and improve Sculptor as
much as possible. It is not very easy to support any type of customization
without replacing some of the Sculptor jar files. I'm very interested in
your suggestions and experience of customization.
Let us talk
I think you do that yourself.
http://www.nabble.com/alerts/EmailAlerts.jtp
http://www.nabble.com/mailing_list/MailingListOptions.jtp?forum=17564
--
View this message in context:
http://www.nabble.com/remove-me-from-this-server-please-%21-tp18971269s17564p18975986.html
Sent from the
Multiple inheritance levels is now implemented for the business tier.
Committed in trunk.
--
View this message in context:
http://www.nabble.com/problem-with-multi-levels-class-inheritance%3A-Best-practices-tp17598981s17564p19134691.html
Sent from the Fornax-Platform mailing list archive at
Ability to extend a fully qualified class is now implemented in trunk.
--
View this message in context:
http://www.nabble.com/-Sculptor--Reference-class-in-jar-tp18119720s17564p19150466.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
Not out of the box, but I guess it would be rather easy to implement that
using oAW AOP (SpecialCases.xpt) as explained in Developer's Guide.
/Patrik
Jeff Wolfe-3 wrote:
This might be a really dumb question, but I can't seem to find the answer.
Is it possible to get Sculptor to generate
Start with building sculptor-parent (run mvn clean install).
Refresh.
Thereafter you should not have any errors.
If you change the grammar (.xtext) you will have to run generate.oaw in
sculptor.dsl project
/Patrik
Ryan Gardner wrote:
I open the org.fornax.sculptor.dsl project in eclipse
I agree, I don't see any problems. Please add it to jira.
/Patrik
amphoras wrote:
Hi,
I have some objects that I want to be generated as Hibernate components,
so it seems that BasicType is the perfect choice. However, I also need
these domain objects to use inheritance. The Sculptor
Sorry, I answered too quick without thinking of everything. The persistence
is problematic.
I don't think Hibernate have support for this.
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1152
/Patrik
Patrik Nordwall wrote:
I agree, I don't see any problems. Please add
rsmith wrote:
As far as the UUID attribute, I guess what I really want to do is get rid
of the natural key altogether and just use the surrogate key for this
particular table.
I tried overriding the modifyUuid extension to not generate the UUID
attribute at all via:
It's down!!
--
View this message in context:
http://www.nabble.com/Fornax-wiki-server-is-down-tp18815679s17564p19239737.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
-
This SF.Net email is
Yes, this is something we should support. I have added a request in jira:
http://www.fornax-platform.org/tracker/browse/CSC-250
Ryan Gardner wrote:
I see in the Library example that a Map is used as the return type in
a repository method, but does fornax support storing a map as part of
1 - 100 of 398 matches
Mail list logo
