See http://www.nabble.com/New-pom-structure-tf1870006.html
I think Martijn tweaked it a bit after that, but he'd better explain
that himself :)
Btw, Frank made a nice search service for Wicket messages etc:
http://woogle.billen.dk . Might make it easier to find stuff like
this.
Eelco
On
Try it again. Probably you were too fast for the sync to ibiblio to happen.
The wicket-parent-1.2.1.pom file is now available on ibiblio.
http://repo1.maven.org/maven2/wicket/
From now on, the maven repository is sync'd frequently with our
repository so (final) releases will become
In your application's init method, call
getDebugSettings.setSerializeSessionAttributes(false);
Eelco
On 7/26/06, Vincent Jenks [EMAIL PROTECTED] wrote:
I just downloaded 1.2.1, how do I take advantage of this? I'm hoping
I can use 1.2.1 on Glassfish w/o having to custom-build it like I did
I'd guess you need to checkout wicket-parent
(http://svn.sourceforge.net/viewcvs.py/wicket/branches/WICKET_1_2/wicket-parent)
and do a mvn install in there first.
/Gwyn
On 26/07/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Also, I'm not able to build Wicket 1.2.1 w/ maven like I did w/ 1.2.
In
I just downloaded 1.2.1, how do I take advantage of this? I'm hoping
I can use 1.2.1 on Glassfish w/o having to custom-build it like I did
w/ 1.2.
Thanks!
On 7/10/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
just added this, it will be in 1.2.1
action type=update dev=Igor VaynbergAdded
Also, I'm not able to build Wicket 1.2.1 w/ maven like I did w/ 1.2.
In the top-level 'wicket' folder doing mvn install
-Dmaven.test.skip=true gives me this:
[INFO] Scanning for projects...
Downloading: http://maven.sateh.com/repository/wicket/wicket-parent/1.2.1/wicket
-parent-1.2.1.pom
OK, that definitely helped...but
Results :
Tests run: 410, Failures: 0, Errors: 1, Skipped: 0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There are
Beautiful, it all built and it works in the app.
Thanks Igor!
On 7/10/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
mvn install -Dmaven.test.skip=true
-Igor
On 7/10/06, Vincent Jenks [EMAIL PROTECTED] wrote:
OK, that definitely helped...but
Results :
Tests run: 410, Failures: 0,
Then you probably don't have done the steps to setup ant... ant
requires you to install the junit jar into the ant/lib folder iirc.
It's been a while since I've setup ant to work like this...
Martijn
On 7/7/06, V. Jenks [EMAIL PROTECTED] wrote:
I did steps 1-5...it immediately fails because
Again, I did this at home on my Gentoo box in a separate project...and
got the same result.
My log4j.properties:
logger.wicket.protocol.http=INFO
The exception stack:
wicket.WicketRuntimeException: Internal error cloning object. Make sure
all dependent objects implement Serializable. Class:
My problem w/ that is; the application is done and I can't go back
through and re-work it to get something working that already works on
another container. This application runs well on JBoss's EJB3
implemenation w/o that kind of tweaking. However, going forward,
JBoss probably isn't an option
Anyway, I don't really understand, why is the ejb object actually being
serialized. Do you store your service objects in session?
-Matej
Igor Vaynberg wrote:
well, the problem might be that it is serialized by wicket itself.
this is done because you have the logger set to debug to help
On Thursday, 06 July 2006 09:16 am, Vincent Jenks escreveu:
My problem w/ that is; the application is done and I can't go back
through and re-work it to get something working that already works on
another container. This application runs well on JBoss's EJB3
implemenation w/o that kind of
Well, this was the first app I've ever built w/ EJB technology of
*any* version...it's sort of a pilot app for future in-house
effortsso far it's worked out great.
So, correct me if I'm wrong but it's my understanding that if I do not
store the stub to the interface of the stateful bean in an
OK, I've created a small test-app in Netbeans where I'm using a Wicket
page and have overridden ISessionFactory in the app class to create a
session. I have a page where I call the stateful bean, create it and
store it in session if it's non-existent, and supply a link to clear
the bean from
that it just works is logical. It is just a test we try to serialize it sothat you get a warning if that is not possible because of a non serializeable object.On 7/6/06,
Vincent Jenks [EMAIL PROTECTED] wrote:
OK, I've created a small test-app in Netbeans where I'm using a Wicketpage and have
Excellent, I'll move forward then and see how it goes...thanks!
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
that it just works is logical. It is just a test we try to serialize it so
that you get a warning if that is not possible because of a non
serializeable object.
On 7/6/06,
For whatever reason, I'm unable to supress this exception in the
storefront application (where I really need it.) I've tried wrapping
a try/catch around the assignment and retrieval of the SFSB stub in
the custom Session class...I can't pull the bean data up w/o the
exception occuring, it would
That's where I put it - nothing changed so you're obviously right...it
won't make a difference anyways.
Hmm...this is bad...this puts me in a rough spot as I have no idea how
to use a spring like proxy and am not at all familiar w/
Springand in effect I'd have no idea how to do this in Wicket
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
log4j.logger.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.catalina.cluster=INFO
log4j.logger.wicket.version=INFO
It must be in the wrong place somehow, if glassfish doesn't pick it
up. You should try to figure out how Glassfish works with commons
logging. Typically there is logging configuration for the whole
application server, and then for specific web applications. Not all
containers behave the same
In fact log4j.logger.wicket=INFO should be enough.
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
Wicket uses commons-logging. I wonder whether glassfish doesn't have
it's own weird logger factory, just like jetty does.
-Matej
Eelco Hillenius wrote:
In fact log4j.logger.wicket=INFO should be enough.
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
log4j.debug=false
I have no idea...but I'm lost at this point. I have both
commons-logging and log4j in the glassfish/lib folder because it is a
requirement for using Hibernate as the persistence engine. I put the
log4j.properties in there w/ the suggested entries and restarted...the
error is the same - didn't
Did you try asking around on the glassfish list/ IRC channel (if they have one)?
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
I have no idea...but I'm lost at this point. I have both
commons-logging and log4j in the glassfish/lib folder because it is a
requirement for using
At 8:30 this morning...it's now 2:30pm here and I was the *last*
person to post to this forum at all...which is weird...it's normally
pretty busy.
http://forums.java.net/jive/thread.jspa?threadID=16673tstart=0
This is the first time I haven't gotten an answer to my problem on the
same
OK, checked it out and I made my changebut bare w/ me...I'm almost
completely unfamiliar w/ Ant and I figured that'd be the easiest way
to build it?
So, how do I build this sucker?
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
well, if it comes down to it just check out wicket, remove
I've heard of it but am not familiar...I'll look into it.
I was going to make a lib project in eclipse or netbeans and build it
that way but realized there's probably a pile of dependencies I don't
have...won't that be an issue even w/ maven?
All the lib folders only contain clover
On
On 06/07/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
so there are people out there not using log4j? :)
I'm quite taken with Simple Log, myself! [https://simple-log.dev.java.net/]
(It includes an CommonsLoggingAdapter for use with clogging.)
/Gwyn
Using Tomcat but need to do more? Need to
Why would you want to make logging easy? :) If SUN had just adopted
Log4J instead of IBM's kit like the whole world besides IBM asked them
to do, we wouldn't have been in this mess.
Eelco
On 7/6/06, Gwyn Evans [EMAIL PROTECTED] wrote:
On 06/07/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
so
Caused by: java.io.NotSerializableException:com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegateat java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)
looks like a bug in sun's impl of ejbs?-IgorOn 7/5/06, Vincent Jenks [EMAIL PROTECTED]
wrote:I'm testing an app I
I don't know, I would believe that if I weren't able to make a
Stateful bean and use it exactly how I did in Wicket, outside of this
project.
I setup a test project and their stateful/stateless beans work
flawlessly when tested against JSP/Servletsthe problem arises w/
Wicket + SFSB on
well, the problem might be that it is serialized by wicket itself.
this is done because you have the logger set to debug to help identify
things you put into session that might not be serializable. maybe the
container doesnt serialize the same way so when the container does it
its not a problem,
That's kind of what I was thinking...and afraid of myself - that
Glassfish isn't playing nicely w/ Wicket when attempting to serialize
- otherwise the error doesn't make much sense.
I'm building a little test-app to demonstrate right now.
If this is the case, what can be done to work around it,
the stuff in session is only serialized because you have the logger
set to debug, if you turn that off it should be fine.
-Igor
On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's kind of what I was thinking...and afraid of myself - that
Glassfish isn't playing nicely w/ Wicket when
I'm not entirely sure what you meant by having the logger set to
debug...but I'll assume that you meant I was missing this from
web.xml?...
init-param
param-nameconfiguration/param-name
param-valueDEPLOYMENT/param-value
well, serialization error happens here:
at wicket.protocol.http.HttpSessionStore.setAttribute(HttpSessionStore.java:62)
if you go there you will see:
// Do some extra profiling/ debugging. This can be a great help
// just for testing whether your webbapp will behave when using
// session
Alright, I stuck a log4j.properties into my src folder, rebuilt,
redeployed - still get the same exception...here's my properties file
(copied from wicket-examples):
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
i dont know, but if the stack trace is exactly the same then log4j
still thinks debug level is enabled on that package.
-Igor
On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Alright, I stuck a log4j.properties into my src folder, rebuilt,
redeployed - still get the same exception...here's
39 matches
Mail list logo
