Re: Newbee to Joe-E

Hi,

I am trying to convert an existing Java based web application into
Joe-E compatible constructs.
I see that there are a number of classes which have all of their
constructors and most methods suppressed. Example File Class, URI
class.
I do understand the reason why the classes are suppressed , but are
there some alternative safe classes, wrappers provided that could be
used to replace these classes.
Is there a standard method that should be followed when trying to
convert "denied/suppressed" JAVA constructs to Joe-E constructs.

Thanks,
Samriti.


On Mon, Nov 15, 2010 at 6:59 PM, samriti katoch <[email protected]> wrote:
> Hi Adrian,
>
> I figured that out yesterday.
> Yes, the documentation is a little hazy in making this point clear.
>
> Thanks a lot for your reply.
> -Sam.
>
> On Mon, Nov 15, 2010 at 6:12 PM, Adrian Mettler
> <[email protected]> wrote:
>> Hi Sam.  Thanks for taking a look at Joe-E.
>>
>> I'm guessing that most likely, you have the plugin installed and enabled
>> for your project, but it isn't actually examining your code because the
>> package the code is in has not been marked as a Joe-E package.  In order
>> to allow a project to contain Joe-E and non-Joe-E code, the verifier
>> only checks packages that have been marked as Joe-E packages using the
>> @org.joe_e.IsJoeE annotation.  It skips over other packages, which can
>> then only be called from Joe-E code using the taming mechanism.
>>
>> While the documentation says how to mark a package as Joe-E (reproduced
>> below) I now see that it doesn't make it clear why you would want to do
>> so -- namely, that the verifier only looks for Joe-E violations in the
>> code of packages that have this annotation.  I'll see if I can fix the
>> documentation to make this clearer.
>>
>> (Joe-E packages are identified by whether or not the package is
>> annotated with the org.joe_e.IsJoeE annotation type. This can be added
>> to a package by creating a file named package-info.java in the package
>> directory containing the line "@org.joe_e.IsJoeE package package.name;"
>> where package.name is the name of the package. Once you've created this
>> file once, you can copy and paste the file to other packages; Eclipse is
>> smart enough to fix the package name.)
>>
>> Thanks for the interest and feedback,
>> Adrian
>>
>> samriti katoch wrote:
>>> Hi,
>>>
>>> So I have the Joe-E plugin installed on eclipse 3.3 and have the
>>> library-2.2.2.jar as an external JAR in the project build path. I also
>>> have the taming database taming-20100421 folder path has been set in
>>> the Joe-E preferences.All these from the commandline-2.2.2download. I
>>> am also able to see the "Enable Joe-E verifier" option for a sample
>>> project.
>>>
>>> However, when I enable the verifier not a single warning message is
>>> generated, this is even when I write a sample program mentioned in the
>>> Joe-E specification (the one in which an exception contains a
>>> capability).
>>>
>>> I am not sure what is wrong. Any help will be greatly appreciated.
>>>
>>> Thanks,
>>> Sam.
>>> _______________________________________________
>>> e-lang mailing list
>>> [email protected]
>>> http://www.eros-os.org/mailman/listinfo/e-lang
>>
>> _______________________________________________
>> e-lang mailing list
>> [email protected]
>> http://www.eros-os.org/mailman/listinfo/e-lang
>>
>