[jira] Commented: (WICKET-2080) InjectorHolder is broken when wicket-ioc.jar is shared between multiple web applications
[
https://issues.apache.org/jira/browse/WICKET-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770673#action_12770673
]
Jawher Moussa commented on WICKET-2080:
---
Works with 1.4-SNAPSHOT too.
Thanks !
> InjectorHolder is broken when wicket-ioc.jar is shared between multiple web
> applications
>
>
> Key: WICKET-2080
> URL: https://issues.apache.org/jira/browse/WICKET-2080
> Project: Wicket
> Issue Type: Bug
> Components: wicket-spring
>Affects Versions: 1.4-M3
> Environment: Java6 tomcat 6.0.18
>Reporter: Matej Zupanc
>Assignee: Igor Vaynberg
> Fix For: 1.4.4, 1.5-M1
>
> Attachments: wib.zip, wib2.zip
>
>
> I notice that in case, when I use two web-application on tomcat, sharing
> spring and wicket libraries, applications start to behave unpredictably.
> After short exploring and debug running, I discovered that wicket "ProxyBean"
> return wrong bean from Spring. When I try with ordinary call to Spring
> context
> (WebApplicationContextUtils.getRequiredWebApplicationContext(WebApplication.get().getServletContext()).getBean("testBeanName");)
> I get correct bean.
> My testCase has been run on tomcat 6.0.18. Shared library are placed under
> shared lib location in tomcat. All spring and wicket libraries are placed in
> shared lib location. For test I create webA and webB war archives. In both
> applications I use bean named "appIdProvider" but each application has
> different implementing class for this bean. When I start tomcat I see in
> logs, that both spring applicationContext are initialised. First I test webA
> application and result is what I expect. Next I make call to webB and result
> isn't what I expect, but result of call to bean injected with @SpringBean is
> same to call from webA application.
> Same story happens if I make first call to webB and after that to webA. In
> this case call to webB are correct and execution of webA is wrong.
> After printing the returned beans I see that annotated beans (@SpringBean)
> are LazyInitProxyFactory (in test values are
> "org.apache.wicket.proxy.lazyinitproxyfactory$jdkhand...@107eafc") and are
> same instances in both applications. If I make direct lookup in SpringContext
> I get back concrete bean and instances of this bean are different for each
> webapplication.
> All this doesn't happens if I deploy both web-application together with all
> spring and wicket libraries embedded into web application archive
> (WEB-INF/lib). But deployment of spring and wicket libraries for each
> application is expensive if I have many web application (using wicket and
> spring) on same server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2080) InjectorHolder is broken when wicket-ioc.jar is shared between multiple web applications
[
https://issues.apache.org/jira/browse/WICKET-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770670#action_12770670
]
Jawher Moussa commented on WICKET-2080:
---
True enough.
Tested (accidentally) with trunk (1.5-SNAPSHOT) and this bug is no more.
Now switching to the 1.4 branch to test with this version too.
> InjectorHolder is broken when wicket-ioc.jar is shared between multiple web
> applications
>
>
> Key: WICKET-2080
> URL: https://issues.apache.org/jira/browse/WICKET-2080
> Project: Wicket
> Issue Type: Bug
> Components: wicket-spring
>Affects Versions: 1.4-M3
> Environment: Java6 tomcat 6.0.18
>Reporter: Matej Zupanc
>Assignee: Igor Vaynberg
> Fix For: 1.4.4, 1.5-M1
>
> Attachments: wib.zip, wib2.zip
>
>
> I notice that in case, when I use two web-application on tomcat, sharing
> spring and wicket libraries, applications start to behave unpredictably.
> After short exploring and debug running, I discovered that wicket "ProxyBean"
> return wrong bean from Spring. When I try with ordinary call to Spring
> context
> (WebApplicationContextUtils.getRequiredWebApplicationContext(WebApplication.get().getServletContext()).getBean("testBeanName");)
> I get correct bean.
> My testCase has been run on tomcat 6.0.18. Shared library are placed under
> shared lib location in tomcat. All spring and wicket libraries are placed in
> shared lib location. For test I create webA and webB war archives. In both
> applications I use bean named "appIdProvider" but each application has
> different implementing class for this bean. When I start tomcat I see in
> logs, that both spring applicationContext are initialised. First I test webA
> application and result is what I expect. Next I make call to webB and result
> isn't what I expect, but result of call to bean injected with @SpringBean is
> same to call from webA application.
> Same story happens if I make first call to webB and after that to webA. In
> this case call to webB are correct and execution of webA is wrong.
> After printing the returned beans I see that annotated beans (@SpringBean)
> are LazyInitProxyFactory (in test values are
> "org.apache.wicket.proxy.lazyinitproxyfactory$jdkhand...@107eafc") and are
> same instances in both applications. If I make direct lookup in SpringContext
> I get back concrete bean and instances of this bean are different for each
> webapplication.
> All this doesn't happens if I deploy both web-application together with all
> spring and wicket libraries embedded into web application archive
> (WEB-INF/lib). But deployment of spring and wicket libraries for each
> application is expensive if I have many web application (using wicket and
> spring) on same server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2080) InjectorHolder is broken when wicket-ioc.jar is shared between multiple web applications
[
https://issues.apache.org/jira/browse/WICKET-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770546#action_12770546
]
Jawher Moussa commented on WICKET-2080:
---
Kudos Igor ! I'll check this out when 1.4.4 is out.
> InjectorHolder is broken when wicket-ioc.jar is shared between multiple web
> applications
>
>
> Key: WICKET-2080
> URL: https://issues.apache.org/jira/browse/WICKET-2080
> Project: Wicket
> Issue Type: Bug
> Components: wicket-spring
>Affects Versions: 1.4-M3
> Environment: Java6 tomcat 6.0.18
>Reporter: Matej Zupanc
>Assignee: Igor Vaynberg
> Fix For: 1.4.4, 1.5-M1
>
> Attachments: wib.zip, wib2.zip
>
>
> I notice that in case, when I use two web-application on tomcat, sharing
> spring and wicket libraries, applications start to behave unpredictably.
> After short exploring and debug running, I discovered that wicket "ProxyBean"
> return wrong bean from Spring. When I try with ordinary call to Spring
> context
> (WebApplicationContextUtils.getRequiredWebApplicationContext(WebApplication.get().getServletContext()).getBean("testBeanName");)
> I get correct bean.
> My testCase has been run on tomcat 6.0.18. Shared library are placed under
> shared lib location in tomcat. All spring and wicket libraries are placed in
> shared lib location. For test I create webA and webB war archives. In both
> applications I use bean named "appIdProvider" but each application has
> different implementing class for this bean. When I start tomcat I see in
> logs, that both spring applicationContext are initialised. First I test webA
> application and result is what I expect. Next I make call to webB and result
> isn't what I expect, but result of call to bean injected with @SpringBean is
> same to call from webA application.
> Same story happens if I make first call to webB and after that to webA. In
> this case call to webB are correct and execution of webA is wrong.
> After printing the returned beans I see that annotated beans (@SpringBean)
> are LazyInitProxyFactory (in test values are
> "org.apache.wicket.proxy.lazyinitproxyfactory$jdkhand...@107eafc") and are
> same instances in both applications. If I make direct lookup in SpringContext
> I get back concrete bean and instances of this bean are different for each
> webapplication.
> All this doesn't happens if I deploy both web-application together with all
> spring and wicket libraries embedded into web application archive
> (WEB-INF/lib). But deployment of spring and wicket libraries for each
> application is expensive if I have many web application (using wicket and
> spring) on same server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2080) InjectorHolder is broken when wicket-ioc.jar is shared between multiple web applications
[
https://issues.apache.org/jira/browse/WICKET-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jawher Moussa updated WICKET-2080:
--
Attachment: wib2.zip
Oups, sorry, you need to add this repository :
spring-osgi
Spring OSGi Friendly Repository
http://maven.springframework.org/osgi
I've uploaded another version of the zip, if you would give it another try :)
> InjectorHolder is broken when wicket-ioc.jar is shared between multiple web
> applications
>
>
> Key: WICKET-2080
> URL: https://issues.apache.org/jira/browse/WICKET-2080
> Project: Wicket
> Issue Type: Bug
> Components: wicket-spring
>Affects Versions: 1.4-M3
> Environment: Java6 tomcat 6.0.18
>Reporter: Matej Zupanc
>Assignee: Igor Vaynberg
> Fix For: 1.5-M1
>
> Attachments: wib.zip, wib2.zip
>
>
> I notice that in case, when I use two web-application on tomcat, sharing
> spring and wicket libraries, applications start to behave unpredictably.
> After short exploring and debug running, I discovered that wicket "ProxyBean"
> return wrong bean from Spring. When I try with ordinary call to Spring
> context
> (WebApplicationContextUtils.getRequiredWebApplicationContext(WebApplication.get().getServletContext()).getBean("testBeanName");)
> I get correct bean.
> My testCase has been run on tomcat 6.0.18. Shared library are placed under
> shared lib location in tomcat. All spring and wicket libraries are placed in
> shared lib location. For test I create webA and webB war archives. In both
> applications I use bean named "appIdProvider" but each application has
> different implementing class for this bean. When I start tomcat I see in
> logs, that both spring applicationContext are initialised. First I test webA
> application and result is what I expect. Next I make call to webB and result
> isn't what I expect, but result of call to bean injected with @SpringBean is
> same to call from webA application.
> Same story happens if I make first call to webB and after that to webA. In
> this case call to webB are correct and execution of webA is wrong.
> After printing the returned beans I see that annotated beans (@SpringBean)
> are LazyInitProxyFactory (in test values are
> "org.apache.wicket.proxy.lazyinitproxyfactory$jdkhand...@107eafc") and are
> same instances in both applications. If I make direct lookup in SpringContext
> I get back concrete bean and instances of this bean are different for each
> webapplication.
> All this doesn't happens if I deploy both web-application together with all
> spring and wicket libraries embedded into web application archive
> (WEB-INF/lib). But deployment of spring and wicket libraries for each
> application is expensive if I have many web application (using wicket and
> spring) on same server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2080) InjectorHolder is broken when wicket-ioc.jar is shared between multiple web applications
[
https://issues.apache.org/jira/browse/WICKET-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jawher Moussa updated WICKET-2080:
--
Attachment: wib.zip
Okay, so, once the attached wib.zip downloaded and extracted somewhere, let's
say in a directory ${wib} :
- execute 'mvn install' in the directory ${wib}/org.djo.tp
- Launch eclipse and import the 5 projects located in ${wib} into your workspace
- In eclipse, double click on the file org.djo.tp/target.target and click on
the button "Set as target platform" in the top right corner of the editor.
- Click on the run button and select the "test" run configuration.
- If everything wen well, after 1 or 2 seconds, you should be able to access
the 2 wicket applications from your browser by pointing it to
http://localhost:9090/app1/ and http://localhost:9090/app1/
Depending on the order, one of the apps should work and show a "App [1|2]"
header, the other should cause an exception to show up.
I'll be around should you encounter any issues in the process ;)
> InjectorHolder is broken when wicket-ioc.jar is shared between multiple web
> applications
>
>
> Key: WICKET-2080
> URL: https://issues.apache.org/jira/browse/WICKET-2080
> Project: Wicket
> Issue Type: Bug
> Components: wicket-spring
>Affects Versions: 1.4-M3
> Environment: Java6 tomcat 6.0.18
>Reporter: Matej Zupanc
>Assignee: Igor Vaynberg
> Fix For: 1.5-M1
>
> Attachments: wib.zip
>
>
> I notice that in case, when I use two web-application on tomcat, sharing
> spring and wicket libraries, applications start to behave unpredictably.
> After short exploring and debug running, I discovered that wicket "ProxyBean"
> return wrong bean from Spring. When I try with ordinary call to Spring
> context
> (WebApplicationContextUtils.getRequiredWebApplicationContext(WebApplication.get().getServletContext()).getBean("testBeanName");)
> I get correct bean.
> My testCase has been run on tomcat 6.0.18. Shared library are placed under
> shared lib location in tomcat. All spring and wicket libraries are placed in
> shared lib location. For test I create webA and webB war archives. In both
> applications I use bean named "appIdProvider" but each application has
> different implementing class for this bean. When I start tomcat I see in
> logs, that both spring applicationContext are initialised. First I test webA
> application and result is what I expect. Next I make call to webB and result
> isn't what I expect, but result of call to bean injected with @SpringBean is
> same to call from webA application.
> Same story happens if I make first call to webB and after that to webA. In
> this case call to webB are correct and execution of webA is wrong.
> After printing the returned beans I see that annotated beans (@SpringBean)
> are LazyInitProxyFactory (in test values are
> "org.apache.wicket.proxy.lazyinitproxyfactory$jdkhand...@107eafc") and are
> same instances in both applications. If I make direct lookup in SpringContext
> I get back concrete bean and instances of this bean are different for each
> webapplication.
> All this doesn't happens if I deploy both web-application together with all
> spring and wicket libraries embedded into web application archive
> (WEB-INF/lib). But deployment of spring and wicket libraries for each
> application is expensive if I have many web application (using wicket and
> spring) on same server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (WICKET-2080) InjectorHolder is broken when wicket-ioc.jar is shared between multiple web applications
[
https://issues.apache.org/jira/browse/WICKET-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769858#action_12769858
]
Jawher Moussa edited comment on WICKET-2080 at 10/25/09 8:08 PM:
-
> jawher can you provide a self-contained osgi setup that can replicate this
> problem? something that is easy to run and debug - preferably using something
> like our Start class. if i have a testbench then i can probably fix the
> problem.
Igor: would an eclipse workspace do ? I can provide you with an archive
containig 5 projects :
- 2 wicket webapps that'll serve to reproduce the bug
- 2 config bundles (for log4j and jetty)
- 1 bundle that contains a pom.xml. Running maven inside this project's
directory will fetch the 27 bundles required for the thing to work.
Once the jars are fetched and isntalled by maven, you'll only have to execute
an existing eclipse launch configuration, in a browser, opening
http://localhost:9090/app1/ and http://localhost:9090/app2/ in two tabs (or
windows) will reproduce this bug.
Is that ok ? (If not, I can try and play a bit with embedding apache felix and
launching it from a java main method)
was (Author: djo.mos):
bq. jawher can you provide a self-contained osgi setup that can replicate
this problem? something that is easy to run and debug - preferably using
something like our Start class. if i have a testbench then i can probably fix
the problem.
Igor: would an eclipse workspace do ? I can provide you with an archive
containig 5 projects :
- 2 wicket webapps that'll serve to reproduce the bug
- 2 config bundles (for log4j and jetty)
- 1 bundle that contains a pom.xml. Running maven inside this project's
directory will fetch the 27 bundles required for the thing to work.
Once the jars are fetched and isntalled by maven, you'll only have to execute
an existing eclipse launch configuration, in a browser, opening
http://localhost:9090/app1/ and http://localhost:9090/app2/ in two tabs (or
windows) will reproduce this bug.
Is that ok ? (If not, I can try and play a bit with embedding apache felix and
launching it from a java main method)
> InjectorHolder is broken when wicket-ioc.jar is shared between multiple web
> applications
>
>
> Key: WICKET-2080
> URL: https://issues.apache.org/jira/browse/WICKET-2080
> Project: Wicket
> Issue Type: Bug
> Components: wicket-spring
>Affects Versions: 1.4-M3
> Environment: Java6 tomcat 6.0.18
>Reporter: Matej Zupanc
>Assignee: Igor Vaynberg
> Fix For: 1.5-M1
>
>
> I notice that in case, when I use two web-application on tomcat, sharing
> spring and wicket libraries, applications start to behave unpredictably.
> After short exploring and debug running, I discovered that wicket "ProxyBean"
> return wrong bean from Spring. When I try with ordinary call to Spring
> context
> (WebApplicationContextUtils.getRequiredWebApplicationContext(WebApplication.get().getServletContext()).getBean("testBeanName");)
> I get correct bean.
> My testCase has been run on tomcat 6.0.18. Shared library are placed under
> shared lib location in tomcat. All spring and wicket libraries are placed in
> shared lib location. For test I create webA and webB war archives. In both
> applications I use bean named "appIdProvider" but each application has
> different implementing class for this bean. When I start tomcat I see in
> logs, that both spring applicationContext are initialised. First I test webA
> application and result is what I expect. Next I make call to webB and result
> isn't what I expect, but result of call to bean injected with @SpringBean is
> same to call from webA application.
> Same story happens if I make first call to webB and after that to webA. In
> this case call to webB are correct and execution of webA is wrong.
> After printing the returned beans I see that annotated beans (@SpringBean)
> are LazyInitProxyFactory (in test values are
> "org.apache.wicket.proxy.lazyinitproxyfactory$jdkhand...@107eafc") and are
> same instances in both applications. If I make direct lookup in SpringContext
> I get back concrete bean and instances of this bean are different for each
> webapplication.
> All this doesn't happens if I deploy both web-application together with all
> spring and wicket libraries embedded into web application archive
> (WEB-INF/lib). But deployment of spring and wicket libraries for each
> application is expensive if I have many web application (using wicket and
> spring) on same server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2080) InjectorHolder is broken when wicket-ioc.jar is shared between multiple web applications
[
https://issues.apache.org/jira/browse/WICKET-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769858#action_12769858
]
Jawher Moussa commented on WICKET-2080:
---
bq. jawher can you provide a self-contained osgi setup that can replicate this
problem? something that is easy to run and debug - preferably using something
like our Start class. if i have a testbench then i can probably fix the problem.
Igor: would an eclipse workspace do ? I can provide you with an archive
containig 5 projects :
- 2 wicket webapps that'll serve to reproduce the bug
- 2 config bundles (for log4j and jetty)
- 1 bundle that contains a pom.xml. Running maven inside this project's
directory will fetch the 27 bundles required for the thing to work.
Once the jars are fetched and isntalled by maven, you'll only have to execute
an existing eclipse launch configuration, in a browser, opening
http://localhost:9090/app1/ and http://localhost:9090/app2/ in two tabs (or
windows) will reproduce this bug.
Is that ok ? (If not, I can try and play a bit with embedding apache felix and
launching it from a java main method)
> InjectorHolder is broken when wicket-ioc.jar is shared between multiple web
> applications
>
>
> Key: WICKET-2080
> URL: https://issues.apache.org/jira/browse/WICKET-2080
> Project: Wicket
> Issue Type: Bug
> Components: wicket-spring
>Affects Versions: 1.4-M3
> Environment: Java6 tomcat 6.0.18
>Reporter: Matej Zupanc
>Assignee: Igor Vaynberg
> Fix For: 1.5-M1
>
>
> I notice that in case, when I use two web-application on tomcat, sharing
> spring and wicket libraries, applications start to behave unpredictably.
> After short exploring and debug running, I discovered that wicket "ProxyBean"
> return wrong bean from Spring. When I try with ordinary call to Spring
> context
> (WebApplicationContextUtils.getRequiredWebApplicationContext(WebApplication.get().getServletContext()).getBean("testBeanName");)
> I get correct bean.
> My testCase has been run on tomcat 6.0.18. Shared library are placed under
> shared lib location in tomcat. All spring and wicket libraries are placed in
> shared lib location. For test I create webA and webB war archives. In both
> applications I use bean named "appIdProvider" but each application has
> different implementing class for this bean. When I start tomcat I see in
> logs, that both spring applicationContext are initialised. First I test webA
> application and result is what I expect. Next I make call to webB and result
> isn't what I expect, but result of call to bean injected with @SpringBean is
> same to call from webA application.
> Same story happens if I make first call to webB and after that to webA. In
> this case call to webB are correct and execution of webA is wrong.
> After printing the returned beans I see that annotated beans (@SpringBean)
> are LazyInitProxyFactory (in test values are
> "org.apache.wicket.proxy.lazyinitproxyfactory$jdkhand...@107eafc") and are
> same instances in both applications. If I make direct lookup in SpringContext
> I get back concrete bean and instances of this bean are different for each
> webapplication.
> All this doesn't happens if I deploy both web-application together with all
> spring and wicket libraries embedded into web application archive
> (WEB-INF/lib). But deployment of spring and wicket libraries for each
> application is expensive if I have many web application (using wicket and
> spring) on same server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2080) InjectorHolder is broken when wicket-ioc.jar is shared between multiple web applications
[
https://issues.apache.org/jira/browse/WICKET-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769648#action_12769648
]
Jawher Moussa commented on WICKET-2080:
---
Just to mention that this problem also arises when Wicket is used in an OSGi
environment. In such a scenario, the wicket jars are installed as bundles in
the OSGi container and are shared by all the deployed web apps.
I faced this problem recently, and the only workaround I found was to embed the
different webapps in a single bundle and assign a different wicket filter to
each. It works but goes against modularization.
> InjectorHolder is broken when wicket-ioc.jar is shared between multiple web
> applications
>
>
> Key: WICKET-2080
> URL: https://issues.apache.org/jira/browse/WICKET-2080
> Project: Wicket
> Issue Type: Bug
> Components: wicket-spring
>Affects Versions: 1.4-M3
> Environment: Java6 tomcat 6.0.18
>Reporter: Matej Zupanc
>Assignee: Igor Vaynberg
> Fix For: 1.5-M1
>
>
> I notice that in case, when I use two web-application on tomcat, sharing
> spring and wicket libraries, applications start to behave unpredictably.
> After short exploring and debug running, I discovered that wicket "ProxyBean"
> return wrong bean from Spring. When I try with ordinary call to Spring
> context
> (WebApplicationContextUtils.getRequiredWebApplicationContext(WebApplication.get().getServletContext()).getBean("testBeanName");)
> I get correct bean.
> My testCase has been run on tomcat 6.0.18. Shared library are placed under
> shared lib location in tomcat. All spring and wicket libraries are placed in
> shared lib location. For test I create webA and webB war archives. In both
> applications I use bean named "appIdProvider" but each application has
> different implementing class for this bean. When I start tomcat I see in
> logs, that both spring applicationContext are initialised. First I test webA
> application and result is what I expect. Next I make call to webB and result
> isn't what I expect, but result of call to bean injected with @SpringBean is
> same to call from webA application.
> Same story happens if I make first call to webB and after that to webA. In
> this case call to webB are correct and execution of webA is wrong.
> After printing the returned beans I see that annotated beans (@SpringBean)
> are LazyInitProxyFactory (in test values are
> "org.apache.wicket.proxy.lazyinitproxyfactory$jdkhand...@107eafc") and are
> same instances in both applications. If I make direct lookup in SpringContext
> I get back concrete bean and instances of this bean are different for each
> webapplication.
> All this doesn't happens if I deploy both web-application together with all
> spring and wicket libraries embedded into web application archive
> (WEB-INF/lib). But deployment of spring and wicket libraries for each
> application is expensive if I have many web application (using wicket and
> spring) on same server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-1645) Syntactic errors in the manifest OSGi headers
[ https://issues.apache.org/jira/browse/WICKET-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598254#action_12598254 ] Jawher Moussa commented on WICKET-1645: --- Thanks Gerolf. I've retrieved the latest snapshot of date-time and tested it => It deploys perfectly well, and no more problems with the manifest \o/ Excellent work ! Many thanks. Cheers, Jawher. > Syntactic errors in the manifest OSGi headers > - > > Key: WICKET-1645 > URL: https://issues.apache.org/jira/browse/WICKET-1645 > Project: Wicket > Issue Type: Bug > Components: wicket-datetime >Affects Versions: 1.4-M2 >Reporter: Jawher Moussa >Assignee: Gerolf Seitz > > Hello, > Not exactly sure about the error location, but upon deployment on a OSGi > container (SpringSource Application Context, based on Equinox), I get the > following trace: > [2008-05-19 19:39:26.041] fs-watcherThe bundle > '/home/djo/Java/servers/springsource-ap-1.0.0.beta3/repository/bundles/usr/wicket-datetime-1.4-m2.jar' > could not be provisioned is its manifest is malformed. The error encountered > whilst parsing the manifest was: The manifest identified by Name 'Wicket > Date/Time', Symbolic Name 'org.apache.wicket.wicket-datetime', and Version > '1.4.0.m2' has the following errors [org.antlr.runtime.NoViableAltException > on 'Package Header [Import]' at Char: > 768,org.antlr.runtime.NoViableAltException on 'Package Header [Export]' at > Char: 101] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-1645) Syntactic errors in the manifest OSGi headers
[ https://issues.apache.org/jira/browse/WICKET-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598232#action_12598232 ] Jawher Moussa commented on WICKET-1645: --- Hi and thanks for the impressively fast response :-O > Jawher, could you try again with latest trunk? Erm ... I'm more than willing to do, but how ? you mean rebuild the project from SVN ? Should I use maven ? Arent't there some nightlies ? > Syntactic errors in the manifest OSGi headers > - > > Key: WICKET-1645 > URL: https://issues.apache.org/jira/browse/WICKET-1645 > Project: Wicket > Issue Type: Bug > Components: wicket-datetime >Affects Versions: 1.4-M2 >Reporter: Jawher Moussa >Assignee: Gerolf Seitz > > Hello, > Not exactly sure about the error location, but upon deployment on a OSGi > container (SpringSource Application Context, based on Equinox), I get the > following trace: > [2008-05-19 19:39:26.041] fs-watcherThe bundle > '/home/djo/Java/servers/springsource-ap-1.0.0.beta3/repository/bundles/usr/wicket-datetime-1.4-m2.jar' > could not be provisioned is its manifest is malformed. The error encountered > whilst parsing the manifest was: The manifest identified by Name 'Wicket > Date/Time', Symbolic Name 'org.apache.wicket.wicket-datetime', and Version > '1.4.0.m2' has the following errors [org.antlr.runtime.NoViableAltException > on 'Package Header [Import]' at Char: > 768,org.antlr.runtime.NoViableAltException on 'Package Header [Export]' at > Char: 101] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (WICKET-1645) Syntactic errors in the manifest OSGi headers
Syntactic errors in the manifest OSGi headers - Key: WICKET-1645 URL: https://issues.apache.org/jira/browse/WICKET-1645 Project: Wicket Issue Type: Bug Components: wicket-datetime Affects Versions: 1.4-M2 Reporter: Jawher Moussa Hello, Not exactly sure about the error location, but upon deployment on a OSGi container (SpringSource Application Context, based on Equinox), I get the following trace: [2008-05-19 19:39:26.041] fs-watcherThe bundle '/home/djo/Java/servers/springsource-ap-1.0.0.beta3/repository/bundles/usr/wicket-datetime-1.4-m2.jar' could not be provisioned is its manifest is malformed. The error encountered whilst parsing the manifest was: The manifest identified by Name 'Wicket Date/Time', Symbolic Name 'org.apache.wicket.wicket-datetime', and Version '1.4.0.m2' has the following errors [org.antlr.runtime.NoViableAltException on 'Package Header [Import]' at Char: 768,org.antlr.runtime.NoViableAltException on 'Package Header [Export]' at Char: 101] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
