Hi All,
I have documented the project. You can have a look here[1]
https://docs.google.com/document/d/1jWBTaSDnVMkY0vOqOnU2ZG7fK28QIyXPC23F-B19zJ0/edit.
All suggestions are welcome.
[1]
https://docs.google.com/document/d/1jWBTaSDnVMkY0vOqOnU2ZG7fK28QIyXPC23F-B19zJ0/edit
Thanks.
On Tue, Aug
Good work Nasmin!
Here is my bit of thoughts to make the document better.
AFAIK, This feature doesn't work on Tomcat 6 and below. So we should
mention the supported tomcat versions.
I think the topic Tomgery : Jaggery Runtime for Apache Tomcat is more
suitable than the current topic. WDYT?
Can
Thanks for the valuable suggestions.
On Sat, Aug 16, 2014 at 5:03 PM, Chamil Jeewantha cha...@wso2.com wrote:
Good work Nasmin!
Here is my bit of thoughts to make the document better.
AFAIK, This feature doesn't work on Tomcat 6 and below. So we should
mention the supported tomcat
Hi All,
We had a demonstration session of the project on 4th August at WSO2. The
jaggery and AS members reviewed the current implementation and suggested
the following ideas.
01) Change the logger for this tomcat extension as tomcat uses
org.apache.juli.logging.Log
02) Rather than using a
Hi Nasmin,
Can you please send a mail to architecture@ list about your progress,
current status, architectural changes etc.
Thanks !
On Wed, Jul 9, 2014 at 5:59 PM, Chamil Jeewantha cha...@wso2.com wrote:
Hi All,
I have check the source code with Nasmin and found,
the JaggeryAsyncServlet
Sure. I will send an update on the progress soon.
On Mon, Jul 21, 2014 at 12:46 PM, Sagara Gunathunga sag...@wso2.com wrote:
Hi Nasmin,
Can you please send a mail to architecture@ list about your progress,
current status, architectural changes etc.
Thanks !
On Wed, Jul 9, 2014 at 5:59
Hi All,
I have check the source code with Nasmin and found,
the JaggeryAsyncServlet is already registered before it does
programatically because JaggeryAsyncServlet class is automatically added to
all the Webapp Contexts because of the @WebServlet annotation.
@WebServlet(name =
After some reading I found the above null pointer comes when we adding the
context listener BEFORE_START_EVENT occurs. So I changed the event to
STARTING. Now without any error the jaggery context listener added to the
standard context.
But when access the sample tomgery application through URL I
According to our earlier conversation I am following the below progression
to accomplish the project. Sorry for the lengthy email.
*Task1. Check whether the app in the tomcat webapps is jaggery app or not
before it gets deployed/initialized*
I trigger the BEFORE_START_EVENT by configuring the
Hi,
How do we plan to add jaggery modules on above context. (ex: caramel, email
)?
Regards,
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Sat, Jun 21, 2014 at 8:01 AM, Mohamed Nasmin nasmin1...@gmail.com
wrote:
According to our earlier
Hi Nasmin,
Best way is to have a look at tomcat source and debug.
On Sat, Jun 21, 2014 at 11:01 AM, Mohamed Nasmin nasmin1...@gmail.com
wrote:
According to our earlier conversation I am following the below progression
to accomplish the project. Sorry for the lengthy email.
*Task1. Check
Hi,
Whats there at line 27 of JaggeryContextListener.java? Where can we find
the source for this?
Regards,
Dilshan
On Sat, Jun 21, 2014 at 1:31 PM, Mohamed Nasmin nasmin1...@gmail.com
wrote:
According to our earlier conversation I am following the below progression
to accomplish the
Hi,
@Ruchira
I will debug the jars that we use in the tomgery app deployment and update
with the results.
@Dilshan
I am using that JaggeryContextListener in a jar which is created by
Ruchira. You can find the source code of that jar here[1].
@Dakshika
With the integration with JSR-223, Jaggery
Hi Nasmin,
the Null Pointer Exception (NPE) comes from the line
registration.setAsyncSupported(true);
Which means registration object is null. The responsible line of
assigning this variable is the line 25.
ServletRegistration.Dynamic registration = servletContext.addServlet(
14 matches
Mail list logo
