I just tried our own WAB Fragment test with 3.1.2.2 and it works. When I
look at your test case, I see that you are bundling
wabtest-fragment-1.0-SNAPSHOT.jar in WEB-INF/lib of
wabtest-1.0-SNAPSHOT.jar. When I modify the host bundle to not include
this fragment jar, things worked as expected. I first installed and
started host and got HTTP-404 for wabtest/test.jsp resource. Then I
installed the fragment and updated the host and the above resource is
available.
Thanks,
Sahoo
On Friday 07 September 2012 08:28 AM, Sahoo wrote:
> I will look into it and get back. We will try with our existing WAB
> fragment test to begin with. If possible, share your test case just
> case it is specific to a given test case.
>
> Thanks,
> Sahoo
>
> On Friday 07 September 2012 07:00 AM, forums_at_java.net wrote:
>> I spent quite some time trying to get WAB Fragments to work in Glassfish
>> 3.1.2.2 (as specified in
>> http://glassfish.java.net/public/GF-OSGi-Features.pdf) without any
>> luck. Out
>> of frustration I tried Glassfish 3.1.1 and 3.1.2 and it worked first
>> time. I
>> have attached the war (I had to change the extension wabtest.jar
>> given the
>> restrictions on the upload for this forum) and the associated
>> fragment. After
>> installing the war (via autodeploy/bundles or asadmin) you can go to
>> http://host:port/wabtest/index.jsp After installing the fragment you
>> should
>> be able to see http://host:port/wabtest/test.jsp With GF 3.1.1 and
>> 3.1.2 this
>> works. With 3.1.2.2 it does not, the bundle installs fine according
>> to the
>> server.log, I just can't access the page. Is there some config that
>> needs to
>> change for 3.1.2.2 to allow this to work? Regards Cameron
>>
>> --
>>
>> [Message sent by forum member 'cameronr']
>>
>> View Post: http://forums.java.net/node/889931
>>
>>
>>
>