Re: WELCOME to users@wicket.apache.org

[Matthew Goodson]

Yeah I'm not feeling too hopeful
I have a tabbed panel which loads the tabs via ajax. When the page is loaded
from the browsers cache i.e. the user hits the back button, the ajax request
to load the tab is sent but wicket thinks that tab is already loaded
(getSelectedTab()) so ignores the request.

Here's the request that's sent. Wicket adds the random parameter. I'm not
sure if I removed the random param (somehow) if that would breaks things.

http://localhost?wicket:interface=:27::IActivePageBehaviorListener:21:2&wicket:ignoreIfNotActive=true&tab=privacysettings&random=0.8811610792763531

Any ideas?


On Wed, Apr 27, 2011 at 7:22 PM, Martin Grigorov wrote:

> Hi,
>
> I'm not sure whether this is possible at all.
> Why do you need to do this ?
>
> On Wed, Apr 27, 2011 at 8:12 AM, Matthew Goodson
>  wrote:
> > Hi guys,
> > I'm trying to find out if an ajax request has come from page that was
> loaded
> > from the browsers cache. Does anyone have any ideas of how I could
> achieve
> > this?
> > Thanks
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

RE: What's the intent of Enclosure.warnAboutFormComponentInsideEnclosure()?

[Russell Morrisey]

Oh, I see that there is a duplicate issue linked on JIRA which shows one use 
case: https://issues.apache.org/jira/browse/WICKET-2541

Sorry!



RUSSELL E. MORRISEY
Programmer Analyst Professional
Mission Solutions Engineering, LLC

| russell.morri...@missionse.com | www.missionse.com
304 West Route 38, Moorestown, NJ 08057-3212

From: Russell Morrisey
Sent: Wednesday, April 27, 2011 5:37 PM
To: users@wicket.apache.org
Subject: What's the intent of Enclosure.warnAboutFormComponentInsideEnclosure()?

All,

Since I upgraded our project to wicket 1.4.17, I am seeing this warning:

http-2467-1 > WARN  [2011-04-27 17:22:00,574] 
Enclosure.warnAboutFormComponentInsideEnclosure():196 - Found a form component 
TextField/contentPanel:rightPane:dataForm:tabbedPanel:panel:modules:lazyGrid:content:datagrid:form:bodyContainer:body:row:1:item:added:textfield1
 inside an enclosure. Form components do not work well inside wicket:enclosure 
tags, use EnclosureContainer instead

I did some searching and I found the relevant JIRA issue 
(https://issues.apache.org/jira/browse/WICKET-2541), and also saw talk on the 
mailing list about how to squelch this message from the log. I'm not clear, 
though what the intent of the warning is. Could you please articulate a 
scenario where an FC in an enclosure would cause undesirable behavior? I would 
like to know what to look out for.

Thanks,


RUSSELL E. MORRISEY
Programmer Analyst Professional
Mission Solutions Engineering, LLC

| russell.morri...@missionse.com | www.missionse.com
304 West Route 38, Moorestown, NJ 08057-3212



This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind MSE to any 
order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.

What's the intent of Enclosure.warnAboutFormComponentInsideEnclosure()?

[Russell Morrisey]

All,

Since I upgraded our project to wicket 1.4.17, I am seeing this warning:

http-2467-1 > WARN  [2011-04-27 17:22:00,574] 
Enclosure.warnAboutFormComponentInsideEnclosure():196 - Found a form component 
TextField/contentPanel:rightPane:dataForm:tabbedPanel:panel:modules:lazyGrid:content:datagrid:form:bodyContainer:body:row:1:item:added:textfield1
 inside an enclosure. Form components do not work well inside wicket:enclosure 
tags, use EnclosureContainer instead

I did some searching and I found the relevant JIRA issue 
(https://issues.apache.org/jira/browse/WICKET-2541), and also saw talk on the 
mailing list about how to squelch this message from the log. I'm not clear, 
though what the intent of the warning is. Could you please articulate a 
scenario where an FC in an enclosure would cause undesirable behavior? I would 
like to know what to look out for.

Thanks,


RUSSELL E. MORRISEY
Programmer Analyst Professional
Mission Solutions Engineering, LLC

| russell.morri...@missionse.com | www.missionse.com
304 West Route 38, Moorestown, NJ 08057-3212



This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind MSE to any 
order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.

Re: Wicket 1.5-RC3 with hibernate-annotation

[Lucky Spiff]

That's it, I forced the usage of slf4j 1.6.1 and the propblem was solved.
Thank you!

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-RC3-with-hibernate-tp3477380p3478670.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

WicketStuff HTML validator 1.5-rc3 released

[Martijn Dashorst]

If you were wondering if you needed to miss this awesome validator
with Wicket 1.5, there's a release for that.

WicketStuff HTML Validator 1.5-rc3 has been released!

Thanks to Emond 'Refactor' Papegaaij we now have a Wicket 1.5 (rc3)
compatible HTML validator. This validator works unfortunately still
only for HTML < 5 (so no HTML 5 constructs) and is still GPL licensed
due to the Tuckey library used.

Find more about Wicket Stuff HTML Validator at
https://github.com/dashorst/wicket-stuff-markup-validator

Martijn

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket 1.5-RC3 with hibernate-annotation

[jcgarciam]

I think you can try to exclude the slfj dependency that wicket ships on,
since its being already contributed by Hibernate or just update you the


org.slf4j
 slf4j-log4j12
* 1.6.1*


To the version that match the one provided hibernate.

On Wed, Apr 27, 2011 at 3:53 AM, Lucky Spiff [via Apache Wicket] <
ml-node+3477380-979833950-65...@n4.nabble.com> wrote:

> I folks,
>
> I tried to upgrade an application from wicket 1.4.17 to wicket 1.5-RC3 and
> after resolving some API changes it crashed at runtime because of a version
> conflicht with slf4j that seems to come from hibernate-annotations:
>
> java.lang.NoSuchMethodError:
> org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
>
> at org.slf4j.impl.Log4jLoggerAdapter.info(Log4jLoggerAdapter.java:318)
>
> at
> org.hibernate.annotations.common.Version.(Version.java:37)
> ...
>
> It seems that hibernate-annotations is compiled against slfj4 1.5.8 and has
> a version conflict. I use hibernate 3.6.2-Final.
>
> Is there a simple way around this without moving to something like OSGi?
>
> Thank you in advance for any hints!
>
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-RC3-with-hibernate-annotation-tp3477380p3477380.html
>  To start a new topic under Apache Wicket, email
> ml-node+1842946-398011874-65...@n4.nabble.com
> To unsubscribe from Apache Wicket, click 
> here.
>
>



-- 

JC


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-RC3-with-hibernate-tp3477380p3477963.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Customized AjaxPagingNavigator to highlight selected page number

[sap2000]

The current page selection is noticed by disabled link of the selected page
number.
In our project we need to highlight (bold font and colour) selected page by
means of css.
How this can be achived ?

Thank you.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Customized-AjaxPagingNavigator-to-highlight-selected-page-number-tp3477625p3477625.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Can't get Javascript filtering to work

[Martin Grigorov]

Static resources are more suitable for the cases when you want to
avoid page locking.
E.g. when you need to deliver dynamic response and there is a chance
that the processing will be slower or there will be more clients for
the same resource. Using a normal component for this will suffer that
only one request can use one page instance (pagemap in 1.4) at a time.

On Wed, Apr 27, 2011 at 11:54 AM, Andrea Del Bene  wrote:
> Hi Alec,
>
> are you sure you are testing your code in DEPLOYMENT mode and not in
> DEVELOPMENT mode?
>
> To answer your question about benefits of using shared resources,  I can say
> that they make sense when you need to access a resource (like a picture)
> with
> an absolute path instead of a relative one (which typically is
> "./resource/package.of.class/pictureName.png" ).
>
>> Hello,
>>
>> I would like to get my Javascript files filtered and gzipped. I added
>> the following code in my Application#init():
>> resourceSettings.setJavascriptCompressor(new
>> DefaultJavascriptCompressor());
>>
>> However, when I add a resource using the following code, I can still
>> see comments and white spaces in the Javascript files loaded by the
>> web pages:
>> final JavascriptResourceReference resourceRef = new
>> JavascriptResourceReference(scope, "/common.js");
>>
>> component.add(JavascriptPackageResource.getHeaderContribution(resourceRef));
>>
>> What am I doing wrong?
>>
>> Also, I am struggling to understand the benefits of using shared
>> resources, e.g. when does it make sense to create a shared resource
>> for a Javascript file?
>>
>> Thanks,
>>
>> Alec
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Can't get Javascript filtering to work

[Andrea Del Bene]

Hi Alec,

are you sure you are testing your code in DEPLOYMENT mode and not in 
DEVELOPMENT mode?


To answer your question about benefits of using shared resources,  I can 
say that they make sense when you need to access a resource (like a 
picture) with
an absolute path instead of a relative one (which typically is 
"./resource/package.of.class/pictureName.png" ).



Hello,

I would like to get my Javascript files filtered and gzipped. I added
the following code in my Application#init():
resourceSettings.setJavascriptCompressor(new DefaultJavascriptCompressor());

However, when I add a resource using the following code, I can still
see comments and white spaces in the Javascript files loaded by the
web pages:
final JavascriptResourceReference resourceRef = new
JavascriptResourceReference(scope, "/common.js");
component.add(JavascriptPackageResource.getHeaderContribution(resourceRef));

What am I doing wrong?

Also, I am struggling to understand the benefits of using shared
resources, e.g. when does it make sense to create a shared resource
for a Javascript file?

Thanks,

Alec

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [osgi] package org.apache.wicket.request exported either from core and request packages

[Martin Grigorov]

On Wed, Apr 27, 2011 at 11:19 AM, Daniele Dellafiore
 wrote:
> On Wed, Apr 27, 2011 at 8:57 AM, Martin Grigorov wrote:
>
>
>> I'm not against improving the current state. I'm saying that it want
>> last long without your help.
>> I said several times that the community can create the uber-jar
>> project in wicketstuff but so far no one wanted to do it.
>> I can do it for you but I wont test it in a real OSGi container. I'm
>> just not interested in this.
>> But we can apply your patches if they are reasonable.
>>
>
> Let's try. As I told, the first move is to rename into .core.util and
> .core.request the packages in -core bundle. This is reasonable? If it is
> not, well, I'll go for a issue for 1.6 and move totally on the uber-jar
> solution. If it is reasonable, we can proceed.
>
You said that broke some tests in your local build. See what are the problems.
Create a ticket and attach patches. It will be easier to review this way.

>
>> About testing - I don't see how unit tests will help to keep it
>> working in the future. Any ideas/patches on this matter are welcome!
>>
>
> Eh, this  can totally be done with pax-runner, as integration tests, but
> I've not enough experience with this so far.
>
>
>>
>> My concerns are that we had similar issue with Portlets support. When
>> we ran the vote whether to remove the support for Wicket 1.5 few
>> people (~ 5) asked to move the related code in wicketstuff so the
>> community can support it. Half an year later no one touched it so far.
>>
>
> This is totally reasonable. Let's see which way we can take here.
>
> Regards.
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Eike Kettner]

Hi Daniele,

sorry for answering this late, anyways, inline reply.


On [Fri, 22.04.2011 16:09], Daniele Dellafiore wrote:
> Hi, sorry I read your reply only today...
> I got basically to the same results yesterday, but I've some problem which I
> summarized in the last message in this thread on felix mailing list:
> 
> http://old.nabble.com/A-better-life%3A-quick-webapp-deploy-to31334158.html
> 
> I'll go into details point by point.
> 
> On Fri, Apr 8, 2011 at 3:29 PM, Eike Kettner  wrote:
> 
> > Hi Daniele,
> >
> > I might have not understood your concern well enough... But here is what I
> > do: I deploy a really small war file (without any deps of course) into the
> > osgi container (I use felix...). There is another bundle from pax,
> > called pax-web-extender, that "listens" for war files coming into the
> > container and will then register them on the embedded jetty instance.
> >
> > I use the following pax bundles:
> > * org.ops4j.pax.web.pax-web-extender-war
> > * org.ops4j.pax.web.pax-web-jetty-bundle
> > * org.ops4j.pax.web.pax-web-jsp   (might be superfluous)
> >
> 
> yeah I've everything installed. I do not remember what osgi features
> installed this but there is:
> 
> [  54] [Active ] [] [   ] [   60] OPS4J Pax Web -
> Runtime (1.0.1)
> [  55] [Active ] [] [   ] [   60] OPS4J Pax Web - API
> (1.0.1)
> [  56] [Active ] [] [   ] [   60] OPS4J Pax Web - Jetty
> (1.0.1)
> [  57] [Active ] [] [   ] [   60] OPS4J Pax Web -
> Service SPI (1.0.1)
> [  59] [Active ] [] [   ] [   60] OPS4J Pax Web -
> Extender - Whiteboard (1.0.1)
> [  60] [Active ] [] [   ] [   60] OPS4J Pax Web -
> FileInstall Deployer (1.0.1)
> [  61] [Active ] [] [   ] [   60] OPS4J Pax Url - war:,
> war-i: (1.2.5)
> [  62] [Active ] [] [   ] [   60] OPS4J Pax Web -
> Extender - WAR (1.0.1)
> [  63] [Active ] [] [   ] [   60] OPS4J Pax Web - Jsp
> Support (1.0.1)
> 
> on Karaf 2.2.0
> 
> 
> >
> > Then I use the felix-bundle plugin to create a MANIFEST.MF for my war
> > file. It looks like that:
> >
> >
> >  
> >org.apache.felix
> >maven-bundle-plugin
> >
> >  
> >bundle-manifest
> >process-classes
> >
> >  manifest
> >
> >  
> >
> >
> >  
> >jar
> >war
> >bundle
> >  
> >  
> ><_include>-osgi.bnd
> >  
> >
> >  
> >  
> >org.apache.maven.plugins
> >maven-war-plugin
> >
> >  
> >
> >  ${project.build.outputDirectory}/META-INF/MANIFEST.MF
> >
> >  
> >
> >  
> >
> >
> >
> 
> it's almost the same as mine, also the war-plugin config is identical.
> I do not have
> 
><_include>-osgi.bnd
> 
> but I have this instructions
> 
>   <_wab>src/main/webapp
> /myApp


I didn't know about tha <_wab> configuration, This will maybe then add the
web bundle class path to the headers, so it needn't be specified
explicitely.
 
> There are some more instructions in the "osgi.bnd" file. You could have
> > written them directly in the  section of the bundle plugin:
> >
> >  Bundle-Classpath: ., WEB-INF/classes
> >  Web-ContextPath: mywebapp
> >  DynamicImport-Package: *
> >  Webapp-Context: mywebapp
> >
> 
> It seems that maven-bundle-plugin, at least 2.3.4 version, automatically
> add  Bundle-Classpath: WEB-INF/classes if the project is a WAR or have a
> Webapp-Context (that make the bundle a WAB, as for OSGI in Action), in fact
> I do not have that intructions and the war project  Bundle-Classpath:
> WEB-INF/classes in the MANIFEST (note, without the dot).
> I think also that Webapp-Context has been deprecated in favor of the new
> Web-ContextPath you also have.

ok, thanks for the info, I used both headers (web-contextpath and
webapp-context) so far without issues, so I didn't worry to modify this
so far.

> As for DynamicImport-Package: *
> what does this do?


This is a very generic import header for the bundle. It is needed, if
you plan to have other bundles contribute wicket pages/components.
Wicket uses reflection to create page instances. In this case, the
classes must be available to the class loader. If you do not know them
up front, you can use the DynamicImport-Package statement.

 
> It does not seem you do not have specific Import or Export package
> instructions, so you use the maven-bundle-plugin defaults, so every dep is
> explicitly written in the MANIFEST right?

yes, every dep especially wicket is explicitely written in the manifest.

 
> 
> >
> > This creates a MANIFEST with Import-Package statements for all your
> > dependencies - they are not included in the war file. The war file has
> > no /lib folder, just WEB-IN

Re: [osgi] package org.apache.wicket.request exported either from core and request packages

[Daniele Dellafiore]

On Wed, Apr 27, 2011 at 8:57 AM, Martin Grigorov wrote:


> I'm not against improving the current state. I'm saying that it want
> last long without your help.
> I said several times that the community can create the uber-jar
> project in wicketstuff but so far no one wanted to do it.
> I can do it for you but I wont test it in a real OSGi container. I'm
> just not interested in this.
> But we can apply your patches if they are reasonable.
>

Let's try. As I told, the first move is to rename into .core.util and
.core.request the packages in -core bundle. This is reasonable? If it is
not, well, I'll go for a issue for 1.6 and move totally on the uber-jar
solution. If it is reasonable, we can proceed.


> About testing - I don't see how unit tests will help to keep it
> working in the future. Any ideas/patches on this matter are welcome!
>

Eh, this  can totally be done with pax-runner, as integration tests, but
I've not enough experience with this so far.


>
> My concerns are that we had similar issue with Portlets support. When
> we ran the vote whether to remove the support for Wicket 1.5 few
> people (~ 5) asked to move the related code in wicketstuff so the
> community can support it. Half an year later no one touched it so far.
>

This is totally reasonable. Let's see which way we can take here.

Regards.

Re: [osgi] package org.apache.wicket.request exported either from core and request packages

[Martin Grigorov]

Hi,

On Wed, Apr 27, 2011 at 10:43 AM, Daniele Dellafiore
 wrote:
> On Tue, Apr 26, 2011 at 9:12 PM, Daan van Etten  wrote:
>
>> Op 26 apr 2011, om 16:41 heeft Martin Grigorov het volgende geschreven:
>>
>>
>> Not doing anything now because it can break in the future is not a really
>> good argument..?
>> Anything can break, that's why there are unit tests, release candidates,
>> etcetera.
>> With some small design improvements (no split packages, 'better' jar(s))
>> and a better manifest the 'Wicket OSGI support' will surpass many other
>> frameworks or libraries.
>>
>
> This is also my main point to conversation. We're talking about being
> somewhere really close to a nice out of the box OSGi support. Why not take a
> little effort to make it complete? Also, having packages that span through
> different jars is not really good to me, OSGi or not.
>
I'm not against improving the current state. I'm saying that it want
last long without your help.
I said several times that the community can create the uber-jar
project in wicketstuff but so far no one wanted to do it.
I can do it for you but I wont test it in a real OSGi container. I'm
just not interested in this.
But we can apply your patches if they are reasonable.
About testing - I don't see how unit tests will help to keep it
working in the future. Any ideas/patches on this matter are welcome!

My concerns are that we had similar issue with Portlets support. When
we ran the vote whether to remove the support for Wicket 1.5 few
people (~ 5) asked to move the related code in wicketstuff so the
community can support it. Half an year later no one touched it so far.

> Anyway,
>
> Daan, I'm really interested in the classloading problem you had. Actually I
> did succeed in making a wicket-spring webapp start and work 100%.
> But after the wicket package is reinstalled or just refreshed in the
> container, @SpringBean injection stop working with:
>
> java.lang.IllegalArgumentException: Can not set
> org.fenotipi.services.StudiService field
> org.fenotipi.web.general.HomePage.studiService to
> org.apache.wicket.proxy.$Proxy40
>
> Any idea?
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [osgi] package org.apache.wicket.request exported either from core and request packages

[Daniele Dellafiore]

On Tue, Apr 26, 2011 at 11:48 PM, Eike Kettner  wrote:

> Hi Daniele,
>
> >
> > This is not as bad as having to package the uber-jar with the war, sure.
> > Better than keeping a separate wicket codebase, at least :)
> >
> > Anyway it's still a custom solution that I, and all wicket developers,
> have
> > to do. More over, they have to discover that this has to be done, that
> > wicket bundles are working bundles, but not usable.
> > Wicket bundles are some sort of raw jars+metadata that can be assemled in
> a
> > custom way to become a usable OSGI bundle. Whatever you consider the
> > uber-jar solution to go good or not, this is a flaw.
>
> I totally agree with you. Wicket is such a great web framework and
> people who like to use it with osgi shouldn't have a hard time to get
> both workgin together. The fact that the three wicket modules have osgi
> related meta data but don't work as osgi bundles is really confusing. So
> a distributed uber-jar would be a quick fix for that. People can easily
> deploy wicket to an osgi container.f a day in thread like this to finally
> arrive to the wicket-stuff projects that solves your problem.
>

Yeah but you know how things really works. You download/maven/something-else
the wicket jars. They do not work in osgi.
Then you start google around, it will take you hours, reading conversation
like this one, before eventually landing to the wicket-stuff page where
there is the solution. If that's the case.

You will be not happy. Of course I can accept the "wicket is not intended to
be OSGi compliant" explanation and go for the uber-jar in wicket-stuff.
Maybe I want to ask: why wicket can't be OSGi compliant? I consider OSGi to
be an important reference platform nowadays. Let's fill a jira issue and see
what happen.


>
>
> > I agree that you have to use -util -request  and -core to make wicket
> work,
> > but so, if they are so coupled, why to make different bundles at all?
> > Alexandros already asked for this.You say modularization helps wicket
> > developer.I would agree but what is the difference between the .request
> and
> > .util package in -request, -util and in -core?
> >
> > As Martin pointed out, there are no more implementation of wicket, to
> date.
> > So the -core is not a specific implementation of -request and -util.
> Maybe
> > just more concret classes?
> >
> > Again I think that the package that span across different modules is a
> > flawed design. For sure it is not OSGi-compliant.
>
> Again I agree with you. The uber jar is good to get wicket quickly
> running with osgi, but it is more a workaround.  I'm not deep in wicket
> code, but it feels awkward to first package classes in one package and
> than split this package across modules (which is even harder grained).


To me seems like that the split of .util and .request package into separate
bundles is just not complete. This is totally understandable.
I'm not seeing the point of splitting those two packages that, indeed, are
always necessary to run a wicket app, but sure I do not have enough insight
view of the project.
Despite that, it took ten minutes straight to me to renamce -core packages
into .wicket.util and .wicket.request and fix the confusion.
Indeed, mvn test now fails in -core, I did not take any care of those in my
tentative.

Re: [osgi] package org.apache.wicket.request exported either from core and request packages

[Daniele Dellafiore]

On Tue, Apr 26, 2011 at 9:12 PM, Daan van Etten  wrote:

> Op 26 apr 2011, om 16:41 heeft Martin Grigorov het volgende geschreven:
>
>
> Not doing anything now because it can break in the future is not a really
> good argument..?
> Anything can break, that's why there are unit tests, release candidates,
> etcetera.
> With some small design improvements (no split packages, 'better' jar(s))
> and a better manifest the 'Wicket OSGI support' will surpass many other
> frameworks or libraries.
>

This is also my main point to conversation. We're talking about being
somewhere really close to a nice out of the box OSGi support. Why not take a
little effort to make it complete? Also, having packages that span through
different jars is not really good to me, OSGi or not.

Anyway,

Daan, I'm really interested in the classloading problem you had. Actually I
did succeed in making a wicket-spring webapp start and work 100%.
But after the wicket package is reinstalled or just refreshed in the
container, @SpringBean injection stop working with:

java.lang.IllegalArgumentException: Can not set
org.fenotipi.services.StudiService field
org.fenotipi.web.general.HomePage.studiService to
org.apache.wicket.proxy.$Proxy40

Any idea?

Re: WELCOME to users@wicket.apache.org

[Martin Grigorov]

Hi,

I'm not sure whether this is possible at all.
Why do you need to do this ?

On Wed, Apr 27, 2011 at 8:12 AM, Matthew Goodson
 wrote:
> Hi guys,
> I'm trying to find out if an ajax request has come from page that was loaded
> from the browsers cache. Does anyone have any ideas of how I could achieve
> this?
> Thanks
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org