<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>>Is there another way we might be mistakenly triggering pyjnius to mistakenly look at abstract classes?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Yes, through the Java JVM. As previously mentioned as the full jar. See classpath.py, classpath.py is loaded through __init__.py. It’s a complete JVM running alongside python, AFAIK, running X3DJSAIL.3.3.full.jar. That is why I talk about honoring classes. Do the @Override annotations last through the compilation cycle? Maybe we should consider places where abstract classes work? You’ve only got a bug left in the abstract classes, with most of your remaining errors (133) occurring in interfaces. Do we want to start addressing interfaces, or kill this bug left in the abstract classes (either your abstract classes or mine, I don’t really mind, it’s the same error).</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Pyjnius uses Cython and JNI to interface with Java. Some of the errors are JavaExceptions. This one is a Python problem, and if you look it up, it’s kind like something in the Python isn’t declared/defined.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>My version of the pipeline serializer clears up 130 of your problems in the interfaces. My abstract classes error almost seems trivial, with only 2 sources, that I could determine, potentially clearing up 10s of problems.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I feel my path is a better approach (at least quicker), and have felt that some time—If the programmer wants to do something else, they can use the non-pipeline serializer. You used to have a Java version which supported my Python version, but I think you’ve moved to native types over X3DJSAIL Object classes.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please help me fix this addChild method on X3DConcreteNode.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>