On Fri, 14 Dec 2012 21:43:17 -0200, bhorvat
wrote:
So what would be the best way to prevent a page to be accessed without
some context?
Object onActivate(EventContext context) {
if (context.getCount() == 0) {
return ...; // some page or URL to redirect to.
>
> I have tried to return
> false in onActiavate() method but no luck.
Not sure what you'd expect to happen here if you return false. Redirecting
to another page is a good answer, even if it's just back to the front page.
Don't forget that your empty onActivate handler is always called.
I ofte
So what would be the best way to prevent a page to be accessed without some
context?
I have a onActivate(Long id) method but I want to prevent users from simply
accessing the page by typing the name of the page. I have tried to return
false in onActiavate() method but no luck.
Is the only choice
Hello Thilo,
>From Selenium point of vue, this issue will be fix in next release
release of Pluto
https://issues.apache.org/jira/browse/PLUTO-620
Under Liferay, we have to use the specific method addHeader from
ResourceResponseImpl provided by the container.
So for "Content-Disposition" and other
That's exactly what I was facing. Thank you for your time :)
On Fri, Dec 14, 2012 at 5:46 PM, Lance Java wrote:
> Basically, the prepare() method is used to fetch the rows between
> startIndex
> and endIndex in a single batch and cache them. This cache might be a list
> with indexes ranging from
Basically, the prepare() method is used to fetch the rows between startIndex
and endIndex in a single batch and cache them. This cache might be a list
with indexes ranging from 0 to (endIndex - startIndex)
getRowValue(int index) is then used to retrieve a single entry from the
batch. This might re
JDBC supports paging which is is available in both hibernate and JPA.
Tapestry provides GridDataSource implementations for both Hibernate and JPA
that support paging.
http://tapestry.apache.org/tapestry5/apidocs/src-html/org/apache/tapestry5/hibernate/HibernateGridDataSource.html
http://tapestry.a
While it is true that you can put Tapestry library in the shared classloader (I
do it in the development environment)
and you can share the registry, you still can't call from one webapp into
another,
as the services themselves will still be loaded by different classloaders and
cannot be shared.
The thing is that my list isn't loaded once. It's loaded on every prepare
as I retrieve it from the database. And the available rows count changes on
every call as more items are available in the database. I solved this be
modulating the provided index, in the getRowValue(int) method, by the
availa
EJB3 is great. Don't hesitate to use it.
On Dec 14, 2012, at 8:12 AM, Martin Nagl wrote:
> Putting tapestry jars in shared folder to have them loaded by common class
> loader seems not quite right to me. Its a hack :) My high level feeling is:
>
> 1. Tapestry can provide IOC and JPA support in
You could extract your shared services into a separate war and expose them as
web-services.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Sharing-the-Registry-instance-between-web-applications-deployed-in-the-same-container-tp5718686p5718721.html
Sent from the Tapestry
Putting tapestry jars in shared folder to have them loaded by common class
loader seems not quite right to me. Its a hack :) My high level feeling is:
1. Tapestry can provide IOC and JPA support in scope of 1 web application.
2. If I need IOC and JPA (and EJB) support in scope of multiple web
app
On Fri, 14 Dec 2012 04:13:33 -0200, karthi
wrote:
Hi,
Hi!
You also need to copy files in src/main/resources to your
${target.classes.dir}.
Using ant how to compile both .tml & .java files?
.tml files are not compiled. Your problem here is that you didn't copy
于 2012/12/14 15:58, antalk 写道:
The onAction event will trigger a page-reload, as the currentpage parameter
is passed from the Grid to the Pager:
@Component(parameters =
{ "source=dataSource", "rowsPerPage=rowsPerPage",
"currentPage=currentPage", "zone=zone" })
private GridPager pager
Firstly, I would urge you not to use ant. It's easy to end up with spaghetti
code that does not conform to any standard. Even though I hate maven, it's
1000 times better than ant. I suggest you build with gradle.
If you *must* use ant. Then I suggest that you at least conform to the maven
standard
> You cannot use approach #2. Two separate web apps cannot call each other
directly.
> This is like having two processes on separate machines in separate JVMs.
This is not entirely true. As Josh said there is a classloader which is
common to all webapps running in a container. Take a look at the
Take a look at the CollectionGridDataSource source code for inspiration:
http://tapestry.apache.org/tapestry5/apidocs/src-html/org/apache/tapestry5/internal/grid/CollectionGridDataSource.html
If you pass a collection to the Grid, tapestry will coerce it to a
CollectionGridDataSource
--
View thi
17 matches
Mail list logo
