[Resin-interest] How to use Hibernate JPA with Resin 3.1.2

2007-10-04 Thread LSK7

I could not figure out how to use Hibernate JPA with resin 3.1.2. The link
here says that the bug for the third party persistence providers has been
fixed in resin-3.1.2 but I am not able to see that happening.
http://bugs.caucho.com/view.php?id=1507
http://bugs.caucho.com/view.php?id=1507 
-- 
View this message in context: 
http://www.nabble.com/How-to-use-Hibernate-JPA-with-Resin-3.1.2-tf4566861.html#a13035799
Sent from the Resin mailing list archive at Nabble.com.



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] How to use Hibernate JPA with Resin 3.1.2

2007-10-04 Thread Sergey Plehov
I have the same question. It seems that bug#1507 is not fixed.


2007/10/4, LSK7 [EMAIL PROTECTED]:


 I could not figure out how to use Hibernate JPA with resin 3.1.2. The link
 here says that the bug for the third party persistence providers has been
 fixed in resin-3.1.2 but I am not able to see that happening.
 http://bugs.caucho.com/view.php?id=1507
 http://bugs.caucho.com/view.php?id=1507
 --
 View this message in context:
 http://www.nabble.com/How-to-use-Hibernate-JPA-with-Resin-3.1.2-tf4566861.html#a13035799
 Sent from the Resin mailing list archive at Nabble.com.



 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest




-- 
---
Sergey Plehov
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] How to use Hibernate JPA with Resin 3.1.2

2007-10-04 Thread Scott Ferguson

I've added it as http://bugs.caucho.com/view.php?id=2041

-- Scott

On Oct 4, 2007, at 3:13 AM, Sergey Plehov wrote:



I have the same question. It seems that bug#1507 is not fixed.


2007/10/4, LSK7 [EMAIL PROTECTED]:

I could not figure out how to use Hibernate JPA with resin 3.1.2.  
The link
here says that the bug for the third party persistence providers  
has been

fixed in resin-3.1.2 but I am not able to see that happening.
http://bugs.caucho.com/view.php?id=1507
http://bugs.caucho.com/view.php?id=1507
--
View this message in context: http://www.nabble.com/How-to-use- 
Hibernate-JPA-with-Resin-3.1.2-tf4566861.html#a13035799

Sent from the Resin mailing list archive at Nabble.com.



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest



--
---
Sergey Plehov
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Resin Comet

2007-10-04 Thread Scott Ferguson
I've updated the Comet API to make it more like the Servlet API and  
to avoid dependencies on Resin details.  Details are at

   http://caucho.com/resin-javadoc/com/caucho/servlet/comet/package- 
summary.html

The example has been updated at

   http://caucho.com/resin-3.1/examples/servlet-comet/

The main changes are
   1. the package (com.caucho.servlet.comet to match javax.servlet),
   2. CometController is now an interface
   3. CometServlet is now an interface
   4. GenericCometServlet replaces the older class
   5. Added CometFilter and CometFilterChain

You might also want to look at the new streaming capabilities of  
Hessian as an example protocol for use with comet: http://caucho.com/ 
resin-javadoc/com/caucho/hessian/io/Hessian2StreamingOutput.html

The Comet API now looks like:

public interface CometController {
   boolean wake();

   Object getAttribute(String name);
   void setAttribute(String name, Object value);

   void close();
}

public interface CometServlet extends Servlet {
   boolean service(ServletRequest requet, ServletResponse response,
CometController controller);

   boolean resume(ServletRequest request, ServletResponse response,
   CometController controller);
}

public interface CometFilter extends Filter {
   boolean doResume(ServletRequest request, ServletResponse response,
   CometFilterChain next);
}

public interface CometFilterChain extends FilterChain {
   boolean doResume(ServletRequest request, ServletResponse response);
}

-- Scott



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Resin Comet

2007-10-04 Thread Alan Wright
What exactly is Comet?  what problem does it solve? When would I use it?

Alan

Scott Ferguson wrote:
 I've updated the Comet API to make it more like the Servlet API and  
 to avoid dependencies on Resin details.  Details are at


   


-- 


Alan Wright
Athene Systems

tel 0845 230 9803


Athene Systems Limited
Registered Office:
Shieling House
Invincible Road
Farnborough
GU14 7QU

Registered in England and Wales No. 3156080



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Resin's JSTL vs the W3C's HTML Validation Engine

2007-10-04 Thread Scott Ferguson

On Oct 4, 2007, at 7:59 AM, Matt White wrote:

 Resin Gurus -

 Please forgive me if this is a frequently asked question, I have only
 recently re-subscribed this list and don't see this issue in the
 documentation.

 If I have a snippet of JSP code that looks like this:

 a href=c:url value=someFile.jspc:param name=w
 value=1/c:param name=h value=2//c:urlClick Me!/a

I've added a bug report as http://bugs.caucho.com/view.php?id=2042,  
but I'll need to check the spec.

You might need to use

   c:url value=... var=foo.../c:url
   c:out value=${foo} escape=true/.

I'm not sure why c:url doesn't have an escape attribute to match c:out.

-- Scott


 Resin's JSTL will produce a URL that looks like this:

 a href=someFile.jsp?w=1h=2Click Me!/a

 ...which, if you ask me, is a perfectly valid URL and is the response
 I'd expect. The W3C disagrees.


 According to the W3C's validator (and the HTML validator plugin for
 FireFox I'm using), the URL should be written like this:

 a href=someFile.jsp?w=1amp;h=2Click Me!/a

 Notice how the  has been escaped into amp;... one could argue that
 this is a silly change as amp; contains , but that just the way
 these things work... *grumble*


 Is there a way to make Resin's JSTL implementation spit out amp;
 instead of  on URLs?

 Thanks!

 - Matt


 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Resin Comet

2007-10-04 Thread Scott Ferguson

On Oct 4, 2007, at 8:20 AM, Alan Wright wrote:

 What exactly is Comet?  what problem does it solve? When would I  
 use it?

Comet is for streaming responses from the server, as a replacement  
for polling.  (Comet doesn't stand for anything, unfortunately.   
It's just a unique identifier.)  The server sends a new packet of  
data to the client when an event occurs.

The best example might be a Flash administration or monitoring  
application that updates the client dynamically as events arrive from  
the server.  The demo examples tend to be simpler, e.g. a chat  
application, which have the same basic properties as a real  
application, i.e. asynchronous updates, but might not be directly  
useful.

It's a somewhat specialized capability, but if the application needs  
async notification of the client, it's very useful for the app server  
to provide the infrastructure.

Resin's Comet is solving two problems

1) Async notification/communication of the servlet thread using the  
CometController.  This is the main issue, really.  The servlet thread/ 
request is single-threaded/synchronous, but Comet applications are  
intrinsically multithreaded/async.   Resin's implementation deals  
with most of the threading issues, which will let applications avoid  
threading issues later on.

2) Thread detachment and reattachment from the idle servlet request.   
While the Comet servlet is idle, waiting for the next event, Resin  
can detach the thread and use it for another request.  This is a nice  
side-effect and many comet implementations push #2, but really it's  
#1 that's the main issue.

-- Scott


 Alan

 Scott Ferguson wrote:
 I've updated the Comet API to make it more like the Servlet API and
 to avoid dependencies on Resin details.  Details are at





 -- 


 Alan Wright
 Athene Systems

 tel 0845 230 9803


 Athene Systems Limited
 Registered Office:
 Shieling House
 Invincible Road
 Farnborough
 GU14 7QU

 Registered in England and Wales No. 3156080



 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Resin's JSTL vs the W3C's HTML Validation Engine

2007-10-04 Thread Matt White
On 10/4/07, Scott Ferguson [EMAIL PROTECTED] wrote:

  a href=c:url value=someFile.jspc:param name=w
  value=1/c:param name=h value=2//c:urlClick Me!/a

 I've added a bug report as http://bugs.caucho.com/view.php?id=2042,
 but I'll need to check the spec.

Thanks Scott.

Glad to know I wasn't overlooking something obvious in the documentation.

- Matt


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest