JPA code completion does not work without source code ?

Hi,
  it seems to me, that code completion for JPA/Hibernate work fine only if I have source code of entities included in the project - NOK.

  I have all JPA entites wrapped in the jar file, which is included to the project as maven dependency. Entities are generated from enterprise architect and generated source code can't be edited by hand. The source codes are bundled as maven dependency too, hence I can see, how entities are annotated (in read only mode).
I have enabled JPA Facet with persistence.xml. Color schema works fine too. The HQL Console works fine (but code completion does not work too).

  After I added manually source codes of the entities to the project, code completion start to work fine.

  How to configure IDE to use entities in the external jar?

Thanks
  Petr

IDEA. 9.0.2 #IU-95.66

Screens without source code and with source code.
without-source-code.pngwith-source-code.png

5 comments
Comment actions Permalink

@jetbrains

We have a similar issues with Entities from jar's.

1. Classes from jar's listed in persistence.xml are shown in red. Ex:       <class>com.something.MyJarEntity</class>
2. Entities/MappedSupperclass are not shown in 'ER Diagram'. In our case some a MappedSupperclass are in a jar. The option 'Merge Inherited Attributes' is activated but ER Diagram does not show inherited attributes.

Perhaps these issues are solved too with IDEA-24847 ...? Or should I create a new Issue for these?

Thanks for feedback

0
Comment actions Permalink

Please check the latest 9.0.3 EAP first.

On 14.07.2010 17:06, Minas Manthos wrote:

@jetbrains

>

We have a similar issues with Entities from jar's.

>

1. Classes from jar's listed in persistence.xml are shown in red. Ex:<class>com.something.MyJarEntity</class> 2.
Entities/MappedSupperclass are not shown in 'ER Diagram'. In our case some a MappedSupperclass are in a jar. The option
'Merge Inherited Attributes' is activated but ER Diagram does not show inherited attributes.

>

Perhaps these issues are solved too with IDEA-24847 ...? Or should I create a new Issue for these?

>

Thanks for feedback

>

--- Original message URL: http://devnet.jetbrains.net/message/5267613#5267613


0
Comment actions Permalink

Ok, I was confused because Issue IDEA-24847 has the 'Fixed in build 96.355' and latest EAP is 95.390, so I don't tried myself (thinking that fix is not included latest EAP).
How ever... It works fine with latest EAP.

Thanks!

BTW: what are the 'mystic' of these 'fixed in build'? have nothing to do with EAP-build? ?:|

0
Comment actions Permalink

We make use of continuous integration powered by TeamCity.
"Fixed in build" value by default is set to a "next build".
Some of the builds are published as EAP builds and some aren't.

Gregory Shrago

On 14.07.2010 19:46, Minas Manthos wrote:

Ok, I was confused because Issue IDEA-24847 has the 'Fixed in build 96.355' and latest EAP is 95.390, so I don't tried myself
(thinking that fix is not included latest EAP). How ever... It works fine with latest EAP.

>

Thanks!

>

BTW: what are the 'mystic' of these 'fixed in build'? have nothing to do with EAP-build?

>

--- Original message URL: http://devnet.jetbrains.net/message/5267641#5267641


0

Please sign in to leave a comment.