It's all fine with me. I'm just trying to do some suggestions to make MMBase better. I don't have a problem with communityprc. You seem to think I'm trying to solve my own problem (wich I do not have). Sorry for that. That was not my intention, and maybe I made to much noise about communityprc already because nobody else seems to care.

Jaco


Michiel Meeuwissen wrote:
Jaco de Groot wrote:

Still my suggestion is to remove the files in mmbase-X.X.X-community.zip from mmbase-X.X.X.zip and possibly create a mmbase-X.X.X-examples.zip that contains the files from mmbase-X.X.X-community.zip to make the examples work.


That seems hackery. The community app should know that it has examples, and
should register it to something as suggested by Daniel. Perhaps it is not
even necessary. mmexamples/index.jsp could simply list through all its
subdirectories.

This is not yet implemented, tough it is clear that is should happen, at
some point.

Whether community-app shoudl be installed in the distro is another issue.
Perhaps not. It has not been changed, because it is an example in the distro
since a long time.

When there are nice alternative examples we could installe a few of those in
the distro.

Or perhaps even that is not necessary any more when apps2 is working.

As it is (in 1.7) installing a app like community by hand is not very hard,
but you don't want that a newby needs to do that, just to have something to
look at.

Uninstalling an application like community is also very easy btw. Just throw
away mmbase-community.jar and communityprc.xml and it's gone. If you don't
there should also break nothing. IIRC you are seeing stacktraces because you
have a message builder with another builder class.


If community gives errors because of that, that could be considered a bug.
You can probably easily fix it, by an extra try/catch in the communityprc
code, to catch the ClassCastException.

For the moment you can simply uninstall the community code, as you probably
shoudl have done all along, since you are obviously not using it.

Michiel






Reply via email to