On 23/11/07 10:05 PM, Stephen Parry wrote:
Already tried using latest daily build and now does work with much arm
twisting (not sure yet if it needs the xml) . How do I access the RC
specifically please?
The announcement is at
https://lists.apache.org/thread/5djhjk8srt1dg0jr6x8pfpkom92h0486
-ernie
On 8 November 2023 04:26:05 GMT, Josh Juneau <juneau...@gmail.com> wrote:
Hi Stephen,
Sorry to hear that it did not work. I believe that the beans.xml
should go within the META-INF within a Java SE application.
Another thing to try...perhaps download NetBeans 20 RC3 and give
it a try to see if you have different behavior with your project.
Thanks
Josh Juneau
On Nov 7, 2023, at 11:13 AM, Stephen Parry
<sgpa...@mainscreen.com> wrote:
No joy, but then the app I am currently trying is an SE app. I am
not sure if beans. xml is recognised in an SE app.
On 6 November 2023 14:58:11 GMT, Josh Juneau
<juneau...@gmail.com> wrote:
Hi Stephen,
Please try to put the following into your beans.xml:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="https://jakarta.ee/xml/ns/jakartaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee
https://jakarta.ee/xml/ns/jakartaee/beans_4_0.xsd";
bean-discovery-mode="all">
</beans>
This tells all beans to be discovered by CDI. Hopefully it
will do the trick. I do not believe there are annotations
that can be used as an alternative at this point.
Thanks
Josh Juneau
On Mon, Nov 6, 2023 at 8:36 AM Stephen Parry
<sgpa...@mainscreen.com> wrote:
Thanks for the reply Josh.
What should I put in my beans.xml and are there
annotations I can try as an alternative?
On 6 November 2023 12:48:13 GMT, Josh Juneau
<juneau...@gmail.com> wrote:
Hi Stephen,
Sorry for the late reply. Do you have a beans.xml in
your project? You may need to have this
configuration file in your project in order for the
JPA entities to be recognized.
Josh Juneau
On Mon, Oct 30, 2023 at 6:28 PM Stephen G. Parry
<sgpa...@mainscreen.com> wrote:
After a lot of swearing and adding of the correct
libraries to
Tools->Libraries, I was able to persuade NB19 to
create JPA 3.1 Entity
classes, based on the jakarta.persistence package
space, from a database
in an SE project, although it identifies the
libraries as EclipseLink
(JPA 3.0), not JPA 3.1 in the dropdown for
persistence provider. I even
managed to make this work in a modular JavaFX
project. However, nothing
I have tried so far will persuade the controller
classes wizard to list
those classes - the list is empty - in any type
of project (modular,
non-modular, SE or EE). Can anyone help here
please? What do I need to
do to get this to recognize JPA 3.1 entities?
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscr...@netbeans.apache.org
For additional commands, e-mail:
users-h...@netbeans.apache.org
For further information about the NetBeans
mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
--
Sent from my Android device with K-9 Mail. Please excuse
my brevity.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
