[jboss-as7-dev] De-typed robustness

[Carlo de Wolf]

I keep seeing two issues with de-typed:
- traceability of operations (in IDE, during refactoring)
- plain invalid invocations, like this one

We need more coverage on de-typed operations.
But maybe we can also tie the runtime to the descriptions, so that 
invalid operations are caught. (A special mode of running?)

Carlo

On 05/20/2011 08:01 PM, Brian Stansberry wrote:
> Fixed.
>
> http://github.com/jbossas/jboss-as/compare/78ee9b2...0a8d61e
>
> On 5/20/11 12:44 PM, Brian Stansberry wrote:
>> I think I know the fix.
>>
>> On 5/20/11 12:41 PM, Scott Stark wrote:
>>> Thank goodness.
>>>
>>> On 5/20/11 10:35 AM, Brian Stansberry wrote:
>>>> I see it too using the latest upstream. So it's not because you're
>>>> checkout is out of date.
>>>>
>>>> On 5/20/11 12:22 PM, Scott Stark wrote:
>>>>> This is ridiculous. I created another github account, forked
>>>>> jbossas/jboss-as:
>>>>> https://github.com/starksmjboss/jboss-as
>>>>>
>>>>> clone that, build it and run it and still see the same problem:
>>>>>
>>>>> [368](ironmaiden:bin)>      ls
>>>>> domain.bat    jboss-admin.bat    standalone.bat    wsconsume.bat
>>>>> wsprovide.sh
>>>>> domain.conf    jboss-admin.sh    standalone.conf    wsconsume.sh
>>>>> domain.sh    server.log    standalone.sh    wsprovide.bat
>>>>>
>>>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>