Make Transaction class name configurable or namespace it
See original GitHub issueI started using Continuum for our project and had a lot of problems just starting.
Turns out that we had model called Transaction
and it clashed with Continuum’s own Transaction
model.
It would be nice to be able to have configuration option to control name of this class (and database table).
Issue Analytics
- State:
- Created 8 years ago
- Reactions:3
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How can I prevent the error "the class name or namespace ...
The namespace statement indicates "I am under this directory" (well, namespace) The use statement indicates: load this class (= a file)
Read more >ServiceBehaviorAttribute Class (System.ServiceModel)
The Name and Namespace properties control the name and namespace for the WSDL expression of the service element. The ReleaseServiceInstanceOnTransactionComplete ...
Read more >How to choose a good namespace name? (Linguistically)
The name chosen for a namespace should indicate the functionality made available by types in the namespace. For example, the System.Net.
Read more >16. Transaction Management - Spring
It can work with JTA transactions or local transactions using JDBC, JPA, Hibernate or JDO by simply adjusting the configuration files. You can...
Read more >Package Options | Defining and Using Classes
Package Mapping · From the Management Portal home page, go to the Namespaces page (System Administration > Configuration > System Configuration > Namespaces)....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is working for me so far (does not use a user class), slightly simplified:
Name is the only thing I want to change, and that’s only because
Transaction
is something that already existed in my app. I think it’s a good API design to allow users to easily change names that are not namespaced.