-
### As a ...
- [ ] Application user/user of the configuration itself
- [X] API user (application developer)
- [ ] SPI user (container or runtime developer)
- [ ] Specification implementer
### I need…
-
```
Include a producer implementation as part of the odata4j distribution backed by
jdbc only - i.e. expose db entities (tables,views,sps) directly as odata
entities without the additional layer of …
-
```
I use Umlet for extracting data model diagrams from JPA entity classes. I think
it would be really handy if the import (Generate class elements from files...)
is a little bit JPA-aware and autom…
-
```
I use Umlet for extracting data model diagrams from JPA entity classes. I think
it would be really handy if the import (Generate class elements from files...)
is a little bit JPA-aware and autom…
-
```
Include a producer implementation as part of the odata4j distribution backed by
jdbc only - i.e. expose db entities (tables,views,sps) directly as odata
entities without the additional layer of …
-
```
Include a producer implementation as part of the odata4j distribution backed by
jdbc only - i.e. expose db entities (tables,views,sps) directly as odata
entities without the additional layer of …
-
```
Include a producer implementation as part of the odata4j distribution backed by
jdbc only - i.e. expose db entities (tables,views,sps) directly as odata
entities without the additional layer of …
-
```
Include a producer implementation as part of the odata4j distribution backed by
jdbc only - i.e. expose db entities (tables,views,sps) directly as odata
entities without the additional layer of …
-
```
Include a producer implementation as part of the odata4j distribution backed by
jdbc only - i.e. expose db entities (tables,views,sps) directly as odata
entities without the additional layer of …
-
```
Include a producer implementation as part of the odata4j distribution backed by
jdbc only - i.e. expose db entities (tables,views,sps) directly as odata
entities without the additional layer of …