[jira] Commented: (WICKET-3088) "split-package" problem for wicket bundles started in an osgi container

["Eike Kettner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977709#action_12977709 ] 

Eike Kettner commented on WICKET-3088:
--------------------------------------

Hello,

I still found some unsolved issues:

1) wicket-core and wicket-request both export org.apache.wicket.request and org.apache.wicket.request.[handler|mapper]
2) wicket-core and wicket-util both export org.apache.wicket, org.apache.wicket.util.[crypt,io,lang,resource,string]

to 1)
For the package org.apache.wicket.request the core module only contains one class ClientInfo.java

For a short test I renamed the mentioned packages (core: util->utils, request->requests), moved ClientInfo to org.apache.wicket.request and it worked.

I think the easiest way to solve this is to include "core" in package names of wicket-core module, or to move util and request packages completely to the appropriate modules (and out of wicket-core).

this applies to rev 1055096.

Kind Regards,
Eike


> "split-package" problem for wicket bundles started in an osgi container
> -----------------------------------------------------------------------
>
>                 Key: WICKET-3088
>                 URL: https://issues.apache.org/jira/browse/WICKET-3088
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5-M2.1
>         Environment: Java 1.6.0_21-b06, wicket 1.5-M2.1,felix 3.0.2 (Linux (Ubuntu 32bit))
>            Reporter: Eike Kettner
>            Assignee: Martin Grigorov
>             Fix For: 1.5-M4
>
>         Attachments: osgiquickstart.tar.gz
>
>
> Referring to the thread in user mailing list: http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-and-OSGi-td2847734.html
> There is a problem when the wicket bundles are started in an osgi envirionment because of split packages

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.