Ext Direct Java based implementation

[pagullo]

It all looks good but before I start looking too deeply into DirectJNgine I would like to know a little about the status of the project. First question that come to mind is

1. Will DirectJNgine work with Ext JS 4.2 ? (only Ext JS 4.1 is mentioned in the docs)
2. Is the project being actively maintained ? I'm fully aware that no recent releases sometimes simply means that the code is stable and feature complete and therefore no reason to release new stuff. I hope that is the case for DirectJNgine.

Thank you.

I have not tested DJN against 4.2 because I have not used it. You can do that on your own by running the test app, which executes around 150 automated tests.

It should work, unless the Sencha guys have performed backward incompatible changes to their code base -something not unheard of.

Please, report back your findings!

Regarding maintenance, yes, it is actively maintained. The code base is very, very mature, that's why there are no new releases.

[extejnar]

I have not tested DJN against 4.2 because I have not used it. You can do that on your own by running the test app, which executes around 150 automated tests.

It should work, unless the Sencha guys have performed backward incompatible changes to their code base -something not unheard of.

Please, report back your findings!

Regarding maintenance, yes, it is actively maintained. The code base is very, very mature, that's why there are no new releases.

Ok, that was a good - and quick - answer. I'll kick off the tests and report back here.

[seade]

I am trying to use DirectJNgine with Sencha Architect (SA). SA provides a Direct Response toolbox item that expects the API to be declared in a slightly different format to what DirectJNgine currently provides (I describe this a little at http://www.sencha.com/forum/showthre...=1#post1000566).

I see that DirectJNgine provides api.js, api-debug.js and api-min.js. This has me wondering how difficult it might be for there to be further alternatives that support SA. Might you consider this?

Scott

[pagullo]

DirectJNgine 2.3 beta 1 is out, with support for pluggable bean adapters: Spring beans, CDI/JEE beans, etc. can be integrated into DirectJNgine by defining a new bean adapter.

See http://softdevbuilttolast.wordpress....cly-available/ for more info.

Regards!

[frengo19]

Hi All!
I'm using Extjs4 and Java with the library DJN.
Everything goes fine except i'm not able to shutdown the server (apache tomcat) without killing it!

• DJN 2.2
• Extjs 4.2.1
• Java 1.5
• Tomcat 6.024
• Windows 7

Anybody has the same problem?

Thank you very much!

bye

[pagullo]

Hi!

Since I created DJN, I've never found this behavior.
What makes you think this might be related to DirectJNgine?

[frengo19]

Hi!

Since I created DJN, I've never found this behavior.
What makes you think this might be related to DirectJNgine?

Hi yourself!
If I start and shutdown my app without doing any DJN ajax call, tomcat stops correctly.. So I imagined that the problem may be caused by Direct..
I've also run the profiler but no threads locked!

[seade]

I am trying to use DirectJNgine with Sencha Architect (SA). SA provides a Direct Response toolbox item that expects the API to be declared in a slightly different format to what DirectJNgine currently provides (I describe this a little at http://www.sencha.com/forum/showthre...=1#post1000566).

I see that DirectJNgine provides api.js, api-debug.js and api-min.js. This has me wondering how difficult it might be for there to be further alternatives that support SA. Might you consider this?

Scott

Hi Pedro. Would you mind taking a quick look into my question above. Thanks, Scott.

[pagullo]

Scott,

I do not have plans to add support for Sencha Architect, unless a) I happen to participate in a project that needs it and b) the customer is willing to allot me the time required to implement and test it. Just don't have free time for doing this right now.

[frengo19]

Hi yourself!
If I start and shutdown my app without doing any DJN ajax call, tomcat stops correctly.. So I imagined that the problem may be caused by Direct..
I've also run the profiler but no threads locked!

When I stop the server that's what I see in console:

11-nov-2013 11.46.42 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
GRAVE: A web application created a ThreadLocal with key of type [null] (value [[email protected]]) and a value of type [java.util.ArrayList] (value [[]]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.
11-nov-2013 11.46.42 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
GRAVE: A web application created a ThreadLocal with key of type [null] (value [[email protected]]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@75733a]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.
11-nov-2013 11.46.42 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
GRAVE: A web application created a ThreadLocal with key of type [null] (value [[email protected]]) and a value of type [java.util.WeakHashMap] (value [{class com.su[email protected]1bbdc80, class com.[email protected]896098, class com.sun.xml.[email protected]124be4f, class javax.xml.bind.annotat[email protected]14a4067, class com.sun.xml.w[email protected]1ca623f, class [email protected], class com.sun.xm[email protected]16b4f5a, class java[email protected]269f76}]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.
log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository.